[WiX-users] Burn and uninstall condition for optional product

Hi all - I just changed one of our installers from the old VS2010 bootstrapper to the burn 3.7 and am generally liking it. I do have a question about the best way to approach one scenario though. The main product, let's call it Q, can have another optional product installed, say B. Ideally Q

[WiX-users] Uninstall bundle by name ?

Hi all - I've managed to upgrade some of our installs to Wix 3.7 with the burn bootstrapper, hooray ! One thing I haven't quite anticipated is this: after our automated build we need to push a newly-built installer to a test machine for an automated smoke/sanity test. First we need to

[WiX-users] Patch creation with Ngen ?

Hi all - we have an MSI with many DLL and a couple of EXE assemblies, the latter of which are nGen'd via netfx:NativeImage. We are getting ready to create a patch MSP using torch/pyro and wondering if we need to do anything explicit to re-nGen these EXE's. Thanks for any info ! -Rob

[WiX-users] heat extension - COM exe servers and 64-bit COM support

Hi all - about a year ago I wrote a heat extension (based on various code I found on the web) for our internal use which harvests 32-bit COM EXE servers and pre-initializes the registry with the ATL Registrar before harvesting. Lately I updated it with support for 64-bit COM servers (DLL and

[WiX-users] Wix 3.6: disable upgrades in burn ?

Hi all - really glad to see 3.6 is out ! We have an MSI with upgrade-related logic implemented by the MajorUpgrade element: Specifically, we don't want upgrades or downgrades to occur automatically (the user is prompted to use Add/Remove Programs instead). Here is an excerpt from Product.wxs

Re: [WiX-users] Burn: uninstalling an MSI

I'm not sure if my previous reply went through, so I'll try again. My first try was using the standard bootstrapper, and after looking through more of the source found that the UI level is being set in the engine in MsiEngineCalculateInstallLevel. There is related code in

[WiX-users] Burn: uninstalling an MSI

Hi all -- I've been tinkering with Wix 3.6 (build 2719), and set up a test bundle which installs a .msi package. I wanted the msi's user interface to be displayed, so I specified DisplayInternalUI=yes in MsiPackage. This all seems to work fine for installation. On uninstallation I wanted to

Re: [WiX-users] Burn: uninstalling an MSI

Some further research after looking at some logs : when I install the .msi via msiexec /I msiFileName.msi, CLIENTUILEVEL=0, which I guess is full UI. When uninstalling via the command line below, CLIENTUILEVEL=2 and UILevel=3 (INSTALLUILEVEL_BASIC). So I guess my question is how to get burn

Re: [WiX-users] BootStrapper Package for SQL CE 3.5?

Found under C:\Program Files\Microsoft SDKs\Windows\v7.0A\Bootstrapper\Packages\SQL Server Compact Edition This is part of the SDK for Win 7 .NET 3.5 SP1http://www.microsoft.com/download/en/details.aspx?displaylang=enid=3138. I would think it would be part of

[WiX-users] Error 1619

Hi, we have a .MSI created with Wix 3.5 which seems to work well for US computers. However, someone in Taiwan tried installing it from our intranet and received this error message box : This installation package could not be opened. Verify that the package exists and is accessible, or contact

[WiX-users] Patches: torch MSI or WIXPDB ?

Hi all - I've been experimenting with torch/pyro/patching on our Wix installer, which I'm proud to say has completely replaced InstallShield for our application. The thing I'm wondering about is this: do you have to use .wixpdb files as input to torch, or can you use .msi's instead ? The docs

Re: [WiX-users] Patches: torch MSI or WIXPDB ?

pyro/torch so that it has access to the files if you don't want to use wixpdb's. -- John Merryweather Cooper Jack Henry Associates, Inc. (Premier Tech, Inc.) Build Install Engineer - jXchange Office: 913-341-3434 x791011 JoCooper@... -Original Message- From: robert_yang

[WiX-users] Heat failing with HEAT5151

Hi all - we are suddenly having a problem with our build machine; Heat.exe is failing with HEAT5151 (could not load assembly), but only for assemblies which are exposed to COM. Regular COM DLL's, OCX's and typelibs are harvesting just fine. Someone installed .NET 4.0 on the build machine

Re: [WiX-users] Heat failing with HEAT5151

It seems to have been fixed on the build machine by swapping the order of the following lines in heat.exe.config : supportedRuntime version=v4.0 / supportedRuntime version=v2.0.50727 / I'm mystified, since this same config file works on my development box .. any ideas ?

[WiX-users] MajorUpgrade vs. InstallShield

Hi all - this is our company's first Wix installer, and so far it is working out very well. The older products have an upgrade code which we can use in the Wix Product element to detect major upgrades. There is just one problem: these older products use InstallShield (11.5 I think) and when

Re: [WiX-users] Major upgrade opt-out ?

Just wanted to say thanks for all the advice : the WIX_UPGRADE_DETECTED condition worked well. Sent: Monday, August 01, 2011 9:31 AM To: 'wix-users@lists.sourceforge.net' Subject: Major upgrade opt-out ? We would like to be able to uninstall an older product, and install the new version. I

[WiX-users] Major upgrade opt-out ?

We would like to be able to uninstall an older product, and install the new version. I tried out the MajorUpgrade element, and it works well. The only problem is that it seems to work silently .. apparently we need to be able to prompt the user and ask them if it's OK to perform the upgrade.

[WiX-users] HEAT5150 and ATL registrar

Hi all - I'm working on an install with a somewhat large number of older COM objects and .NET classes exposed to COM. For the most part, heat.exe works very well to move away from self-registration; very impressive. We have had some issues, like how to deal with the inability of heat to