Thanks Ari,
After your reply a reviewed with Orca the GUIDs of my components and
find out that, since the version the issue started 80% of the GUIDs were
changed I changed back to the original values and the Upgrade worked
just fine.
You're answer was exactly what I needed :)
PameAlex
--
That's a good point. In most cases, the default is "absent" == "no". Except in
this case.
The hint is here: "Typically the value should be 'yes', except when the custom
action needs elevated privileges to apply changes to the machine."
Be great if you could open a documentation bug to suggest
is customaction impersonate attribute default when attribute is not specified
"yes" or "no" . . . the current chm details does not say which
--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to
You could advertise the shortcut. That's most straight forward. Or you could
ignore ICE69. I've considered doing so in the past... it is a very frustrating
situation for cases that don't happen often.
-Original Message-
From: Curtis Jewell (Perl-programming e-mail)
[mailto:lists.wix-
Not sure if sub keys are supported... be a good feature request if they are not
-Original Message-
From: Reddy, Mallikarjun (GWM-CAI) [mailto:mallikarjun_re...@ml.com]
Sent: Friday, January 30, 2009 06:14
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] A
On Fri, 30 Jan 2009, Bob Arnson wrote about Re: [WiX-users] Why is this not...:
> Curtis Jewell (Perl-programming e-mail) wrote:
>> Package/@InstallScope='perMachine' should turn on ALLUSERS=1 and therefore,
>> avoid those particular 2 ICE's, correct? If not, why not? I'm puzzled.
>>
>
> Sadly, n
Pamela Alvarez wrote:
> This is the issue.. I'm developing a product that releases versions
> every month and each of these releases can be used as a major upgrade.
> For the Major Upgrade I've scheduled the RemoveExistingProducts action
> after InstallFinalize and it worked for a while.. but th
Curtis Jewell (Perl-programming e-mail) wrote:
> Package/@InstallScope='perMachine' should turn on ALLUSERS=1 and therefore,
> avoid those particular 2 ICE's, correct? If not, why not? I'm puzzled.
>
Sadly, no. Because ALLUSERS is a public property, it can be reset at the
command line. See
On Fri, 30 Jan 2009, Olivier Cochelin wrote about Re: [WiX-users] Why is...:
> MSI requires for each component a KeyPath to check if the component is
> here or not (when repairing an install for example).
> Typically a Keypath is a file, folder or registry key. If the component
> contains items th
MSI requires for each component a KeyPath to check if the component is
here or not (when repairing an install for example).
Typically a Keypath is a file, folder or registry key. If the component
contains items that are user-specific the KeyPath must also be
user-specific.
So you can add something
I messed up on the pasting, so here it is, fixed.
I'm compiling my installer on WiX 3.0.4805. Here is the error(s) I get...
C:\Documents and Settings\Curtis\Local
Settings\Temp\perldist\wix_fragments\Icons.wxs(5) : error LGHT0204 : ICE38:
Component C_S_CPAN_Client installs to user profile. It m
I'm compiling my installer on WiX 3.0.4805. Here is the error(s) I get...
C:\Documents and Settings\Curtis\Local
Settings\Temp\perldist\wix_fragments\Icons.wxs(5) : error LGHT0204 : ICE38:
Component C_S_CPA
N_Client installs to user profile. It must use a registry key under HKCU as
its KeyPath,
It sounds like your component GUIDs changed between releases. Make sure all
the GUIDs stay the same.
And check the verbose log during the upgrade, it will tell you what it intends
to do with each component, which can help you figure out why it's doing that.
-Ari
-Original Message-
Fr
Hi there!
Thanks for your answer! We will either use XML config files or
environment variables. This decision is still open. What I want to do is
to execute the SSIS package from a C# application to perform a Fuzzy
lookup to compare addresses. There are around 1 million data rows to
compare. T
Hi All,
This is the issue.. I'm developing a product that releases versions
every month and each of these releases can be used as a major upgrade.
For the Major Upgrade I've scheduled the RemoveExistingProducts action
after InstallFinalize and it worked for a while.. but then one day
without a
Hi,
thank you for this hint. I found more information now after searching
for "Major Upgrade".
But somehow I couldn't find a working example.
Here is my xml file:
NEWPRODUCTFOUND
Rob, it seems to be cache package. Now with Ex, I am able to have the
permissions retained. Could you let me know how I make the permissions
apply to the subkeys too ? Earlier I mentioned that with I
was able to get the permissions to the subkeys. But now I am not getting
that either. I guess I wa
I had a similar situation and this is how I was able to resolve.
Our products requires SQL 2008 and I used wix installer and with Bootstrapper
to install SQL 2008 and after installing SQL 2008 we install our product after
the products gets installed before the finish dialog, I execute a custom Ac
Hello guys,
I would like to launch a Configuration Wizard of my application after the
installation process. This Wizard would be responsible of setting the SQL
Server, user and password informations, writing to registry and running a
service. So, it needs elevated privileges. But, if I understand c
As for me, the best way to get the major and minor versions of IIS is to
reference the properties introduced by standard IIS extension:
Note, that the values are prefixed with the '#' sign. Thus, for IIS 5.1
(WinXP) it is IISMAJORVERSION="#5" and IISMINORVERSION="#1".
Probably, the presence of
Hi,
Here's a sample code to detect IIS 5/6 or some IIS7 components :
Then I use these properties to diplay or not a feature :
Fix was just checked-in. If all goes well, build that comes out tomorrow will
be much happier.
-Original Message-
From: Uwe Stump [mailto:uwe.st...@gewi.com]
Sent: Friday, January 30, 2009 01:14
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] SetupBld a
Ok. I'll have a look at former discussions than.
Thanks.
Fred
Rob Mensching a écrit :
> This is discussed much in the list. You might search to get lots of options.
> Nothing is supported natively.
>
> -Original Message-
> From: Frédéric Viollet [mailto:frederic.viol...@evidian.com]
Rob, I think, you are right. The problem does not occur in WiX 3.0.4827.0.
So I will try to open a bug. Be warned ;-)
Kind regards and many thanks for your help,
Uwe
-Ursprüngliche Nachricht-
Von: Rob Mensching [mailto:rob.mensch...@microsoft.com]
Gesendet: Donnerstag, 29. Januar 2009 17
This is discussed much in the list. You might search to get lots of options.
Nothing is supported natively.
-Original Message-
From: Frédéric Viollet [mailto:frederic.viol...@evidian.com]
Sent: Friday, January 30, 2009 00:57
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] mult
Hi everyone,
I was wondering if it was possible to build a single installer that
embeds several languages (this installer would switch to the platform's
current language)?
Or do I have to build as many installers as I have languages to support?
I want my product to be able to be deployed in Fr
Yeah sure. Check out Major Upgrade.
-Original Message-
From: Thomas Guettler [mailto:h...@tbz-pariv.de]
Sent: Friday, January 30, 2009 00:31
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] auto delete on reinstall
Hi,
if I try to install a new version of my msi file, I get the
Hi,
if I try to install a new version of my msi file, I get the error message,
that I need to uninstall it first.
Is there a way to automatically uninstall it? Is possible to enable a switch
in the wix file that says "delete old version on install"?
The next best solution would be an option if y
28 matches
Mail list logo