Automatic account creation is now enabled. Captcha authentication required for account creation and editing unless you are trusted here.
WiX Development Methods
From WiX Wiki at MindCapers
Contents |
Command Line
Compiler
candle.exe ''sourcefile''.wxs
Linker
light.exe ''sourcefile''.wixobj
Decompiler
dark.exe ''sourcefile''.msi
dark.exe ''sourcefile''.msm
Other tools
- WixCop validates Wix source code. It can assist in converting Wix2 source code to Wix3.
- Smoke validates MSI files. You don't need to do this if you prepared the MSI file using light because light has built-in validation.
- Torch provides transformation support. The following command line creates a file
transform.mst
which can be used to transform target.msi to updated.msi - Pyro is a new tool for creating patch files. It is not really ready for prime time.
- Lit combines multiple object files into libraries that can be parsed by Light.
- Melt decompiles merge modules to component groups.
torch.exe target.msi updated.msi -out transform.mst
Votive
Votive doesn't present a user interface of its own. Rather, it allows use of the Wix tools via the Visual Studio interface. Requesting a build of a Wix project causes compiling and linking just as it does for C# or any other language.
Like most Visual Studio project types, Wix projects can present a tabbed property sheet. This is supported by Wix3 but not by Wix2. Request it as usual, by right-clicking on a project and selecting Properties from the context menu.
MSBuild
Use of MSBuild is very straightforward; at a command prompt, set the current directory to the folder containing a solution file, and issue theMSBUILDcommand. You don't need to specify any arguments; MSBuild searches the current directory for a solution file.
Preparing a solution file is another matter. The easiest way is to use Visual Studio.
Third Party Tools
These come into their own for creating custom UI.
