Re: [WiX-users] UPGRADINGPRODUCTCODE is not working

> *No i tried that also. but still it is not working. that custom action is > throwing error. * *RemoveExistingProducts action sequenced incorrectly. i placed this after PublishProduct before installFinalise.* On Tue, Oct 21, 2008 at 5:59 PM, Amit Shrivastav <[EMAIL PROTECTED]>wr

Re: [WiX-users] UPGRADINGPRODUCTCODE is not working

lFinalize > > > Phil Wilson > > > -Original Message- > From: Amit Shrivastav [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 21, 2008 5:05 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] UPGRADINGPRODUCTCODE is not work

Re: [WiX-users] Problem in Upgrade scenario

> different. The only use for UPGRADINGPRODUCTCODE is when you don't want > custom action to run on upgrade. > > Alex > > > > -----Original Message- > From: Amit Shrivastav [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 21, 2008 2:56 PM > To: General

Re: [WiX-users] UPGRADINGPRODUCTCODE is not working

assembly\GAC_MSIL\x\1.0.0.0__31bf3856ad364e35\x.InstallState'. * does anybody have the idea on this? I will appreciate the help on this. Thanks Amit On Tue, Oct 21, 2008 at 5:05 PM, Amit Shrivastav <[EMAIL PROTECTED]>wrote: > original msi doen not contain that condition NOT UPGRADING

Re: [WiX-users] UPGRADINGPRODUCTCODE is not working

original msi doen not contain that condition NOT UPGRADINGPRODUCTCODE. Is this mandatory? Is there any other way so that i can stop executing that custom action in the uninstallation through Major upgrade. On Tue, Oct 21, 2008 at 4:57 PM, Amit Shrivastav <[EMAIL PROTECTED]>wrote: &g

Re: [WiX-users] UPGRADINGPRODUCTCODE is not working

stalled via major upgrade, you need the condition of NOT > UPGRADINGPRODUCTCODE to be in the original msi. It's not clear to me if you > have that condition in the original msi or the second msi. > > > -----Original Message- > From: Amit Shrivastav [mailto:[EMAIL PROTECTED

[WiX-users] UPGRADINGPRODUCTCODE is not working

Hi, I am trying to upgrade my installer using property *UPGRADINGPRODUCTCODE. *In the previous MSI it was not there. now In the latest version i.e. upgraded msi contains that version. I have an custom action in original msi which execute at the time of uninstallation. In the upgrade msi i dont wan

Re: [WiX-users] Problem in Upgrade scenario

d because > the condition is something like REMOVE="ALL". If you don't want the > uninstall custom action to run from your old uninstall if it's upgrading > than that uninstall needs to add the condition AND NOT UPGRADINGPRODUCTCODE. > > Phil Wilson > > -Ori

Re: [WiX-users] Problem in Upgrade scenario

Hi Richard, Any Suggestions? Thanks Amit On Mon, Oct 20, 2008 at 10:14 PM, Amit Shrivastav <[EMAIL PROTECTED]>wrote: > that custom action is present in old as well as new assembly. and also I am > putting assmblies in the GAC as well in the upgrade scenario. > > > On Mon,

Re: [WiX-users] Problem in Upgrade scenario

that custom action is present in old as well as new assembly. and also I am putting assmblies in the GAC as well in the upgrade scenario. On Mon, Oct 20, 2008 at 9:14 PM, Richard <[EMAIL PROTECTED]> wrote: > Does your InstallUtil based custom action depend on the *new* assemblies > you are trying

Re: [WiX-users] Problem in Upgrade scenario

:02 PM, Richard <[EMAIL PROTECTED]> wrote: > > In article <[EMAIL PROTECTED]>, >"Amit Shrivastav" <[EMAIL PROTECTED]> writes: > > > I am getting strange problem. I have added some custom actions on the > > previous MSI. That custom action is i

[WiX-users] Problem in Upgrade scenario

Hi All, I am getting strange problem. I have added some custom actions on the previous MSI. That custom action is invoked using installUtil.exe. When I am executing that MSI working fine in both installation and uninstallation scenario. Now I am upgrading my MSI using Major Upgrade. I want to exe

Re: [WiX-users] Major upgrade scenario problem

fore > upgrade and restore them after or you need to write custom action which will > read the changes from the Config files, preserve them somewhere (like > registry) and restore these values after upgrade. > > > Alex > > > -Original Message- > From: Amit Shr

[WiX-users] Major upgrade scenario problem

HI All, Here is the scenario i am working on. 1) I created a msi. it is deploying some binaries and config files to the system. 2) Now we are planning to give major upgrade of that product. In that we are modifying the binaries but not the config files. 3) In upgrade scenario if i am mentioning th

[WiX-users] Adding Major upgrade scenario

Hi, I am trying to do major upgrade on my previous installation. In that I have to upgrade some binaries and leave the config files as it is. For that if i use OnlyDetect="no" in upgrade table it is removing all the files including my config files. But if i use OnlyDetect="yes" in upgrade table it