NetCore: Release v2.1.3.0

This release specifically delivers .NET Core Visual Studio integration. No functionality changes comparing to v2.1.2.

---

• added project templates
• improved error reporting during compilation.
• added full CustomUI sample

WiX4: Release v2.0.5.0

• Feature condition support in managed UI #1430
• Added support for condition evaluation and custom installlevel settings.
• Issue #1431: Hidden NullReferenceException in Extensions.GetEmbeddedData
• Enhancement #1401: Can't mark the directory as permanent
• PR#1408 (special thanks to @NJullienSweet):
  • added a sample for signing bundles
  • fixed SigningBundle sample project

WiX3-Release v1.24.2.0

• WiX3: improvements triggered by #1424
• Feature condition support in managed UI #1430
• Added support for condition evaluation and custom installlevel settings.
• Issue #1405: Can't make LookupInstalledVersion work
• added test case for Issue #1403
• updated the WPF BA sample to show the solution for #1400
• Enhancement #1401: Can't mark directory as permanent

WiX4-Release v2.0.4.0

• #1363: Shortcut to Dir/Folder
• #1398: Underscore in String Id in wxl breaks localization
• reverted experimental change for x86 bitness of WixSharp.UI. Now it's back to AnyCPU but SilentUI BA will no longer work. It's acceptable as it's better to set x86 on the user codebase (e.g. custom BA) than on generic lib (WixSharp.UI) and put bitness pressure on all users of this lib.
• WarnOnOutputPathCollision changed from Warning to Error (continuation of #1384).
• Extended cascading Project.Platform to RegistrySearch (triggered by #1390 discussion).

WiX3-Release v1.24.1.0

SHA-1: dc5717d

• #1363: Shortcut to Dir/Folder
• #1398: Underscore in String Id in wxl breaks localization
• reverted experimental change for x86 bitness of WixSharp.UI. Now it's back to AnyCPU but SilentUI BA will no longer work. It's acceptable as it's better to set x86 on the user codebase (e.g. custom BA) than on generic lib (WixSharp.UI) and put bitness pressure on all users of this lib.
• WarnOnOutputPathCollision changed from Warning to Error (continuation of #1384).
• Extended cascading Project.Platform to RegistrySearch (triggered by #1390 discussion).

WiX4: Release v2.0.3.0

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

WiX3-Release v1.24.0.0

v1.24.0.0

• Issue #1392: Is it possible to inherit wxl files using managed UI?
• Issue #1389: Multi language installer intermediate .msi not found error
• Issue #1387: Cannot update to latest Caliburn.Micro
• Issue #1384: When the bootstrapper.Build API uses the same name as the project, then misleading compile warnings are issued
• Issue #1382: Package (all child elements of Chain) need to have the After field added
• Issue #1383: Package (all child elements of Chain) need to have the SuppressSignatureVerification field added
• Issue #1381: ExePackage needs to have the Protocol field implemented
• Issue #1379: A way (Or create an example) of how to create a standalone fragment and insert into Projects / chains / etc
• Issue #1377: WixSharp.wix.bin nuget references a url which is no longer available
• Issue #1372: Creating a FileAssociation with Icon and Advertised = false does not work
• Validation of the CPU architecture for the custom BA assembly.
• Updated default BootstrapperCore.config content
• Updated WixBootstrapper_UI sample to demonstrate how to use the WinForm-based custom BA (#1386)
• Added support for ManagedUI to foll back on the stock WXL if one was not supplied by the user for non-English languages
• Added WXL and theme files to be used in WixSharp.wix.bin package.
• Added support for ManagedUI to fall back on the stock WXL if one was not supplied by the user for non-English languages
• Improved multi-language sample
• Updated project templates to comment out webref package for bootstrapper template
• Added WixStandardBootstrapperApplication.AddPayload

v1.23.0.0

• NuGet packages are updated to .NET Framework v4.6.2; v4.5.1 assemblies are also included in the package
• Issue #1366: What is the purpose of StartArguments in the .targets file (see linked code)
• Issue #1358: XML exception when run CustomMSIDialog sample
• Issue #1328: Strange focus on the taskbar
• Issue #1326: Library erased after update
• Added Tasks.UnelevateAfterInstallEvent
• Added Session.PersistData for securely persisting data between sessions; Triggered by Issue #1029.
• Updated MajorUpgrade sample

WiX3: Release v1.23.0.0-PRE

• NuGet packages are updated to .NET Framework v4.6.2; v4.5.1 assemblies are also included in the package
• Issue #1366: What is the purpose of StartArguments in the .targets file (see linked code)
• Issue #1358: XML exception when run CustomMSIDialog sample
• Issue #1328: Strange focus on the taskbar
• Issue #1326: Library erased after update
• Added Tasks.UnelevateAfterInstallEvent
• Added Session.PersistData for securely persisting data between sessions; Triggered by Issue #1029.
• Updated MajorUpgrade sample

WiX4: Release v2.0.1.0

• Issue #1329: the sample of Install on x64 generate a msi which installs components to Program Files (x86)
• Ported some method extensions from the WiX3 codebase.
• Added project.UnelevateAfterInstallEvent() API
• WixSharp binaries re-targeted for target runtime v4.7.2
• Added Session.PersistData for securely persisting data between sessions; Triggered by Issue #1029.

Release v2.0.0.0

WixSharp release for WiX4.

System Requirements:

• .NET runtime v7.0 or higher must be installed.
• WiX4 toolset: dotnet tool install --global wix

Limitations:

WixSharp just drops these features because they have no direct support in WiX4:

• Package.InstallPrivileges
• Publish.Condition
• Package.Languages no longer exists
• WixSharp.DriverInstaller is based on now deprecated element. WiX4 offers no guidance on how to deal with it.
• <CustomAction Id="VBScript" Script="vbscript" ...>
• <Package Platform="x64" is illegal but not even picked by wix convert; doc says Component.Bitness may have the value default which means "will be installed using the same bitness as the package". But the package element does not have bitness attribute. WixSharp maintains Project.Platform property but does not convert it in the Package.Platform while still cascades it to the Component.Bitness

UPDATE: WixSharp templates for WiX4 have been published on marketplace.

Keeping the section below just in case if some users experience the problems with Visual Studio projects.

Until VS templates are released use this simple technique for creating the projects

Any WixSharp project except WPF UI:

1. In VS create "Console App" project targeting .NET Framework v4.7.2 .
   Note: ensure you did not accidentally use "Console App (.NET Framework)"
2. Add the required nuget package WixSharp-wix4.2.0.0.0 or WixSharp-wix4.bin.2.0.0.0
3. Setup post-build event command:

   cd .\
   set ide=true
   "$(TargetPath)"
   

   

This is the sample project with similar settings.

WixSharp project for WPF UI

1. Copy this sample project
2. Add nuget package WixSharp-wix4.WPF2.0.0.0
3. Remove reference to any WixSharp project (it is a leftover from the sample referencing).

Consult WixSarp (WiX4) code samples as you go.