WixSharp_wix4.bin 2.0.3

There is a newer version of this package available.
See the version list below for details.
dotnet add package WixSharp_wix4.bin --version 2.0.3
NuGet\Install-Package WixSharp_wix4.bin -Version 2.0.3
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="WixSharp_wix4.bin" Version="2.0.3" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add WixSharp_wix4.bin --version 2.0.3
#r "nuget: WixSharp_wix4.bin, 2.0.3"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install WixSharp_wix4.bin as a Cake Addin
#addin nuget:?package=WixSharp_wix4.bin&version=2.0.3

// Install WixSharp_wix4.bin as a Cake Tool
#tool nuget:?package=WixSharp_wix4.bin&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 Compatible and additional computed target framework versions.
.NET Framework net is compatible. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (2)

Showing the top 2 NuGet packages that depend on WixSharp_wix4.bin:

Package Downloads
WixSharp_wix4

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 WixSharp binaries. If you need only Wix# binaries you may want to use WixSharp.bin package instead. 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

WixSharp-wix4.WPF

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

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
2.1.7 89 5/27/2024
2.1.6 490 5/1/2024
2.1.5 2,346 4/6/2024
2.1.2 1,422 3/4/2024
2.1.1 317 2/25/2024
2.1.0 388 2/15/2024
2.0.6-pre 141 1/25/2024
2.0.5 463 1/21/2024
2.0.4 667 12/14/2023
2.0.3 298 12/6/2023
2.0.2 2,091 10/20/2023
2.0.1 1,863 8/22/2023
2.0.0 2,359 8/13/2023
1.21.0-pre 431 4/23/2023

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).