WiX v5.0.1

Author: barnson

src/Docusaurus/docs/intro.md

@@ -62,7 +62,7 @@ wix --version
 WiX is available as an MSBuild SDK for building from the command line using `dotnet build` from the .NET SDK or the .NET Framework-based `MSBuild` from Visual Studio. 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/5.0.0">
+<Project Sdk="WixToolset.Sdk/5.0.1">
 </Project>
 ```
 
@@ -71,7 +71,7 @@ WiX is available as an MSBuild SDK for building from the command line using `dot
 To update your .wixproj MSBuild projects from previous WiX releases, update the `Project` element's `Sdk` attribute:
 
 ```xml
-<Project Sdk="WixToolset.Sdk/5.0.0">
+<Project Sdk="WixToolset.Sdk/5.0.1">
 ```
 
 For `PackageReference`s to WiX extensions, update their `Version` attribute. For example:

src/Docusaurus/docs/tools/msbuild.md

@@ -7,7 +7,7 @@ sidebar_position: 20
 WiX v4 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/5.0.0">
+<Project Sdk="WixToolset.Sdk/5.0.1">
 </Project>
 ```
 
@@ -143,7 +143,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/5.0.0">
+<Project Sdk="WixToolset.Sdk/5.0.1">
   <PropertyGroup Label="Globals">
      <DefineConstants>MyProductNameProperty=$(MyProductNameProperty);</DefineConstants>
   </PropertyGroup>

src/Docusaurus/docs/tools/wixexe.md

@@ -254,7 +254,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/5.0.0`
+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/5.0.1`
 :::
 
 | Subcommand | Description |

src/Docusaurus/docs/tools/wixext/index.md

@@ -63,8 +63,8 @@ You might need to specify a version for WiX extension packages (such as when the
 
 ```xml
 <ItemGroup>
-  <PackageReference Include="WixToolset.BootstrapperApplications.wixext" Version="5.0.0" />
-  <PackageReference Include="WixToolset.Util.wixext" Version="5.0.0" />
+  <PackageReference Include="WixToolset.BootstrapperApplications.wixext" Version="5.0.1" />
+  <PackageReference Include="WixToolset.Util.wixext" Version="5.0.1" />
 </ItemGroup>
 ```
 

src/Docusaurus/news/2024-07-16-wix-v5.0.1-available.md

@@ -0,0 +1,6 @@
+# WiX Toolset v5.0.1 available
+
+[WiX v5.0.1][rel] is now available! Read more about it at [the FireGiant blog][fg].
+
+[rel]: /docs/releasenotes#v5
+[fg]: https://www.firegiant.com/blog/2024/7/16/wix-v5.0.1-has-been-released/