Skip to content

Fix shameful typo to restore my family honor. #13

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
barnson merged 1 commit into from
Jul 9, 2025
Merged

Fix shameful typo to restore my family honor. #13

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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/whatsnew/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ WiX v6 contains a number of bug fixes and new features, including these favorite
Windows Installer uses GUIDs at the drop of a hat...any hat. It's hard to complain because GUIDs are perfect as unique identifiers (it's right in the name). But they're definitely awkward and WiX has been on a 20+-year-fight to get rid of them where feasible. This year, we got rid of the last "mandatory" GUID: The upgrade code.

:::note[Well, actually...]
Upgrade codes in MSI packates aren't _technically_ mandatory, but omitting them is a bad idea. So bad, in fact, that they _are_ mandatory for bundles.
Upgrade codes in MSI packages aren't _technically_ mandatory, but omitting them is a bad idea. So bad, in fact, that they _are_ mandatory for bundles.
:::

The _concept_ of an upgrade code is still needed: MSI and Burn need a way to identify a "family" of product versions that can upgrade each other. But now you can use a human-readable string in its `Id` attribute rather than a GUID in an `UpgradeCode` attribute:
Expand Down