Re: [WiX-users] Std Bootstrapper failed: Error

Now this defect is reproducible on all our tester machines. The weirdest thing it that simple verification of any file, signed with company certificate, on the problem computer repels defect ^^ (signtool.exe verify /pa anySignedFile.exe). I added comment to the defect https://sourceforge.net/trac

Re: [WiX-users] How to check the Registry with ?

Custom Actions are an MSI concept so you would need to do your oracle detection and configuration custom action inside a bundled MSI. Alternatively you could write your configuration as a standalone tool and add that to the bundle as a .exe package. -Original Message- From: Tobias S [mail

Re: [WiX-users] Strange InstallExecuteSequence errors (ICE27) with WixUI_Advanced

Bob Arnson-6 wrote: > > WixUI_Advanced is the only dialog set that includes something in > InstallExecuteSequence. So it pulls in some values that conflict with > the bad sequences from the merge module. > If the merge modules alone (without the Advanced UI) don't produce these ICE validation

[WiX-users] APPLICATIONFOLDER vs INSTALLDIR

I like the Advanced UI more than Mondo for most things. It cuts down on clicks and superfluous dialogs for the most common use cases. I'm curious why WixUI_Advanced uses APPLICATIONFOLDER instead of the well-known INSTALLDIR property which Mondo and other popular msi build technologies use? I'm

[WiX-users] 64-bit burn?

Hi Everyone, I need to call a unmanaged 64-bit .DLL method from my managed bootstrapper using P/Invoke. As such I am trying to get Wix to compile my setup.exe as a 64-bit executable. I tried editing the .wixproj file changing x86 to x64. This gets Visual Studio to allow me to select the setup proj

Re: [WiX-users] APPLICATIONFOLDER vs INSTALLDIR

john.burak wrote: > > I like the Advanced UI more than Mondo for most things. It cuts down on > clicks and superfluous dialogs for the most common use cases. > > I'm curious why WixUI_Advanced uses APPLICATIONFOLDER instead of the > well-known INSTALLDIR property which Mondo and other popular m

[WiX-users] Downloading and installing optional components

I apologize in advance for asking a vague question. I'm going to make this as precise as I can, but it's still open-ended enough to give Google fits. I'm an almost-complete newb to WiX, but a long-time Python programmer. I'd like to distribute an MSI containing a Python application written using

Re: [WiX-users] Downloading and installing optional components

This is exactly what Burn is for in WIX v3.6. That'll keyword will probably get you some really good hits in Bing. On Wed, Sep 7, 2011 at 3:01 PM, Robert J. Hansen wrote: > I apologize in advance for asking a vague question. I'm going to make > this as precise as I can, but it's still open-ende

Re: [WiX-users] 64-bit burn?

Burn is not available for 64bit yet. It is not as simple as changing a couple settings in configuration manager. The "Could not find part of the path" is a bug in a recent build of WiX v3.6. 64-bit Bundles (aka: Burn that only runs on 64-bit, not Bundles that install 64-bit stuff) are not yet suppo

Re: [WiX-users] 64-bit burn?

Thank you for the prompt reply as usual Rob. :) I was doing some stuff with the Windows Embedded 7 Enhanced Write Filter API as part of the installer I am working on and ewfapi.dll is an OS .DLL so it's only 64-bit. I found a nice little workaround by spawning the ewfmgr.exe process. It's not as id