Welcome to Round Three! Previously, we announced the availability of WiX v4 Preview 1 and the first preview of HeatWave Community Edition, then came WiX v4 RC1 and a matching HeatWave. Today, we're pleased to announce WiX v4 RC2 and a HeatWave Community Edition that supports it.

HeatWave v0.9.4 supports WiX v4 RC2, includes a number of bug fixes that users have kindly reported, and adds support for Visual Studio on Arm64 devices.

Note that HeatWave v0.9.4 is required to match changes made in the WiX v4 RC2 MSBuild targets.

To upgrade WiX from RC1 to RC2, check out the WiX release notes.

To update HeatWave Community Edition from within Visual Studio:

  1. Choose Extensions|Manage Extensions.
  2. Expand the Updates node.
  3. Select Visual Studio Marketplace.
  4. Select HeatWave Community Edition.
  5. Choose Update (or Update All).
  6. Choose Close.
  7. Close Visual Studio to trigger the update.

To install HeatWave Community Edition for the first time:

Double-click the downloaded .vsix file to install HeatWave.

Now's the time

If you haven't checked out WiX v4 prereleases yet, now's the time to take a look at Release Candidate 2. Here's the scoop on WiX v4 and HeatWave:

WiX v4 is a major release of the WiX Toolset and contains some exciting new features like broad Arm64 support and a modern acquisition experience. You can read the release notes for an overview of what's new and changed.

HeatWave supports the WiX v4 acquisition experience with support for SDK-style projects and package references that acquire the WiX tooling from NuGet without needing to install anything. HeatWave also supports:

  • Conversion of WiX v3 projects and authoring
  • Building of WiX v4 SDK-style projects
  • Project references and WiX extension package references
  • Project and item templates
  • Property pages to control how the project builds

HeatWave Community Edition is available free of charge. Read more about it and download it here.

To hear about the ongoing work FireGiant is doing in HeatWave, follow us here on the FireGiant blog.