OK, I did a little testing and the results surprised me because the "working" solution goes against the advice of not including the policy MSM.
Scenarios are as follows, all on Windows XP SP 3: - No MSMs, run the vcredist_x86.exe, install my application, my app launches - Payload MSM, install my application, my app doesn't launch. => then run vcredist_x86.exe, my app launches - Payload MSM + Policy MSM, install my application, my app launches This seems to imply that I *need* the policy MSM in order to launch my application. I'm not sure what the policy MSM is doing, but I noticed that it is also installed by the vcredist_x86.exe installer. Am I doing something wrong, or do I really need the policy MSM? -- "The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download <http://legalizeadulthood.wordpress.com/the-direct3d-graphics-pipeline/> Legalize Adulthood! <http://legalizeadulthood.wordpress.com> ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
