[WiX-users] CabExtract returns 0x80070003

2015-07-09 Thread Edwin Castro
I'm trying to use CabExtract from cabutil.h (WiX v3.9) but I always get hr == 0x80070003 (The system cannot find the path specified). My code is equivalent to the following: hr = CabInitialize(false); hr = PathCreateTempDirectory(NULL, L"extract", 1, &tempDir); hr = PathConcat(tempDir, L"file.c

Re: [WiX-users] .NET Prerequisite, Burn, and the ARP

2015-07-09 Thread Rob Mensching
Cool. It's a very big feature. So you'll want to do all this first: http://wixtoolset.org/development/ Also, a WIP (http://wixtoolset.org/development/wips/-wix-improvement-proposal/) will definitely be in order. ___ FireGiant |

Re: [WiX-users] .NET Prerequisite, Burn, and the ARP

2015-07-09 Thread soundararajan dhakshinamoorthy
Hi, Added the issue , http://wixtoolset.org/issues/4822 We will try to contribute to the issue :-). Thanks, Sound On Thu, Jul 9, 2015 at 10:02 AM, Rob Mensching wrote: > Add feature to Burn. > > ___ > FireGiant | Dedicated support

Re: [WiX-users] Bootstrap conditioned on OSbittage

2015-07-09 Thread Matt O'Connell
Ah that's great, and I can hide the bundle ARP itself as well? On 09/07/2015 11:51, Pally Sandher wrote: > Unless the 3rd party installer is an MSI (which from your previous e-mails, > it appears they're executables), Burn won't do that regardless. > If it is an MSI you can set the Visible attrib

Re: [WiX-users] Bootstrap conditioned on OSbittage

2015-07-09 Thread Pally Sandher
Unless the 3rd party installer is an MSI (which from your previous e-mails, it appears they're executables), Burn won't do that regardless. If it is an MSI you can set the Visible attribute on the MsiPackage element to yes & it won't do it either. Palbinder Sandher Software Platform Engineer T

Re: [WiX-users] Bootstrap conditioned on OSbittage

2015-07-09 Thread Matt O'Connell
Thank David yes I agree with what your saying. I am a bit concerned the 3rd party wouldn't like our bundle 'wrapping' and hiding their ARP entry. Is it possible to only hide the bundles entry? dotNetInstaller looks good. (I was worried it was C# but the bootstrapper element is C++) . Ta On 09/

Re: [WiX-users] Bootstrap conditioned on OSbittage

2015-07-09 Thread David Watson
Hi, Experience has taught that the best experience for the user and for the developer and the support organisation is to follow the way that the burn bundle works, it has been very carefully designed. Fire and forget bootstrappers are an alternative (I used to use this many years ago http://dbl

[WiX-users] Publisher policy registry entries not cleaned up after an uninstall

2015-07-09 Thread kirannhegde
Hello, *Scenario:*I have a merge module which contains certain assemblies, which get installed into the GAC. This merge module is consumed by a msi package. The merge module also contains GAC publisher policy files associated with each of the assemblies. When the msi package is installed , seve

Re: [WiX-users] Bootstrap conditioned on OSbittage

2015-07-09 Thread Matt O'Connell
Well I only need to install one 3rd party installer based on os bittage. On x64- install a_64.exe else install a_32.exe I don't require downloader, and chainer engine for that. If I can use the burn chainer to do this AND get an effectively 'invisible' ARP for the un-avoidable bundle that would