WiX exposes (for the most part) all of the power of native Windows Installer. LaunchConditions are exposed by the Condition elements under the Product and Fragment elements and result in entries into the LaunchCondition table (http://msdn.microsoft.com/library/aa369752.aspx) which is processed by the built-in LaunchConditions action (http://msdn.microsoft.com/library/aa369751.aspx).
According to http://msdn.microsoft.com/library/aa369823.aspx merge modules can't supply LaunchCondition table rows. However, they can supply what are known as Type 19 custom actions. In WiX, type 19 custom actions are created by supplying the Id and Error attribute values to the CustomAction element, and then scheduling that action with one or two instances (usually two, one under the InstallIUSequence element and the other under the InstallExecuteSequence element) of the Custom element. -----Original Message----- From: Ken Halprin [mailto:khalp...@autosoln.com] Sent: Wednesday, December 09, 2009 11:58 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Conditions in merge modules To get a feel for how wix works, I created an installer project which produces an .msi file. It includes conditions at the Product level (are those launch conditions?) that check for os version and .net version, exiting the install if the condition is not met. I'll convert that project into a merge module project and would like to do the same checks. Would I need to put the condition checks on each feature to be installed? -----Original Message----- From: Blair [mailto:os...@live.com] Sent: Wednesday, December 09, 2009 12:38 PM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Conditions in merge modules Are you talking about LaunchConditions, Feature conditions, or Component conditions? You can't "isolate" your merge module parts in a final MSI very easily, but you should be able to condition any/all of your components and/or custom actions your merge module contributes. -----Original Message----- From: Ken Halprin [mailto:khalp...@autosoln.com] Sent: Wednesday, December 09, 2009 10:08 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Conditions in merge modules I'm creating a merge module for inclusion in another company's msi package. It does not appear to be possible to put conditions (such as checking operating system version or .net installed version) in the merge module. How is that generally handled? Thanks. ---------------------------------------------------------------------------- -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
