WiX v7.0.0-rtm!

Author: barnson

src/content/docs/heatwave/index.md

@@ -13,14 +13,13 @@ HeatWave is FireGiant's Visual Studio extension for modern WiX. HeatWave Communi
 -   Project and item templates
 -   Property pages to control how the project builds
 
-HeatWave peacefully coexists with the WiX v3 Visual Studio extension, which lets you mix and match WiX v3 and modern WiX projects in a solution. You can convert the WiX v3 projects to modern WiX gradually.
+HeatWave peacefully coexists with the WiX v3 Visual Studio extension, which lets you convert WiX v3 projects to modern WiX.
 
 ## Installing HeatWave
 
 HeatWave is available from the Visual Studio Marketplace.
 
-- [Download HeatWave for Visual Studio 2022 here.](https://marketplace.visualstudio.com/items?itemName=FireGiant.FireGiantHeatWaveDev17)
-- [Download HeatWave for Visual Studio 2019 here.](https://marketplace.visualstudio.com/items?itemName=FireGiant.FireGiantHeatWaveDev16)
+- [Download HeatWave for Visual Studio 2026 and 2022 here.](https://marketplace.visualstudio.com/items?itemName=FireGiant.FireGiantHeatWaveDev17)
 
 Double-click the downloaded .vsix file to install HeatWave.
 

src/content/docs/index.mdx

@@ -22,7 +22,7 @@ import { Card, CardGrid } from '@astrojs/starlight/components';
 <CardGrid>
   <Card title="HeatWave" icon="seti:css">
     Seamless Visual Studio integration for your WiX projects.
-    Visual Studio 2022 and 2019 supported.
+    Visual Studio 2026 and 2022 supported.
 
     [Read more about HeatWave](https://www.firegiant.com/heatwave/)
 

src/content/docs/wix/tools/msbuild.md

@@ -5,7 +5,7 @@ title: MSBuild
 WiX is available as an MSBuild SDK. SDK-style projects have smart defaults that make for simple .wixproj project authoring. For example, here's a minimal .wixproj that builds an MSI from the .wxs source files in the project directory:
 
 ```xml
-<Project Sdk="WixToolset.Sdk/6.0.2">
+<Project Sdk="WixToolset.Sdk/7.0.0">
 </Project>
 ```
 
@@ -141,7 +141,7 @@ You can then reference `MyProductNameProperty`, for example, in other properties
 To make property values available as preprocessor variables in your WiX authoring, add them to the `DefineConstants` property. For example:
 
 ```xml
-<Project Sdk="WixToolset.Sdk/6.0.2">
+<Project Sdk="WixToolset.Sdk/7.0.0">
   <PropertyGroup Label="Globals">
      <DefineConstants>MyProductNameProperty=$(MyProductNameProperty);</DefineConstants>
   </PropertyGroup>

src/content/docs/wix/tools/wixexe.md

@@ -252,7 +252,7 @@ Manage the extension cache. Extensions are referenced by:
 - `id` (uses the latest available version)
 
 :::note
-When omitting `version`, `wix extension` commands could choose a version of an extension that is incompatible with the version of WiX you're running. Use a specific version to avoid that scenario. For example: `wix extension add WixToolset.Util.wixext/6.0.2`
+When omitting `version`, `wix extension` commands could choose a version of an extension that is incompatible with the version of WiX you're running. Use a specific version to avoid that scenario. For example: `wix extension add WixToolset.Util.wixext/7.0.0`
 :::
 
 | Subcommand | Description |

src/content/docs/wix/tutorial/index.md

@@ -11,9 +11,9 @@ You can follow along this whole tutorial one step at a time. You can also hop in
 
 ## System requirements
 
-WiX is available as an MSBuild SDK and .NET tool when using a .NET 6.0 or later SDK. It is also available as an MSBuild SDK when using MSBuild in Visual Studio 2019 and later.
+WiX is available as an MSBuild SDK and .NET tool when using a .NET 6.0 or later SDK. It is also available as an MSBuild SDK when using MSBuild in Visual Studio 2022 and later.
 
-In this tutorial, we're using Visual Studio 2022 but you can use Visual Studio 2019 -- or even no Visual Studio at all. But sometimes the words and procedures are assuming the use of current versions of Visual Studio 2022. You can also just follow along and not actually play with the code...but where's the fun in that?
+In this tutorial, we're using Visual Studio 2022 but you can use Visual Studio 2026 -- or even no Visual Studio at all. But sometimes the words and procedures are assuming the use of current versions of Visual Studio 2022. You can also just follow along and not actually play with the code...but where's the fun in that?
 
 
 ## The story so far

src/content/docs/wix/tutorial/sprint1/Install HeatWave.md

@@ -9,11 +9,10 @@ We're building our app and its installer in Visual Studio, so we need a Visual S
 
 HeatWave is available from the Visual Studio Marketplace.
 
-- [Download HeatWave for Visual Studio 2022 here.][dl17]
-- [Download HeatWave for Visual Studio 2019 here.][dl16]
+[Download HeatWave for Visual Studio 2022 and 2026 here.][dl]
 
 Double-click the downloaded .vsix file to install HeatWave.
 
+You can also install HeatWave inside Visual Studio by choosing `Extensions` then `Manage Extensions`.
 
-[dl17]: https://marketplace.visualstudio.com/items?itemName=FireGiant.FireGiantHeatWaveDev17
-[dl16]: https://marketplace.visualstudio.com/items?itemName=FireGiant.FireGiantHeatWaveDev16
+[dl]: https://marketplace.visualstudio.com/items?itemName=FireGiant.FireGiantHeatWaveDev17

src/content/docs/wix/using-wix.md

@@ -28,7 +28,7 @@ SDK-style projects have smart defaults that make for simple .wixproj project aut
 For example, here's a minimal .wixproj that builds an MSI from the .wxs source files in the project directory:
 
 ```xml
-<Project Sdk="WixToolset.Sdk/6.0.2">
+<Project Sdk="WixToolset.Sdk/7.0.0">
 </Project>
 ```
 
@@ -37,7 +37,7 @@ For example, here's a minimal .wixproj that builds an MSI from the .wxs source f
 To update your .wixproj MSBuild projects from previous WiX releases, update the `Project` element's `Sdk` attribute:
 
 ```xml
-<Project Sdk="WixToolset.Sdk/6.0.2">
+<Project Sdk="WixToolset.Sdk/7.0.0">
 ```
 
 For `PackageReference`s to WiX extensions, update their `Version` attribute. For example:

src/content/docs/wix/whatsnew/index.md

@@ -4,9 +4,22 @@ sidebar:
   order: 2
 ---
 
+## Get the latest version of WiX
+
+- [WiX MSBuild SDK](https://www.nuget.org/packages/WixToolset.Sdk)
+- [.NET command-line tool](https://www.nuget.org/packages/wix)
+- [GitHub release](https://github.com/wixtoolset/wix/releases/tag/v7.0.0)
+
+
 ## What's new in WiX v7
 
-WiX v7.0.0-rc.2 is available. See [the release notes](/wix/whatsnew/releasenotes/#wix-v7) for details about this prerelease.
+WiX v7 continues our annual release cadence, first introduced with WiX v4 way back in 2023. This release contains a normal number of features and fixes but the highlights are:
+
+- Burn now supports dual-purpose MSI packages in bundles, which lets a user choose to install a bundle per-user or per-machine at install time.
+- WiX v7 adopts the OSMF EULA v1.1 that avoids requiring a fee until you make at least US$10,000 a year from your projects that use WiX and requires explicit acceptance of the EULA.
+- Extra-long paths (i.e., paths longer than 260 characters) are now generally supported for locating payloads in packages.
+
+See [the release notes](/wix/whatsnew/releasenotes/#wix-v7) for details about this release.
 
 
 ## What's new in WiX v6

src/content/docs/wix/whatsnew/releasenotes.md

@@ -6,6 +6,7 @@ sidebar:
 
 ## WiX v7
 
+- WiX v7.0.0 was published 6-Apr-2026.
 - WiX v7.0.0-rc.2 was published 5-Mar-2026.
 - WiX v7.0.0-rc.1 was published 6-Feb-2026.
 
@@ -28,6 +29,7 @@ WiX v7 continues our three-year-old tradition of shipping releases annually and
 - Make WixUI_Advanced handle 64-bit installation directories. (Issue [2165](https://github.com/wixtoolset/issues/issues/2165))
 - Add `ProductSearch/@Result='exists'` to Burn searches. (Issue [9079](https://github.com/wixtoolset/issues/issues/9079))
 
+
 ## WiX v6
 
 WiX v6 is the second annual release since WiX v4. WiX v6 continues in the tradition of being intentionally highly compatible with its predecessor WiX v5—and by the transitive property of backward compatibility, with WiX v4 too. WiX v6 contains a number of fixes and enhancements of existing features, including those newly introduced in WiX v5. Notable examples include:
@@ -55,15 +57,15 @@ WiX v6 is the second annual release since WiX v4. WiX v6 continues in the tradit
 Get started with an SDK-style .wixproj project:
 
 ```xml
-<Project Sdk="WixToolset.Sdk/6.0.2">
+<Project Sdk="WixToolset.Sdk/7.0.0">
 </Project>
 ```
 
 and simple package code in a .wxs file:
 
 ```xml
 <Wix xmlns="http://wixtoolset.org/schemas/v4/wxs">
-    <Package Id="Acme.HelloWorld" Name="HelloWorld" Version="6.0.0" Manufacturer="Acme">
+    <Package Id="Acme.HelloWorld" Name="HelloWorld" Version="7.0.0" Manufacturer="Acme">
         <Files Include="*" />
     </Package>
 </Wix>