As long as your entire organization is using Wix to build their deployments.
Chris On Mon, Aug 11, 2008 at 1:22 AM, Blair Murri <[EMAIL PROTECTED]> wrote: > I don't know if anyone has mentioned this already, but the Windows > Installer team has been trying to deprecate Merge Modules almost ever since > they created them. > > If you don't have to distribute your merge modules to external customers, > you should consider using WixLibs instead of Merge Modules. They are much > easier to work with. > > ________________________________________ > From: [EMAIL PROTECTED] [ > [EMAIL PROTECTED] On Behalf Of Cristian Libardo [ > [EMAIL PROTECTED] > Sent: Tuesday, August 05, 2008 7:31 AM > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] ps:SnapIn > > Hi. I've been diving into the amazing world of wix and I just came to the > point where I could use some help (newbie alert). > > We have a setup with two solutions. One that builds merge modules. The > other > that picks the previously generated msm:s and creates msi:s. > > My problem occurs when I use the <ps:SnapIn extension. It seems that > certain > registry values aren't bound as they should somewhere during the process. > Using orca I can see that the Version key is > "!(bind.assemblyVersion.MyAssembly.dll)" in both the intermediate msm and > the final msi (that value is inserted in the registry when I install). > > I have tried Andy Burgess tips: > > http://ajbdeveloper.blogspot.com/2008/01/i-recently-tried-to-create-wix-msi.html > > I've also created a minimal wixproject with the same assembly and this > works > like a charm. > > And an excerpt from the wxs file: > ... > <Directory Id="Tools" Name="Tools" > FileSource="$(var.AssemblyRootPath)\$(var.Configuration)\"> > <Component Id="MyAssembly.dll" Guid="..."> > <File Id="MyAssembly.dll" Name="MyAssembly.dll" > Assembly=".net" KeyPath="yes"> > <ps:SnapIn Id="MyAssembly.SnapIn" Description="Installer > Cmdlets" Vendor="..." /> > </File> > </Component> > </Directory> > ... > > Any ideas on what might be the culprit? > I noticed that the minimal project defines a <wix><product...> while the > complete one defines a <wix><module...>. At what stage is the version > information supposed to be bound? > > Thanks > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
