Wix 2013

exe setups bundles,.msi install packages,.msm merger module, and.msp patch.

WiX line-of-sight builds work with any automatic buildsystem. The WiX package contains several enhancements that provide features beyond those of Windows Installer. WiX, for example, can deploy IIS Web pages, generate SQL Server database files, and record exclusions in Windows Firewall, among other things. Burn, the WiX boatstrapper, lets you set up set-up packages that include requirements such as the .NET framework and other runtime applications with your own installation.

Using Burns you can either browse and browse packets or merge them into a unique executable. WiX SDK contains administered and natively available library files that make it easy to create Windows Installer-compatible writing, even user-defined operations in C# and C++.

Activate WiX in Visual Studio 2013 projects

2013-12-02 Update: WiX Tool Set 3.8 is officially supported for Visual Studio 2013 series. Visual Studio 2013 is compatible with older WiX versions: C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\Extensions\Microsoft\WiX\extension.vsixmanifest by manual activation by addition of the following: "12.0" Then open the command prompt RS2013 Native Tools (from C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Tools\Shortcuts) and run it:

If you open Visual Studio 2013, WiX 3.7 compatibility will work. I had to create all the Wix 3.8 and 3.9 data caches in Wix with 2012 and 2013 Cubes: Studio: "%appdata%..\Local\Microsoft\VisualStudio\11.0\ComponentModelCache" (for VS 2012) and "%appdata%..\Local\Microsoft\VisualStudio\12.0\ComponentModelCache" (for VS 2013). Once you have removed these directories, run the commands line for each VS version: e.g. "C:\Program files (x86)\Microsoft visual studio 12.0\Common7\IDE\devenv /setup" and "C:\Program file (x86)\Microsoft Visual Studio 11.0\Common7\IDE\devenv /setup". Only after I removed these directories and rebooted the computer, did running "devenv /setup" have the intended effect.

Failure to clear these caches first may result in a bug where your packets do not get loaded correctly. You' ll know if your package can't be loaded because VS fails badly at boot time. The latest Wix plumber seems to fix the install without configuring it. exclude all Visual Studio. run the .exe at https://wix.codeplex.com/releases/view/136891.