Only thing I can think of is to: A) privately deploy the VC runtime in your app folder, which leaves your app open to exploit B) Deploy the runtime as a prerequisite and eliminate the merge module
I'd shoot for B, though this means a non-admin user can't install your app if they are missing the VC runtime (may not be an issue, and not certain if burn can support conditionally not elevating) -----Original Message----- From: PKEuS [mailto:[email protected]] Sent: Thursday, October 25, 2012 3:57 PM To: [email protected] Subject: Re: [WiX-users] Major upgrade stops working after doing small changes and switching to 3.6 I finally found the solution (by trial&error): Its the VC CRT merge module I added. It requires per-machine install and thus whole install scope changes. Any ideas how to solve that (if possible with keeping installer per-user)? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Major-upgrade-stops-working-after-doing-small-changes-and-switching-to-3-6-tp7581476p7581600.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ WiX-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ WiX-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-users
