[WiX-users] How to supersede a minor update in next patch.

2015-03-24 Thread Kashif Md.
I created patches as explained further below. All patches contain MSIPatchSequence table. None of the patches are full file updates, they all contain file diff from previous target version. I want P3 to ignore/supersede P2 so that installer eliminates P2 when applying P3. P1 (v1.0.1) - Targets

Re: [WiX-users] Cannot install Wix - Wix39.exe

2015-03-24 Thread Phill Hogland
Error 0x80070005: Failed to run per-user mode. Seems interesting, I thought that both the VS2013 and the Wix toolset setups were per-machine, but I could be wrong. IF there are so many different wix-based setups which do not run, is there a Group policy or Security policy that is preventing

Re: [WiX-users] Cannot install Wix - Wix39.exe

2015-03-24 Thread Hoover, Jacob
Do you have any antivirus/anti-malware software on the machine in question? Something is preventing LoadLibraryW from loading the UX from the temp folder. -Original Message- From: Sean Hall [mailto:r.sean.h...@gmail.com] Sent: Monday, March 23, 2015 9:00 PM To: General discussion about

Re: [WiX-users] How to supersede a minor update in next patch.

2015-03-24 Thread Nir Bar
Is it not possible to create two patches to v1.0.3 - one applicable on v1.0.1 and the other on v1.0.2? - Nir Bar Freelance Developer Mail: nir@panel-sw.com Web: www.panel-sw.com - C++ On Windows, Linux and Embedded Platforms - WiX InstallShield -- View this message in

Re: [WiX-users] How to supersede a minor update in next patch.

2015-03-24 Thread Tunney, Stephen
If all have supercede set, then patch 1.0.3 would apply to BOTH 1.0.1 AND 1.0.2 as long as ProductCodes and UpgradeCodes match up. -Original Message- From: Nir Bar [mailto:nir@panel-sw.com] Sent: March-24-15 1:54 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] How to

Re: [WiX-users] How to supersede a minor update in next patch.

2015-03-24 Thread Skildum, Mat
I do not think this is possible when dealing with binary patches. This is because the binary differences are going to be specific to the base package the patch was built against. You will always have to have individual patches to jump over versions in this case. This is why using binary

Re: [WiX-users] Prevent run of Custom action if product is installed.

2015-03-24 Thread Sarvagya Pant
@Nir, Yep I figured that out. I used REMOVE~=ALL based on Rob's answer given at http://stackoverflow.com/a/321874/2634612 . On Tue, Mar 24, 2015 at 12:30 PM, Nir Bar nir@panel-sw.com wrote: You should use REMOVE, not Remove - case matters. - Nir Bar Freelance Developer Mail:

Re: [WiX-users] Prevent run of Custom action if product is installed.

2015-03-24 Thread Nir Bar
You should use REMOVE, not Remove - case matters. - Nir Bar Freelance Developer Mail: nir@panel-sw.com Web: www.panel-sw.com - C++ On Windows, Linux and Embedded Platforms - WiX InstallShield -- View this message in context:

Re: [WiX-users] Cannot install Wix - Wix39.exe

2015-03-24 Thread ctludlow
Thanks all for your answers, I think you're on the right track. I installed Wix fine about a month ago on my work PC here and wrote an installer package and finished it. I went to reinstall Visual Studio 2013 and noticed the installer would not launch neither from the file system or from Control