Re: [WiX-users] WiX 3.6 Upgrade Leaves Files in Cache (v3.6.2520.0 to v3.6.2527.0)

Hi, Could you please help me to set the msi property values from BA.dll during installation. When i used to uninstall the setup by SyncBA.hwnd = IntPtr.Zero; SyncBA.Model.Engine.Plan(LaunchAction.Uninstall); SyncBA.Model.Engine.Apply(SyncBA.hwnd); but unable to uninstall the msi file. Tha

[WiX-users] Extracting embedded packages from the standard bootstrapper

If I do need to provide my customers access to the embedded msi files from a bootstrapper I would like to be able to extract them instead of needing to provide them separately. The standard bootstrapper comes close to being able to do this with the /layout command line parameter - it works great

[WiX-users] burn - UninstallCommand

Hi, I am starting to evaluate burn. I am trying to create a bundle that includes a 3rd party installer (not much control over it). It is an exe, so I created an ExePackage. Now, to uninstall that package, it seems like I need to run the unwise.exe that the installer put in the application's

Re: [WiX-users] Burn: Exe package can't find payload file that's not a dll.

I have the same issue. Allowing us to change directory would be good. Or at least have a property with the name of the cached folder, and a way to put that in the InstallCommand? Christophe. -- Live Security Virtual Co

Re: [WiX-users] Burn Failure 0x8007051b

Looks like this is a bug as I have now managed to reproduce it - if UAC is disabled and the user is not a local admin the code fails to request admin access (or block the install). Defect raised 3534925. Neil -Original Message- From: Neil Sleightholm [mailto:n...@x2systems.com] Sent: 1

Re: [WiX-users] Burn: Exe package can't find payload file that's not a dll.

In that case, I am not sure how to help you. It has been my experience that the exe is run from the cached location, so I don't know what is different for you. One thing that might be different is that the bundle I work with has lots of things to install, so we have placed all of the files in

Re: [WiX-users] Should you install 32-bit and 64-bit versions os the same application?

I agree with Peter. To be able to have tight control over these kinds of scenarios, I designed our 32-bit installer to explicitly prevent itself from being installed on a 64-bit O/S (using a simple launch condition). I then designed our 64-bit installer to install support for both 32-bit and 64-

[WiX-users] Install location for Wix 3.6

Hi, Is there a way to specify install location for Wix3.6. Currently i am using WiX Toolset v3.6.2221.0. It is getting installed under "C:\Program Files (x86)\Windows Installer XML v3.6". I want to change this while installing. Is that possible? Thanks, G.Subbiah -

Re: [WiX-users] light.exe error when merging VC100 merge modules for both x86 and x64

Bob Arnson-6 wrote > >> then how can a 64-bit operating system interogate a bespoke file format >> in >> order to draw a thumbnail preview when it is installed as part of a >> 32-bit >> package? > It can't. That requires a 64-bit package, as I said. The rules are that > a 32-bit package can cont

Re: [WiX-users] Should you install 32-bit and 64-bit versions os the same application?

There's no harm I can think of in offering both but you have to be certain that your application (and any third party add-ins) aren't contending for system resources which could result in data corruption or undesired behaviour. For instance, would both versions overwrite the same user settings file

Re: [WiX-users] Burn: Exe package can't find payload file that'snot a dll.

You could work around the issue by writing a small exe that changes the current directory then calls the troublesome exe, then use that as your exepackage and add the troublesome exe and txt as its payload. Maybe the wix team (or you) could implement a ExePackage@changeCurrentDirectory option, thi