Re: [WiX-users] majorupgrade when signing and merge
I wish this was mentioned in the MajorUpgrade planning guide. I put so much efforts into planning MajorUpgrade but I totally unforseen this one. How can I uninstall the existing per user previous installations of my program now?Thanks,Martin > Date: Sat, 8 Oct 2011 16:11:54 -0400 > From: b...@joyofsetup.com > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] majorupgrade when signing and merge > > On 06-Oct-11 19:53, Martin Kulov wrote: > > files in ProgramFiles, Windows and ProgramData. Should it install per-user > > or per-machine mode? > > Per-machine; the big reason to use per-user packages is so they don't > require elevation. > > -- > sig://boB > http://joyofsetup.com/ > > > -- > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2dcopy2 > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] majorupgrade when signing and merge
On 06-Oct-11 19:53, Martin Kulov wrote: > files in ProgramFiles, Windows and ProgramData. Should it install per-user or > per-machine mode? Per-machine; the big reason to use per-user packages is so they don't require elevation. -- sig://boB http://joyofsetup.com/ -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] majorupgrade when signing and merge
indeed when I open the original MSI file with Orca ALLUSERS property is missing
(i.e. it is per-user mode).now I open the MSI file with the merge module inside
and I see ALLUSERS property is set to 1 (i.e. per-machine)there is no other
change in the WiX file so it must have been set automatically somehow when I
added the merge modulecorrection... I just opened the .msm file and the only
one property inside it is ALLUSERS=1. They must have a reason setting it up to
1. Can I override the ALLUSERS property set with the MSM file? My installer
puts files in ProgramFiles, Windows and ProgramData. Should it install per-user
or per-machine mode?
Now my MSI file is working in per-machine mode and it cannot upgrade the
existing per-user installations. What is it right way of removing existing
installations before installing the new one?Thank you so much!
Martin Kulov
Microsoft Regional Director
VS ALM MVP, MCT, INETA Speaker
www.kulov.net | (+359) 88 821 3255
> From: edwin.cas...@fiserv.com
> To: wix-users@lists.sourceforge.net
> Date: Thu, 6 Oct 2011 18:21:37 -0400
> Subject: Re: [WiX-users] majorupgrade when signing and merge
>
> Sounds like your original package was per-user. The VC9 merge module very
> likely accesses per-machine locations. That merge module must have required
> that you change the package to per-machine so that it compiled successfully.
>
> If your source control system does not show any other changes then perhaps
> the per-user/per-machine setting wasn't set then WiX might have picked a
> "smart" default based on the contents of the package. I don't know if WiX
> would really do that...
>
> Edwin G. Castro
> Software Developer - Staff
> Digital Channels
> Fiserv
> Office: 503-746-0643
> Fax: 503-617-0291
> www.fiserv.com
> Please consider the environment before printing this e-mail
>
> > -Original Message-
> > From: Martin Kulov [mailto:mar...@kulov.net]
> > Sent: Thursday, October 06, 2011 2:55 PM
> > To: wix-users
> > Subject: Re: [WiX-users] majorupgrade when signing and merge
> >
> >
> > So I guess you were right. Here is excerpt of the log: MSI (c) (D8:18)
> > [14:49:27:908]: Doing action: FindRelatedProducts MSI (c) (D8:18)
> > [14:49:27:908]: Note: 1: 2205 2: 3: ActionText Action 14:49:27:
> > FindRelatedProducts. Searching for related applications Action start
> > 14:49:27:
> > FindRelatedProducts.
> > MSI (c) (D8:18) [14:49:27:908]: FindRelatedProducts: current install is per-
> > machine. Related install for product '{AB5B1162-D4DE-4C59-BAB3-
> > 020B2323AF98}' is per-user. Skipping...
> > MSI (c) (D8:18) [14:49:27:908]: FindRelatedProducts: current install is per-
> > machine. Related install for product '{AB5B1162-D4DE-4C59-BAB3-
> > 020B2323AF98}' is per-user. Skipping...
> > Action ended 14:49:27: FindRelatedProducts. Return value 1.
> > I do not get it why adding an MSM merge module will have any effect on the
> > per-machine vs per-user mode. How can I fix it back to per-machine mode?
> > Thanks,
> >
> >
> > Martin Kulov
> > Microsoft Regional Director
> > VS ALM MVP, MCT, INETA Speaker
> > www.kulov.net | (+359) 88 821 3255
> >
> >
> > > From: phil.wil...@invensys.com
> > > To: wix-users@lists.sourceforge.net
> > > Date: Thu, 6 Oct 2011 13:17:06 -0400
> > > Subject: Re: [WiX-users] majorupgrade when signing and merge
> > >
> > > Two entries in Add/Remove Programs usually means you tried to upgrade a
> > per-system product with a per-user install, or vuice versa (all other things
> > being correct to do the upgrade). A verbose log will say something near the
> > FindRelatedProducts action.
> >
> > >
> > > Phil Wilson
> > >
> > > -Original Message-
> > > From: Martin Kulov [mailto:mar...@kulov.net]
> > > Sent: Thursday, October 06, 2011 3:59 AM
> > > To: John Robbins; wix-users
> > > Subject: Re: [WiX-users] majorupgrade when signing and merge
> > >
> > >
> > > So I verified that digitally signing the MSI does NOT break MajorUpgrade
> > process and product gets upgraded just fine.Also adding the MSM Merge
> > module DOES break MajorUpgrade process.When I add the following two
> > lines Merge and MergeRef I end up with two installations of my product:
> >
> > > ...
> > > > SourceFile="Microsoft_VC90_CRT_x86.msm" DiskId="1" />
> > >
> > > > > Title="$(var.ProductName) Setup"
> > > Level="1"
> > >
Re: [WiX-users] majorupgrade when signing and merge
Some of those VC merge modules have a Property table with ALLUSERS=1, so that
will do it. If you're using a bootstrapper maybe you could run the VC9 redist
executable instead of using merge modules.
Phil Wilson
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Thursday, October 06, 2011 3:22 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] majorupgrade when signing and merge
Sounds like your original package was per-user. The VC9 merge module very
likely accesses per-machine locations. That merge module must have required
that you change the package to per-machine so that it compiled successfully.
If your source control system does not show any other changes then perhaps the
per-user/per-machine setting wasn't set then WiX might have picked a "smart"
default based on the contents of the package. I don't know if WiX would really
do that...
Edwin G. Castro
Software Developer - Staff
Digital Channels
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
Please consider the environment before printing this e-mail
> -Original Message-
> From: Martin Kulov [mailto:mar...@kulov.net]
> Sent: Thursday, October 06, 2011 2:55 PM
> To: wix-users
> Subject: Re: [WiX-users] majorupgrade when signing and merge
>
>
> So I guess you were right. Here is excerpt of the log: MSI (c) (D8:18)
> [14:49:27:908]: Doing action: FindRelatedProducts MSI (c) (D8:18)
> [14:49:27:908]: Note: 1: 2205 2: 3: ActionText Action 14:49:27:
> FindRelatedProducts. Searching for related applications Action start 14:49:27:
> FindRelatedProducts.
> MSI (c) (D8:18) [14:49:27:908]: FindRelatedProducts: current install is per-
> machine. Related install for product '{AB5B1162-D4DE-4C59-BAB3-
> 020B2323AF98}' is per-user. Skipping...
> MSI (c) (D8:18) [14:49:27:908]: FindRelatedProducts: current install is per-
> machine. Related install for product '{AB5B1162-D4DE-4C59-BAB3-
> 020B2323AF98}' is per-user. Skipping...
> Action ended 14:49:27: FindRelatedProducts. Return value 1.
> I do not get it why adding an MSM merge module will have any effect on the
> per-machine vs per-user mode. How can I fix it back to per-machine mode?
> Thanks,
>
>
> Martin Kulov
> Microsoft Regional Director
> VS ALM MVP, MCT, INETA Speaker
> www.kulov.net | (+359) 88 821 3255
>
>
> > From: phil.wil...@invensys.com
> > To: wix-users@lists.sourceforge.net
> > Date: Thu, 6 Oct 2011 13:17:06 -0400
> > Subject: Re: [WiX-users] majorupgrade when signing and merge
> >
> > Two entries in Add/Remove Programs usually means you tried to upgrade a
> per-system product with a per-user install, or vuice versa (all other things
> being correct to do the upgrade). A verbose log will say something near the
> FindRelatedProducts action.
>
> >
> > Phil Wilson
> >
> > -----Original Message-
> > From: Martin Kulov [mailto:mar...@kulov.net]
> > Sent: Thursday, October 06, 2011 3:59 AM
> > To: John Robbins; wix-users
> > Subject: Re: [WiX-users] majorupgrade when signing and merge
> >
> >
> > So I verified that digitally signing the MSI does NOT break MajorUpgrade
> process and product gets upgraded just fine.Also adding the MSM Merge
> module DOES break MajorUpgrade process.When I add the following two
> lines Merge and MergeRef I end up with two installations of my product:
>
> > ...
> > SourceFile="Microsoft_VC90_CRT_x86.msm" DiskId="1" />
> >
> > > Title="$(var.ProductName) Setup"
> > Level="1"
> > Display="expand"
> > Absent="disallow"
> > AllowAdvertise="no"
> > ConfigurableDirectory="INSTALLLOCATION" > Id="Microsoft_VC90_CRT_x86" />
> > ...
> > Moving the merge module in another feature does not help
> either. Any ideas? Thanks,Martin
> >
> > > From: mar...@kulov.net
> > > To: j...@wintellect.com; wix-users@lists.sourceforge.net
> > > Date: Thu, 6 Oct 2011 09:58:17 +
> > > Subject: Re: [WiX-users] majorupgrade when signing and merge
> > >
> > >
> > > Hey John,nice to hear from you :) Yes, I did change the Product Id and
> Version. I used to publish 3 more upgrades already. However when I digitally
> signed the MSI, integrated a merge module and changed the Package
> InstallerVersion from 200 to 300 now the upgrade is not recognizing the old
> version. I keep the UpgradeCode the same. I will try adding the changes one
> by one and see what the problem is. Thanks
Re: [WiX-users] majorupgrade when signing and merge
Sounds like your original package was per-user. The VC9 merge module very
likely accesses per-machine locations. That merge module must have required
that you change the package to per-machine so that it compiled successfully.
If your source control system does not show any other changes then perhaps the
per-user/per-machine setting wasn't set then WiX might have picked a "smart"
default based on the contents of the package. I don't know if WiX would really
do that...
Edwin G. Castro
Software Developer - Staff
Digital Channels
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
Please consider the environment before printing this e-mail
> -Original Message-
> From: Martin Kulov [mailto:mar...@kulov.net]
> Sent: Thursday, October 06, 2011 2:55 PM
> To: wix-users
> Subject: Re: [WiX-users] majorupgrade when signing and merge
>
>
> So I guess you were right. Here is excerpt of the log: MSI (c) (D8:18)
> [14:49:27:908]: Doing action: FindRelatedProducts MSI (c) (D8:18)
> [14:49:27:908]: Note: 1: 2205 2: 3: ActionText Action 14:49:27:
> FindRelatedProducts. Searching for related applications Action start 14:49:27:
> FindRelatedProducts.
> MSI (c) (D8:18) [14:49:27:908]: FindRelatedProducts: current install is per-
> machine. Related install for product '{AB5B1162-D4DE-4C59-BAB3-
> 020B2323AF98}' is per-user. Skipping...
> MSI (c) (D8:18) [14:49:27:908]: FindRelatedProducts: current install is per-
> machine. Related install for product '{AB5B1162-D4DE-4C59-BAB3-
> 020B2323AF98}' is per-user. Skipping...
> Action ended 14:49:27: FindRelatedProducts. Return value 1.
> I do not get it why adding an MSM merge module will have any effect on the
> per-machine vs per-user mode. How can I fix it back to per-machine mode?
> Thanks,
>
>
> Martin Kulov
> Microsoft Regional Director
> VS ALM MVP, MCT, INETA Speaker
> www.kulov.net | (+359) 88 821 3255
>
>
> > From: phil.wil...@invensys.com
> > To: wix-users@lists.sourceforge.net
> > Date: Thu, 6 Oct 2011 13:17:06 -0400
> > Subject: Re: [WiX-users] majorupgrade when signing and merge
> >
> > Two entries in Add/Remove Programs usually means you tried to upgrade a
> per-system product with a per-user install, or vuice versa (all other things
> being correct to do the upgrade). A verbose log will say something near the
> FindRelatedProducts action.
>
> >
> > Phil Wilson
> >
> > -Original Message-
> > From: Martin Kulov [mailto:mar...@kulov.net]
> > Sent: Thursday, October 06, 2011 3:59 AM
> > To: John Robbins; wix-users
> > Subject: Re: [WiX-users] majorupgrade when signing and merge
> >
> >
> > So I verified that digitally signing the MSI does NOT break MajorUpgrade
> process and product gets upgraded just fine.Also adding the MSM Merge
> module DOES break MajorUpgrade process.When I add the following two
> lines Merge and MergeRef I end up with two installations of my product:
>
> > ...
> > SourceFile="Microsoft_VC90_CRT_x86.msm" DiskId="1" />
> >
> > > Title="$(var.ProductName) Setup"
> > Level="1"
> > Display="expand"
> > Absent="disallow"
> > AllowAdvertise="no"
> > ConfigurableDirectory="INSTALLLOCATION" > Id="Microsoft_VC90_CRT_x86" />
> > ...
> > Moving the merge module in another feature does not help
> either. Any ideas? Thanks,Martin
> >
> > > From: mar...@kulov.net
> > > To: j...@wintellect.com; wix-users@lists.sourceforge.net
> > > Date: Thu, 6 Oct 2011 09:58:17 +
> > > Subject: Re: [WiX-users] majorupgrade when signing and merge
> > >
> > >
> > > Hey John,nice to hear from you :) Yes, I did change the Product Id and
> Version. I used to publish 3 more upgrades already. However when I digitally
> signed the MSI, integrated a merge module and changed the Package
> InstallerVersion from 200 to 300 now the upgrade is not recognizing the old
> version. I keep the UpgradeCode the same. I will try adding the changes one
> by one and see what the problem is. Thanks,Martin
> > >
> > > > From: j...@wintellect.com
> > > > To: wix-users@lists.sourceforge.net; mar...@kulov.net
> > > > Date: Wed, 5 Oct 2011 17:20:29 -0700
> > > > Subject: RE: [WiX-users] majorupgrade when signing and merge
> > > >
> > > > Hi Martin,
> > > >
> > > > Did you change the Product ID and the version number? Both of those
> have to change to be called a major upgra
Re: [WiX-users] majorupgrade when signing and merge
So I guess you were right. Here is excerpt of the log: MSI (c) (D8:18)
[14:49:27:908]: Doing action: FindRelatedProducts
MSI (c) (D8:18) [14:49:27:908]: Note: 1: 2205 2: 3: ActionText
Action 14:49:27: FindRelatedProducts. Searching for related applications
Action start 14:49:27: FindRelatedProducts.
MSI (c) (D8:18) [14:49:27:908]: FindRelatedProducts: current install is
per-machine. Related install for product
'{AB5B1162-D4DE-4C59-BAB3-020B2323AF98}' is per-user. Skipping...
MSI (c) (D8:18) [14:49:27:908]: FindRelatedProducts: current install is
per-machine. Related install for product
'{AB5B1162-D4DE-4C59-BAB3-020B2323AF98}' is per-user. Skipping...
Action ended 14:49:27: FindRelatedProducts. Return value 1.
I do not get it why adding an MSM merge module will have any effect on the
per-machine vs per-user mode. How can I fix it back to per-machine mode?
Thanks,
Martin Kulov
Microsoft Regional Director
VS ALM MVP, MCT, INETA Speaker
www.kulov.net | (+359) 88 821 3255
> From: phil.wil...@invensys.com
> To: wix-users@lists.sourceforge.net
> Date: Thu, 6 Oct 2011 13:17:06 -0400
> Subject: Re: [WiX-users] majorupgrade when signing and merge
>
> Two entries in Add/Remove Programs usually means you tried to upgrade a
> per-system product with a per-user install, or vuice versa (all other things
> being correct to do the upgrade). A verbose log will say something near the
> FindRelatedProducts action.
>
> Phil Wilson
>
> -Original Message-
> From: Martin Kulov [mailto:mar...@kulov.net]
> Sent: Thursday, October 06, 2011 3:59 AM
> To: John Robbins; wix-users
> Subject: Re: [WiX-users] majorupgrade when signing and merge
>
>
> So I verified that digitally signing the MSI does NOT break MajorUpgrade
> process and product gets upgraded just fine.Also adding the MSM Merge module
> DOES break MajorUpgrade process.When I add the following two lines Merge and
> MergeRef I end up with two installations of my product: Id="INSTALLLOCATION" Name="$(var.ProductName)">
> ...
> SourceFile="Microsoft_VC90_CRT_x86.msm" DiskId="1" />
>
> Title="$(var.ProductName) Setup"
> Level="1"
> Display="expand"
> Absent="disallow"
> AllowAdvertise="no"
> ConfigurableDirectory="INSTALLLOCATION" > Id="Microsoft_VC90_CRT_x86" />
> ...
> Moving the merge module in another feature does not help either.
> Any ideas? Thanks,Martin
>
> > From: mar...@kulov.net
> > To: j...@wintellect.com; wix-users@lists.sourceforge.net
> > Date: Thu, 6 Oct 2011 09:58:17 +
> > Subject: Re: [WiX-users] majorupgrade when signing and merge
> >
> >
> > Hey John,nice to hear from you :) Yes, I did change the Product Id and
> > Version. I used to publish 3 more upgrades already. However when I
> > digitally signed the MSI, integrated a merge module and changed the Package
> > InstallerVersion from 200 to 300 now the upgrade is not recognizing the old
> > version. I keep the UpgradeCode the same. I will try adding the changes one
> > by one and see what the problem is. Thanks,Martin
> >
> > > From: j...@wintellect.com
> > > To: wix-users@lists.sourceforge.net; mar...@kulov.net
> > > Date: Wed, 5 Oct 2011 17:20:29 -0700
> > > Subject: RE: [WiX-users] majorupgrade when signing and merge
> > >
> > > Hi Martin,
> > >
> > > Did you change the Product ID and the version number? Both of those have
> > > to change to be called a major upgrade.
> > >
> > > http://wix.sourceforge.net/manual-wix3/major_upgrade.htm shows how to
> > > integrate a major upgrade into your .WXS file.
> > >
> > > John
> > > Wintellect
> > > http://www.wintellect.com
> > > +1-877-968-5528
> > >
> > >
> > > -Original Message-
> > > From: Martin Kulov [mailto:mar...@kulov.net]
> > > Sent: Wednesday, October 05, 2011 2:59 PM
> > > To: wix-users
> > > Subject: [WiX-users] majorupgrade when signing and merge
> > >
> > >
> > > Hi,
> > >
> > > I have an MSI installer built few months ago. It used to work fine during
> > > MajorUpgrade.
> > >
> > > Today I signed the MSI with code certificate and also added one Merge
> > > Module. However now my MSI file gets installed as a new product and does
> > > not upgrade the existing installation as it used to do. As usual I only
> > > changed ProductCode and CurrentVersion prop
Re: [WiX-users] majorupgrade when signing and merge
Two entries in Add/Remove Programs usually means you tried to upgrade a per-system product with a per-user install, or vuice versa (all other things being correct to do the upgrade). A verbose log will say something near the FindRelatedProducts action. Phil Wilson -Original Message- From: Martin Kulov [mailto:mar...@kulov.net] Sent: Thursday, October 06, 2011 3:59 AM To: John Robbins; wix-users Subject: Re: [WiX-users] majorupgrade when signing and merge So I verified that digitally signing the MSI does NOT break MajorUpgrade process and product gets upgraded just fine.Also adding the MSM Merge module DOES break MajorUpgrade process.When I add the following two lines Merge and MergeRef I end up with two installations of my product: ... ... Moving the merge module in another feature does not help either. Any ideas? Thanks,Martin > From: mar...@kulov.net > To: j...@wintellect.com; wix-users@lists.sourceforge.net > Date: Thu, 6 Oct 2011 09:58:17 + > Subject: Re: [WiX-users] majorupgrade when signing and merge > > > Hey John,nice to hear from you :) Yes, I did change the Product Id and > Version. I used to publish 3 more upgrades already. However when I digitally > signed the MSI, integrated a merge module and changed the Package > InstallerVersion from 200 to 300 now the upgrade is not recognizing the old > version. I keep the UpgradeCode the same. I will try adding the changes one > by one and see what the problem is. Thanks,Martin > > > From: j...@wintellect.com > > To: wix-users@lists.sourceforge.net; mar...@kulov.net > > Date: Wed, 5 Oct 2011 17:20:29 -0700 > > Subject: RE: [WiX-users] majorupgrade when signing and merge > > > > Hi Martin, > > > > Did you change the Product ID and the version number? Both of those have to > > change to be called a major upgrade. > > > > http://wix.sourceforge.net/manual-wix3/major_upgrade.htm shows how to > > integrate a major upgrade into your .WXS file. > > > > John > > Wintellect > > http://www.wintellect.com > > +1-877-968-5528 > > > > > > -Original Message----- > > From: Martin Kulov [mailto:mar...@kulov.net] > > Sent: Wednesday, October 05, 2011 2:59 PM > > To: wix-users > > Subject: [WiX-users] majorupgrade when signing and merge > > > > > > Hi, > > > > I have an MSI installer built few months ago. It used to work fine during > > MajorUpgrade. > > > > Today I signed the MSI with code certificate and also added one Merge > > Module. However now my MSI file gets installed as a new product and does > > not upgrade the existing installation as it used to do. As usual I only > > changed ProductCode and CurrentVersion properties. > > > > Does digital signing or adding merge module makes the MSI look like a new > > product? > > What else could be the case? > > > > Thanks, > > Martin > > > > -- > > All the data continuously generated in your IT infrastructure contains a > > definitive record of customers, application performance, security threats, > > fraudulent activity and more. Splunk takes this data and makes sense of it. > > Business sense. IT sense. Common sense. > > http://p.sf.net/sfu/splunk-d2dcopy1 > > ___ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > -- > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2dcopy1 > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ WiX-users mailing list WiX-users@lists.sourceforge.
Re: [WiX-users] majorupgrade when signing and merge
So I verified that digitally signing the MSI does NOT break MajorUpgrade process and product gets upgraded just fine.Also adding the MSM Merge module DOES break MajorUpgrade process.When I add the following two lines Merge and MergeRef I end up with two installations of my product: ... ... Moving the merge module in another feature does not help either. Any ideas? Thanks,Martin > From: mar...@kulov.net > To: j...@wintellect.com; wix-users@lists.sourceforge.net > Date: Thu, 6 Oct 2011 09:58:17 + > Subject: Re: [WiX-users] majorupgrade when signing and merge > > > Hey John,nice to hear from you :) Yes, I did change the Product Id and > Version. I used to publish 3 more upgrades already. However when I digitally > signed the MSI, integrated a merge module and changed the Package > InstallerVersion from 200 to 300 now the upgrade is not recognizing the old > version. I keep the UpgradeCode the same. I will try adding the changes one > by one and see what the problem is. Thanks,Martin > > > From: j...@wintellect.com > > To: wix-users@lists.sourceforge.net; mar...@kulov.net > > Date: Wed, 5 Oct 2011 17:20:29 -0700 > > Subject: RE: [WiX-users] majorupgrade when signing and merge > > > > Hi Martin, > > > > Did you change the Product ID and the version number? Both of those have to > > change to be called a major upgrade. > > > > http://wix.sourceforge.net/manual-wix3/major_upgrade.htm shows how to > > integrate a major upgrade into your .WXS file. > > > > John > > Wintellect > > http://www.wintellect.com > > +1-877-968-5528 > > > > > > -Original Message----- > > From: Martin Kulov [mailto:mar...@kulov.net] > > Sent: Wednesday, October 05, 2011 2:59 PM > > To: wix-users > > Subject: [WiX-users] majorupgrade when signing and merge > > > > > > Hi, > > > > I have an MSI installer built few months ago. It used to work fine during > > MajorUpgrade. > > > > Today I signed the MSI with code certificate and also added one Merge > > Module. However now my MSI file gets installed as a new product and does > > not upgrade the existing installation as it used to do. As usual I only > > changed ProductCode and CurrentVersion properties. > > > > Does digital signing or adding merge module makes the MSI look like a new > > product? > > What else could be the case? > > > > Thanks, > > Martin > > > > -- > > All the data continuously generated in your IT infrastructure contains a > > definitive record of customers, application performance, security threats, > > fraudulent activity and more. Splunk takes this data and makes sense of it. > > Business sense. IT sense. Common sense. > > http://p.sf.net/sfu/splunk-d2dcopy1 > > ___ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > -- > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2dcopy1 > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] majorupgrade when signing and merge
Hey John,nice to hear from you :) Yes, I did change the Product Id and Version. I used to publish 3 more upgrades already. However when I digitally signed the MSI, integrated a merge module and changed the Package InstallerVersion from 200 to 300 now the upgrade is not recognizing the old version. I keep the UpgradeCode the same. I will try adding the changes one by one and see what the problem is. Thanks,Martin > From: j...@wintellect.com > To: wix-users@lists.sourceforge.net; mar...@kulov.net > Date: Wed, 5 Oct 2011 17:20:29 -0700 > Subject: RE: [WiX-users] majorupgrade when signing and merge > > Hi Martin, > > Did you change the Product ID and the version number? Both of those have to > change to be called a major upgrade. > > http://wix.sourceforge.net/manual-wix3/major_upgrade.htm shows how to > integrate a major upgrade into your .WXS file. > > John > Wintellect > http://www.wintellect.com > +1-877-968-5528 > > > -Original Message- > From: Martin Kulov [mailto:mar...@kulov.net] > Sent: Wednesday, October 05, 2011 2:59 PM > To: wix-users > Subject: [WiX-users] majorupgrade when signing and merge > > > Hi, > > I have an MSI installer built few months ago. It used to work fine during > MajorUpgrade. > > Today I signed the MSI with code certificate and also added one Merge Module. > However now my MSI file gets installed as a new product and does not upgrade > the existing installation as it used to do. As usual I only changed > ProductCode and CurrentVersion properties. > > Does digital signing or adding merge module makes the MSI look like a new > product? > What else could be the case? > > Thanks, > Martin > > -- > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security threats, > fraudulent activity and more. Splunk takes this data and makes sense of it. > Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2dcopy1 > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] majorupgrade when signing and merge
Hi Martin, Did you change the Product ID and the version number? Both of those have to change to be called a major upgrade. http://wix.sourceforge.net/manual-wix3/major_upgrade.htm shows how to integrate a major upgrade into your .WXS file. John Wintellect http://www.wintellect.com +1-877-968-5528 -Original Message- From: Martin Kulov [mailto:mar...@kulov.net] Sent: Wednesday, October 05, 2011 2:59 PM To: wix-users Subject: [WiX-users] majorupgrade when signing and merge Hi, I have an MSI installer built few months ago. It used to work fine during MajorUpgrade. Today I signed the MSI with code certificate and also added one Merge Module. However now my MSI file gets installed as a new product and does not upgrade the existing installation as it used to do. As usual I only changed ProductCode and CurrentVersion properties. Does digital signing or adding merge module makes the MSI look like a new product? What else could be the case? Thanks, Martin -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] majorupgrade when signing and merge
Hi, I have an MSI installer built few months ago. It used to work fine during MajorUpgrade. Today I signed the MSI with code certificate and also added one Merge Module. However now my MSI file gets installed as a new product and does not upgrade the existing installation as it used to do. As usual I only changed ProductCode and CurrentVersion properties. Does digital signing or adding merge module makes the MSI look like a new product? What else could be the case? Thanks, Martin -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
