Re: [WiX-users] Major upgrade stops working after doing small changes and switching to 3.6

2012-10-25 Thread PKEuS
Your previous install was per user, the new install is per machine, and one will not upgrade the other. The Windows default if unspecified is per user, so perhaps if you never set it in the original install it defaulted to per user. The question is: Why has the new one a different setting? I

Re: [WiX-users] Major upgrade stops working after doing small changes and switching to 3.6

2012-10-25 Thread PKEuS
I finally found the solution (by trialerror): 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:

Re: [WiX-users] Major upgrade stops working after doing small changes and switching to 3.6

2012-10-25 Thread Hoover, Jacob
working after doing small changes and switching to 3.6 I finally found the solution (by trialerror): 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

Re: [WiX-users] Major upgrade stops working after doing small changes and switching to 3.6

2012-10-25 Thread Rob Mensching
[mailto:philipp.kl...@web.de] Sent: Thursday, October 25, 2012 3:57 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Major upgrade stops working after doing small changes and switching to 3.6 I finally found the solution (by trialerror): Its the VC CRT merge module I added. It requires

Re: [WiX-users] Major upgrade stops working after doing small changes and switching to 3.6

2012-10-21 Thread PKEuS
Has nobody an idea what (and why) is going wrong? As far as I can see, it doesn't find the old installation because of conflicting InstallScope. But I have no idea, why install scope is different (even if I explicitly set it). -- View this message in context:

Re: [WiX-users] Major upgrade stops working after doing small changes and switching to 3.6

2012-10-21 Thread Phil Wilson
- it may show why you got a per user install if you weren't expecting one. Phil W -Original Message- From: PKEuS [mailto:philipp.kl...@web.de] Sent: Sunday, October 21, 2012 2:50 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Major upgrade stops working after doing

[WiX-users] Major upgrade stops working after doing small changes and switching to 3.6

2012-10-19 Thread PKEuS
Hello, First of all, sorry for posting this a second time, but my first post (via nabble) seems to have been rejected, because I hadn't received subscription confirmation mail before. I am a dev of the cppcheck project and I am trying to improve our installer. We are using WiX, and the original

[WiX-users] Major upgrade stops working after doing small changes and switching to 3.6

2012-10-19 Thread PKEuS
Hello, I am a dev of the cppcheck project and I am trying to improve our installer. We are using WiX, and the original installer was built using WiX 3.5. You can see the original installer code here: https://github.com/danmar/cppcheck/tree/master/win_installer I switched to WiX 3.6(.3303), made

Re: [WiX-users] Major upgrade stops working after doing small changes and switching to 3.6

2012-10-19 Thread Rob Mensching
If theUpgradeCode is stable then I don't see anything obvious. What does verbose logfile for update show? On Fri, Oct 19, 2012 at 9:05 AM, PKEuS philipp.kl...@web.de wrote: Hello, First of all, sorry for posting this a second time, but my first post (via nabble) seems to have been rejected,

Re: [WiX-users] Major upgrade stops working after doing small changes and switching to 3.6

2012-10-19 Thread PKEuS
You can find verbose log file here: http://kloke-witten.dyndns.org/~philipp/Temp/msi_log.zip There are some lines about finding related products, where it says FindRelatedProducts: current install is per-machine. Related install for product '{1CC8C271-A877-4DF0-B1DE-C1B7D83521BC}' is per-user.