Thanks! I replaced the Package ID with the old Module GUID and deleted the Module GUID, and Wix seems to have kept the same module signature. It looks like the Package ID wasn't being used anywhere as long as there was a Module GUID so it doesn't matter that the Package ID changed.
Thanks again! John On Fri, Sep 24, 2010 at 4:01 PM, Christopher Painter <chr...@deploymentengineering.com> wrote: > Checkout an example at: > > http://iswix.codeplex.com/SourceControl/changeset/view/53668#841593 > > This module ends up having a signature of: > > IsWiXAddInMM.68061036_B1D9_4092_AD3B_DC569F3DD183 1033 1.0.0.0 > > and a package code of: {68061036-B1D9-4092-AD3B-DC569F3DD183} every time it > builds. This has no adverse side effects. > > > > Christopher Painter, Author of Deployment Engineering Blog > Have a hot tip, know a secret or read a really good thread that deserves > attention? E-Mail Me > > > > ----- Original Message ---- > From: Christopher Painter <chr...@deploymentengineering.com> > To: General discussion for Windows Installer XML toolset. > <wix-users@lists.sourceforge.net> > Sent: Fri, September 24, 2010 5:53:28 PM > Subject: Re: [WiX-users] Wix 3.5 Module GUID Deprecated > > Yes, what I was trying to say is that WiX v3 uses the Module Id along with > the > Package Id to create the Module.GUID you see in the ModuleSignature table. > Just build your old, tweak it up and build the new and you'll see they are the > same in Orca if you did it right. > > Christopher Painter, Author of Deployment Engineering Blog > Have a hot tip, know a secret or read a really good thread that deserves > attention? E-Mail Me > > > > ----- Original Message ---- > From: John Fry <j...@ifeats.com> > To: General discussion for Windows Installer XML toolset. > <wix-users@lists.sourceforge.net> > Sent: Fri, September 24, 2010 5:26:22 PM > Subject: Re: [WiX-users] Wix 3.5 Module GUID Deprecated > > Won't removing the module GUID change the module signature? > > If we have the following lines: > > <Module Id='OurModuleName' Guid='OLD_MODULE_GUID' ... > > <Package Id='PACKAGE_GUID' ... /> > > then the ModuleID field in the ModuleSignature table ends up as: > OurModuleName.OLD_MODULE_GUID > > If we remove the module GUID so it looks like: > > <Module Id='OurModuleName' ... > <!-- no GUID --> > <Package Id='PACKAGE_GUID' ... /> > > then the ModuleID field in the ModuleSignature table ends up as > OurModuleName.PACKAGE_GUID. > > Since older versions of our product are already installed with the > ModuleID of OurModuleName.OLD_MODULE_GUID, if a customer installs a > new version of our product that has a ModuleID of > OurModuleName.PACKAGE_GUID, won't the installer think it's a > different, new module (rather than upgrading the old module)? > > A potential solution seems to be changing the Package ID to the old > Module GUID so that the ModuleID ends up the same in newer versions, > but I'm not sure where else the Package ID gets used (i.e. if doing > this would cause even more problems). > > Thanks! > John > > On Fri, Sep 24, 2010 at 3:02 PM, Christopher Painter > <chr...@deploymentengineering.com> wrote: >> Merge modules are recognized by their Module Signature. I know of no purpose >> for the Summary Information Package Code other then it must have one becaues >> it's an MSI database. I know of no harm in changing it and this is probably >> the reason why the schema no longer requires it. >> >> Christopher Painter, Author of Deployment Engineering Blog >> Have a hot tip, know a secret or read a really good thread that deserves >> attention? E-Mail Me >> >> >> >> ----- Original Message ---- >> From: John Fry <j...@ifeats.com> >> To: wix-users@lists.sourceforge.net >> Sent: Fri, September 24, 2010 4:25:47 PM >> Subject: [WiX-users] Wix 3.5 Module GUID Deprecated >> >> Hello, >> >> We’re upgrading our build system from Wix 2.0 to 3.5 and are now >> getting the following warning: >> >> warning CNDL1088 : The Module/@Guid attribute is deprecated merge >> modules use their package code as the modularization guid. Use the >> Package/@Id attribute instead. >> >> We currently specify both a module GUID and a package ID – can we just >> remove the module GUID in future releases? Our “finished product” is a >> merge module that gets included in several different products, and we >> want to ensure that it’s recognized properly e.g. if a user installs a >> new product with an upgraded version of our service packaged in. >> >> Also, we’re currently hardcoding a GUID as the package ID and keeping >> it the same from release to release, is this correct? I didn’t see any >> other ID that was staying constant between releases that would >> associate a new version of our module with an older one. >> >> Any advice would be appreciated. >> >> Thanks! >> John Fry >> >> ------------------------------------------------------------------------------ >> Start uncovering the many advantages of virtual appliances >> and start using them to simplify application deployment and >> accelerate your shift to cloud computing. >> http://p.sf.net/sfu/novell-sfdev2dev >> _______________________________________________ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> >> >> >> >> >> ------------------------------------------------------------------------------ >> Start uncovering the many advantages of virtual appliances >> and start using them to simplify application deployment and >> accelerate your shift to cloud computing. >> http://p.sf.net/sfu/novell-sfdev2dev >> _______________________________________________ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
