Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/content/docs/wix/osmf.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ occasional manual use. See the table at the bottom of this page for the [full li
The first option to accept the EULA is to add the `AcceptEula` MSBuild property to your .wixproj with the [appropriate EULA ID](#available-eula-ids):

```xml title="MyPackage.wixproj" ins={3}
<Project Sdk="WixToolset.Sdk/7.0.0">
<Project Sdk="WixToolset.Sdk/7.0.1">
<PropertyGroup>
<AcceptEula>wix7</AcceptEula>
</PropertyGroup>
Expand Down
4 changes: 2 additions & 2 deletions src/content/docs/wix/tools/msbuild.md
Original file line number Diff line number Diff line change
Expand Up @@ -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/7.0.0">
<Project Sdk="WixToolset.Sdk/7.0.1">
</Project>
```

Expand Down Expand Up @@ -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/7.0.0">
<Project Sdk="WixToolset.Sdk/7.0.1">
<PropertyGroup Label="Globals">
<DefineConstants>MyProductNameProperty=$(MyProductNameProperty);</DefineConstants>
</PropertyGroup>
Expand Down
2 changes: 1 addition & 1 deletion src/content/docs/wix/tools/wixexe.md
Original file line number Diff line number Diff line change
Expand Up @@ -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/7.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/7.0.1`
:::

| Subcommand | Description |
Expand Down
4 changes: 2 additions & 2 deletions src/content/docs/wix/using-wix.md
Original file line number Diff line number Diff line change
Expand Up @@ -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/7.0.0">
<Project Sdk="WixToolset.Sdk/7.0.1">
</Project>
```

Expand All @@ -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/7.0.0">
<Project Sdk="WixToolset.Sdk/7.0.1">
```

For `PackageReference`s to WiX extensions, update their `Version` attribute. For example:
Expand Down
2 changes: 1 addition & 1 deletion src/content/docs/wix/whatsnew/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ sidebar:

- [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)
- [GitHub release](https://github.com/wixtoolset/wix/releases/tag/v7.0.1)


## What's new in WiX v7
Expand Down
13 changes: 11 additions & 2 deletions src/content/docs/wix/whatsnew/releasenotes.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,7 @@ sidebar:

## WiX v7

- WiX v7.0.1 was published 26-Oct-2026.
- 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.
Expand All @@ -30,20 +31,28 @@ WiX v7 continues our three-year-old tradition of shipping releases annually and
- Add `ProductSearch/@Result='exists'` to Burn searches. (Issue [9079](https://github.com/wixtoolset/issues/issues/9079))


### WiX v7.0.1

WiX v7.0.1 was released in response to a security release in a .NET assembly that WiX includes. WiX v7.0.1 avoids the vulnerable assembly and also includes the following fixes for customers:

- Add the `-nohardlinks` switch to prevent WiX from using hard links to copy files during the build process. Copying files instead of using hard links can significantly add to build times for large payloads but some build systems get confused without physical copying.
- Don't complain about duplicate layout names in a bundle build if the payloads are identical files. The `WIX8004` error was added in WiX v4 to prevent accidentally overwriting commonly-named files and breaking a bundle install. But if the files being laid out are identical, the bundle will install successfully, so `WIX8004` is not an accurate error.


### Get started

Get started with an SDK-style .wixproj project:

```xml
<Project Sdk="WixToolset.Sdk/7.0.0">
<Project Sdk="WixToolset.Sdk/7.0.1">
</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="7.0.0" Manufacturer="Acme">
<Package Id="Acme.HelloWorld" Name="HelloWorld" Version="7.0.1" Manufacturer="Acme">
<Files Include="*" />
</Package>
</Wix>
Expand Down