I'll have to let those people on this list that are more knowledgeable than I about merge modules guide you as to whether there are better ways for you to proceed. With my limited knowledge what you have looks fine. I would recommend you convert the merge modules to wixlibs at the time or shortly thereafter you convert the MSI projects to WiX, however.
-----Original Message----- From: Bill Packard [mailto:bill.pack...@kepware.com] Sent: Wednesday, January 06, 2010 6:44 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Shortcut path for Merge modules Blair, The merge modules are internal only. At this point I am expecting to convert all merge modules to wix, but initially leave the msi projects in Wise. The merge modules are simple, only a few have more than payload and resources. The msi projects are significantly more involved and will require more time than I have right now. I can currently create a more or less identical merge module with either wise or wix, and have written a script to transform the wise merge module projects to wix source. Wise lets certain things pass, such as global properties, that wix allows but warns about (SuppressModularization). I'm just trying to figure out the best way to implement with wix functionality that effectively duplicates what we can do with wise. I don't think that wixlibs are a possibility at this point, though might be once all the msi projects are converted as well. Oh, and I am using wix 3.0.5419.0. Thanks, bill -----Original Message----- Date: Tue, 5 Jan 2010 14:39:51 -0800 From: "Blair" <os...@live.com> Subject: Re: [WiX-users] Shortcut path for Merge modules To: "'General discussion for Windows Installer XML toolset.'" <wix-users@lists.sourceforge.net> Message-ID: <blu111-ds309f76d62b2f5f8e91372cd...@phx.gbl> Content-Type: text/plain; charset="us-ascii" What you don't say is whether what you ship are the merge modules themselves or if you simply use them as internal "global" libraries for the MSIs you build. You also don't say whether you are porting all at once or in stages. -----Original Message----- From: Bill Packard [mailto:bill.pack...@kepware.com] Sent: Tuesday, January 05, 2010 9:55 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Shortcut path for Merge modules I am evaluating whether I can port our installations from Wise to Wix. We have several merge modules, each of which contains a set of files and a couple of shortcuts. In the Wise definition we use a global property to define the shortcut path for the merge modules. I can use the substitution tables to tweak the directory table, and use the global property, but was wondering if there was some other (better) way to accomplish this? <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi";> <Module Id="MyMergeModule" Language="1033" Version="2.0"> <!-- This block replaces the parent directory (in the Directory table) of SMHelp directory entry. This allows the user defined Start Menu property to be used for the shortcuts. --> <Configuration Name="SMPRODNAME" Format="Key" Type="Identifier" DefaultValue="SMPRODNAME" Description="Start Menu Path" DisplayName="Start Menu Folder"/> <Substitution Table="Directory" Column="Directory_Parent" Row="SMHelp" Value="[=SMPRODNAME]"/> <Directory Id="TARGETDIR" Name="SourceDir"> <!-- Set up Directory for Start Menu --> <!-- SMHelp is reparented to SMPRODNAME --> <Directory Id="SMHelp" Name="Help Documentation" ShortName="HELPDOC" /> <Directory Id="MergeRedirectFolder" > <!-- other files here --> <!-- Help files --> <Directory Id="Help" Name="Help" > <Component Id="MyComponent.chm" Guid="*"> <!-- Start Menu shortcut to help file --> <Shortcut Id="MYCOMPHelpSC" Directory="SMHelp" Name="My Component Help" Advertise="no" Target="{00000000-0000-0000-0000-000000000000}" Hotkey="0" Show="normal" IconIndex="0"/> </Component> </Directory> </Directory> </Directory> </Module> </Wix> When the merge module is merged into the msi the directory table is updated and the user defined property SMPRODNAME (set in UI sequence) becomes the parent of the SMHelp directory. I am simply wondering if there is some other way to accomplish this? Thanks, Bill ---------------------------------------------------------------------------- -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ 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 Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
