See the version list below for details.
Requires NuGet 2.7 or higher.
Install-Package WiX.Toolset.UnofficialFork -Version 3.10.2
dotnet add package WiX.Toolset.UnofficialFork --version 3.10.2
<PackageReference Include="WiX.Toolset.UnofficialFork" Version="3.10.2" />
paket add WiX.Toolset.UnofficialFork --version 3.10.2
#r "nuget: WiX.Toolset.UnofficialFork, 3.10.2"
// Install WiX.Toolset.UnofficialFork as a Cake Addin #addin nuget:?package=WiX.Toolset.UnofficialFork&version=3.10.2 // Install WiX.Toolset.UnofficialFork as a Cake Tool #tool nuget:?package=WiX.Toolset.UnofficialFork&version=3.10.2
This package contains the binaries needed to compile Windows Installer XML (WiX) setup projects. Just add this NuGet package to your WiX setup projects and you're done (no setup required on build servers etc.). Note that you still need to install WiX Toolset in Visual Studio to get the editor experience.
File issues with the NuGet package at https://github.com/jozefizso/WiX.Toolset.NuGet
This package has no dependencies.
This package is not used by any NuGet packages.
This package is not used by any popular GitHub repositories.
WiX v3.10.2 is the latest recommended maintenance release of WiX v3.10 with a series of mitigations for a serious Windows vulnerability affecting all bootstrapper bundles. We strongly recommend upgrading to WiX v3.10.2 so you can ship safe bundles.
For more information about the vulnerabilities, the mitigations, and the release, see https://www.firegiant.com/blog/2016/1/20/wix-v3.10.2-released/
There are two breaking changes due to this security fix:
* A bundle cannot be named Setup.exe. When an executable is named Setup.exe, Windows loads additional DLLs in an insecure manner. To prevent such a guaranteed vulnerability, Light.exe now yields an error if the bundle output is named Setup.exe. As Setup.exe might be a common file name, this breaking change is especially annoying. Unfortunately, Windows loads the additional DLLs in a way that Burn code cannot mitigate.
* The process that loads the bootstrapper application is no longer the process the user started. Attempts to use ::GetModuleFileName to locate the source media (i.e., with loose files next to the bundle .exe) will fail. A workaround is to use the new WixBundleSourceProcessPath and WixBundleSourceProcessFolder variables to find the original process. In general, this shouldn't be a serious problem--bootstrapper applications can already carry all the files they need using Payload elements.