You didn't read the comment from Heath just below Aaron's blog post :) "It's important to note that the policy MSM should be merged after the payload, if merged at all. It is recommended that you do not merge the policy MSM as this will redirect all applications depending on the related native assembly to that version. If you have no major reason to affect every application, merge only the payload MSM. I'll be doing a post or two on the situation as a whole very soon."
We also confirmed this before writing the topic on merging VC Redist into your installer for the How To in the WiX CHM. Neil -----Original Message----- From: Wilson, Phil [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 23, 2008 11:29 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Questions about using MFC Merge Module Are you sure? I was just reading Aaron Stebner's blog about building an MSI with WiX that includes the VC 8.0 merge modules and he includes the policy merge module. I don't believe this would change for VC 9.0. http://blogs.msdn.com/astebner/archive/2007/02/13/building-an-msi-using-wix-v3-0-that-includes-the-vc-8-0-runtime-merge-modules.aspx The policy file redirects people to use the newer version, so this might just be a "good citizen" choice to upgrade the system. The Dll merge modules contain multiple copies of files, that's why they increase the size. Orca reveals that Unicode and non-Unicode are also in there, plus versions of mfcm90.dll for Winforms integration. Phil Wilson -----Original Message----- From: Neil Enns [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 23, 2008 8:05 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Questions about using MFC Merge Module The answer to your last question is no, you do not need (and should not) include the policy modules. Neil ________________________________ From: Travis Burkitt [EMAIL PROTECTED] Sent: Tuesday, September 23, 2008 7:58 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Questions about using MFC Merge Module Hello, I am adding the VC 9.0 and the MFC 9.0 Merge modules to an installation. Previously I was directly including the required files in my application directory, but now I wanted to do it properly. Everything seems to work fine except that I would like to keep this install as small as possible and the install is now significantly larger. (previously was less than 3MB, but now it is almost 15Mb) Part of what is confusing me is that in that in my windows\winsxs directory I have 3 VC and 3 MFC directories (3 versions) x86_Microsoft.VC90.MFC_1fc8b3b9a1e18e3b_9.0.21022.8_x-ww_a173767a x86_Microsoft.VC90.MFC_1fc8b3b9a1e18e3b_9.0.30411.0_x-ww_421e9f78 x86_Microsoft.VC90.MFC_1fc8b3b9a1e18e3b_9.0.30729.1_x-ww_405b0943 The dlls in the 21022 directory are much smaller than those in the other two directories. (1.1Mb vs 3.6Mb) The MFC merge modules picking up the middle version 9.0.30411. My main questions are: - Why do I have an MFC merge module that is picking up the middle version of the 3 that are installed? (FYI the VC module does the same thing) - Is there a way to reduce the size of the msi file and still ensure that the necessary files are included for the end user? (e.g. any way to use version 9.0.21022.8 which likely has all I need and is much smaller?) - It isn't as clean, but is it acceptable to require users to download and install the MS VC++ 2008 Redistributable Package. - Also I need to use the policy merge modules? (e.g. policy_9_0_Microsoft_VC90_MFC_x86.msm) Thanks, Travis ------------------------------------------------------------------------- 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 ------------------------------------------------------------------------- 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
