wix3.6

In my custom Burn managed bootstrapper application, I want a way to set the default log directory of the installer so that customers can easily find the installation logs. If this can't be done, I would like a suitable way to copy the log files after installation. I tried unsuccessfully at setting the WixBundleLog variable in my setup project (i.e. Bundle.wxs) and in my managed bootstrapper application. Also, my bootstrapper applicaton is generic enough so that it my be used with a variety of products / install packages, so I need a solution that is flexible enough to set / get the

To give you a background - I have a 4 MSI's which comes from our vendor and this has to go to our company servers (we are looking at around 3500 servers). As of now, my counterparts are managing this using vbs, ps1 scripts. But the problem with the script is that everytime an update comes we have to worry about uninstalling the existing package before running the new one and a ton of hardcoding. I want to automate the whole process (with very less hardcoding) by setting up a WIX script to package all the 4 MSI's together. I read about the WIX bundle and used that to create a single MSI. But

I have one MSI setup like this: <Product Id="*" ... UpgradeCode="4207FF3B-5E0D-4311-9DFC-B41AA8DE2965" /> <MajorUpgrade DowngradeErrorMessage="Can't downgrade" /> It works as expected: Install product Recompile (effectively generating a new Id) Starting the new msi file brings up the change view and I can repair or uninstall the product. Good. But then comes burn. I have created the most simplistic Bundle one can thing of. I use the standard bootrapper and just add one single MsiPackage: <MsiPackage SourceFile="$(var.Setup.TargetPath)" /> The problem is that after each recompile I can install

I need to use custom action to load items into combobox. UI.wxs: <Control Id="Server" Type="ComboBox" X="30" Y="65" Width="200" Height="18" Property="DATABASE_SERVER"> <ComboBox Property="DATABASE_SERVER"> <ListItem Text="[DATABASE_SERVER]" Value="[DATABASE_SERVER]" /> </ComboBox> <Publish Property="LOGON_VALID" Value="0">1</Publish> </Control> Custom Action private static ActionResult EnumSqlServersIntoComboBox(Session session, IEnumerable<DataRow> rows) { try { Debugger.Break(); session.Log("EnumSQLServers: Begin"); // Grab the combo box but make sure I'm getting only the one // from

I tried to construct a working example of a WiX 3.6 installation script. We currently use WiX 3.5 and now we would like to begin installing the .NET 4 Client Profile framework as a pre-requisite for our MSI file that our product.wxs script creates. WiX 3.6 seems like the best way forward. Is there a functional example of how to do this with WiX 3.6? Here is our 3.5 script we use today: <?xml version="1.0" encoding="utf-8"?> <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi" xmlns:util="http://schemas.microsoft.com/wix/UtilExtension"> <!-- Version change handling --> <?define UpgradeCode="##

When installing an application that can use either .NET 4.0 or 4.5, what is the best practice when installing the prerequisites .NET framework? And how do you implement it using Burn in WiX? These are the options and trade-offs that I am aware of: Option 1: Install .NET 4.0 (just what you need) Advantages: None known (except for Windows XP, where this is the only choice) Option 2: Install .NET 4.5 if .NET 4.5 is not present Advantages: User won't have to install .NET 4.5 later for future apps. App won't experience a .NET version change when user later does upgrade to .NET 4.5. App immediately