Skip to main content

WiX - Windows Installer XML

Latest Release ('Rosario' November CTP msdn) now has Visual Studio Integration.
WiX Tutorial (tramontana).
WiX documentation (sourceforge).
WiX and Visual Studio (msdn forum).
WiX integration in Visual Studio using Votive (Votive blog).
WiX integration (msdn).
WiX Forum.
Building setup packages for Visual Studio project templates and starter kits (Aaron Stebner's WebBlog)
WiX Tallow tool

WiX is a methodology to write installers.
WiX has a compiler/linker (candle/light) which may give the installer writer some validation before deployment.
The contents of the end installer (.msi) are edited using an XML file.
I haven't found WiX to be advantageous over the ordinary Visual Studio Setup Project.
Visual Studios SDK has a project template (from Votive) for creating WiX installers. This project template gives you the skeletol wix file to start and the build commands are built into the project, all you've to do is create new GUIDs ,these guids are only for the installer, they've nothing to do with your applications GUIDs, the WiX compiler, candle.exe, will complain if you fail to change one anyway.
The addition of items to install is done be editing the WiX xml file! if you choose to use it with Visual Studio , the Votive version (present Wix 2) then you'll get Intellisence, that with the Candle compiler are very useful but editing xml files is very tedious.
You'll also note that this version does not support integrated Visual Sourcesafe in Visual Studio, I found this a disadvantage. However WiX 3 (presently in developer status) does have this but lacks other vital components at present, such as it does not support the gui components you require for user input in the installer. In WiX 2 these are provided by the SDK in the wixui.dll.

All in all I don't think WiX is up to scratch just yet but WiX 3 does look promising.

There's a tool now called Tallow which included in the WiX SDK, apparently it's a command line tool that allows you to create a WiX installer be passing in you file locations and registry settings on the command line.

WiX pre-processor table (these items can be added to your WiX file, they are replaced at compile time).

Preprocessor VariableExample Variable UseExample Variable Value
var.<Project>.ConfigurationName$(var.MyApp.ConfigurationName)Debug.NET
var.<Project>.ProjectDir$(var.MyApp.ProjectDir)C:\code\msdn\MyApp
var.<Project>.ProjectDosFileName$(var.MyApp.ProjectDosFileName)MYAPP.CSP
var.<Project>.ProjectExt$(var.MyApp.ProjectExt).csproj
var.<Project>.ProjectFileName$(var.MyApp.ProjectFileName)MyApp.csproj
var.<Project>.ProjectName$(var.MyApp.ProjectName)MyApp
var.<Project>.ProjectPath$(var.MyApp.ProjectPath)C:\code\msdn\MyApp\MyApp.csproj
var.<Project>.TargetDir$(var.MyApp.TargetDir)C:\code\msdn\MyApp\obj\Debug
var.<Project>.TargetDosFileName$(var.MyApp.TargetDosFileName)MYAPP.EXE
var.<Project>.TargetExt$(var.MyApp.TargetExt).exe
var.<Project>.TargetFileName$(var.MyApp.TargetFileName)MyApp.exe
var.<Project>.TargetName$(var.MyApp.TargetName)MyApp
var.<Project>.TargetPath$(var.MyApp.TargetPath)C:\code\msdn\MyApp\obj\Debug\MyApp.exe
var.SolutionDir$(var.SolutionDir)C:\code\msdn\MySetup
var.SolutionDosFileName$(var.SolutionDosFileName)MYSETUP.SLN
var.SolutionExt$(var.SolutionExt).sln
var.SolutionFileName$(var.SolutionFileName)MySetup.sln
var.SolutionName$(var.SolutionName)MySetup
var.SolutionPath$(var.SolutionPath)C:\code\msdn\MySetup\MySetup.sln
Labels:

Comments

Post a Comment

Popular posts from this blog

Installer CustomAction, Debugging the CustomAction, InstallState

Custom Action The Custom Action is added to the Setup Project, select the Project node and hit the Custom Action button. This allows you add an Action to a particular phase in the Installation. But first you must create the Custom Action. To Add a Custom Action you must first have a Custom Action created, this is usually in the form of a Installer Class, this should be created in a seperate project, the Installer Class is actually one of the File Templates in the C# Projects. So it's File->New Project and select Visual C# Projects. Then add a Class Library, this will prompt you for the Class Library Types , select "Installer Class". Walkthrough - Creating Custom Action (msdn). Also here's a more comprehensive document on Setup/Installer implementations, it delves into the Registry etc Getting Started with Setup Projects (SimpleTalk). Visual Studio Setup Projects and Custom Actions (Simple Talk). Create your Installer Class and then add it as a Custom Action to the ...
3 comments
Read more

dotNET - Debugging

Debugging with .NET MSIL assemblies Visual Studio and debugging the CLR are different, I'll talk about both. MSIL Assemblies Assemblies compiled with .NET tools such as the CLR compiler are compiled into a file which contains MSIL (Microsoft Intermediate Language). At runtime the contents of the assembly are loaded into the CLR and ran as machine code. When you compile an assembly in debug a PDB file is generated alongside the DLL or EXE you've just created. The link between these 2 files is that the PDB contains the line numbers of the methods and classes as well as the file names of the original source code that created the assembly. When you launch the debugger in Visual Studio the assembly is loaded into the Debugger (similar to the CLR) along with the PDB file. The debugger now uses your PDB file contents to match the running code found in the assembly to locations in source files (hopefully in your present project). CLR CLR Inside Out (msdn magazine) .NET Framework Tools:...
7 comments
Read more

BootStrapper BootStrapping

Bootstrapping is the creation of a wrapper installer around already existing installars or files. It's useful if you have multiple installation files that you'll like the user to install in on step. The Bootstrapper itself is a .exe installer file, it also may have .SED file which contains details of the contents of the .exe. There are a few applications out there to generate a bootstrapper, the most simple I've seen is the an app called IEXpress . IExpress Is actually installed on windows (System32/iexpress.exe). This creates an installer, you tell it what files you wish it to include in the installation. I've only played with this so far and it appears to me that the isntaller can only install upto 2 setup.exes. You can include as many files as you like, but the files cannot have the same name, because of this you will probably need to rename your setup.exes to something else because you cannot have 2 files with the same name. After you've included all the files...
1 comment
Read more