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: > <Directory Id="INSTALLLOCATION" Name="$(var.ProductName)"> > > ... > > <Merge Id="Microsoft_VC90_CRT_x86" Language="1033" > SourceFile="Microsoft_VC90_CRT_x86.msm" DiskId="1" /> > > </Directory> > > <Feature Id="F_Complete" > > Title="$(var.ProductName) Setup" > > Level="1" > > Display="expand" > > Absent="disallow" > > AllowAdvertise="no" > > ConfigurableDirectory="INSTALLLOCATION" > <MergeRef > Id="Microsoft_VC90_CRT_x86" /> > > ... > > </Feature>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 +0000 > > > 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 > > > > > > *** Confidentiality Notice: This e-mail, including any associated or > > attached > files, is intended solely for the individual or entity to which it is > addressed. > This e-mail is confidential and may well also be legally privileged. If you > have > received it in error, you are on notice of its status. Please notify the > sender > immediately by reply e-mail and then delete this message from your system. > Please do not copy it or use it for any purposes, or disclose its contents to > any > other person. This email comes from a division of the Invensys Group, > owned by Invensys plc, which is a company registered in England and Wales > with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X > 7AW (Registered number 166023). For a list of European legal entities within > the Invensys Group, please go to > http://www.invensys.com/en/legal/default.aspx. > > > > You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail > recept...@invensys.com. This e-mail and any attachments thereto may be > subject to the terms of any agreements between Invensys (and/or its > subsidiaries and affiliates) and the recipient (and/or its subsidiaries and > affiliates). > > > > > > > > ------------------------------------------------------------------------------ > > 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
