WixSharp-wix4.WPF
2.0.3
See the version list below for details.
dotnet add package WixSharp-wix4.WPF --version 2.0.3
NuGet\Install-Package WixSharp-wix4.WPF -Version 2.0.3
<PackageReference Include="WixSharp-wix4.WPF" Version="2.0.3" />
paket add WixSharp-wix4.WPF --version 2.0.3
#r "nuget: WixSharp-wix4.WPF, 2.0.3"
// Install WixSharp-wix4.WPF as a Cake Addin
#addin nuget:?package=WixSharp-wix4.WPF&version=2.0.3
// Install WixSharp-wix4.WPF as a Cake Tool
#tool nuget:?package=WixSharp-wix4.WPF&version=2.0.3
Wix# is a framework for building a complete MSI or WiX source code by using build script files written with the C# syntax.
The package contains Wix# binaries only.
In order to use this package you need have WiX Toolset installed: `dotnet tool install --global wix`
The package is tested against WIX (Windows Installer Xml) Toolset v4.0.1.0
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NETPlatform | dotnet is compatible. |
-
- Caliburn.Micro (>= 3.2.0)
- WixSharp_wix4.bin (>= 2.0.3)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
Release v2.0.3.0
- Added `Compiler.VerboseOutput`
- Release WixSharp.VSIX v2.1.0
- Made split on WiX3 vs WiX4 templates
- Added Bootstrapper Custom BA templates
- `WarnOnOutputPathCollision` changed from Warning to Error (continuation of #1384).
- Extended cascading `Project.Platform` to `RegistrySearch` (triggered by #1390 discussion).
- Issue #1392: Is it possible to inherit wxl files using managed UI?
- Added support for ManagedUI to foll back on the stock WXL if one was not supplied by the user for non-English languages
- Added handling new WiX constant `PFiles` (same as old `ProgramFilesFolder`)
- added `WixStandardBootstrapperApplication.AddPayload`
- #1387: Cannot update to latest Caliburn.Micro
- #1384: When the bootstrapper.Build API uses the same name as the project, then misleading compile warnings are issued
- #1379: A way (Or create an example) of how to create a standalone fragment and insert into Projects / chains / etc
- #1382: Package (all child elements of Chain) need to have the After field added (2)
- #1382: Package (all child elements of Chain) need to have the After field added
- #1383: Package (all child elements of Chain) need to have the SuppressSignatureVerification field added
- #1381: ExePackage needs to have the Protocol field implemented
- #1372: Creating a FileAssociation with Icon and Advertised = false does not work
- #1373: Need a clearer reason for the following Build exception: "System.NullReferenceException: Object reference not set to an instance of an object."
- Added ensuring `project.OutDir` exists.
- Updated WixToolset.Dtf.WindowsInstaller to the latest version
- `WarnOnOutputPathCollision` changed from Warning to Error (continuation of #1384).
- Extended cascading `Project.Platform` to `RegistrySearch` (triggered by #1390 discussion).