WiX Online Meeting 313 Highlights

Wednesday, November 18, 2026

Today's meeting was longer than we've had for a while. Interesting topics of discussion tend to make for longer meetings, after all. Read on for a glimpse at what kept us occupied.

WiX v7.0.1

As promised, we shipped WiX v7.0.1. This was a minor release that was needed because WiX includes an assembly that was deemed to contain a security vulnerability. WiX didn’t expose the vulnerability but because the guilty assembly was included, we shipped WiX v7.0.1.

AI guidelines

Without getting into the politics, economics, ethics, or other icks of AI, it has undoubtedly affected many aspects of software development, especially in open source. WiX doesn’t yet have policy on the use of AI but a guiding principle is that humans are in charge. We want humans to judge feature requests and how they and bug fixes are implemented. For that we have our ongoing guidelines about issues and pull requests: Start with an issue so we can discuss it during our triage—because there might be important feedback—and reference the issue so everyone can keep up to date on what’s happening. Should we start getting more and/or bigger AI contributions, we’ll reevaluate the need for actual written-down policy.

Issue triage

  • License appears blank if RTF content is too short., from @wixbot, provides details about the problematic RTF content created by Word that caused problems with the rich-edit text control used in Windows Installer UI. It’s caused problems for years—decades, actually—but an easy workaround was to open the .rtf file in WordPad and save it again. As WordPad shared the same rich-edit control, it was more compatible. Unfortunately, Microsoft decided that WordPad needed to be killed off and it’s no longer available in current Windows 11 releases. So Rob updated WiX to remove the problematic RTF automatically.

  • WIX0103 Cannot Find File Error in wixlib project, from @weberms, is a problem when you want to build a .wixlib with bound files that includes the bound files from another .wixlib. This is an older bug that came back to triage so Rob could discuss an open pull request in the context of AI guidelines. Rob is the proud new assignee of this bug to review the pull request.

  • Support referencing a LaunchCondition, from @robmen, addresses the lack of a method to reference a fragment that contains a Launch element. It’s useful to centralize and share launch conditions, so Rob’s proposing a LaunchRef element to pull them in. Nobody likes the name but barring some extraordinary brainstorm, that’s what we’ll use when Rob implements this in WiX v8.

  • Release only 64-bit WiX tools, from @robmen, is a topic of discussion: In 2027 with WiX v8, can we stop shipping 32-bit WiX build tools? Though MSBuild is still available as a 32-bit tool, the default is 64-bit. The WiX MSBuild tasks themselves are MSIL and launch wix.exe as a separate process, so should be compatible with both bitnesses without extra work. Rob volunteered to verify the “should be” into an “is” and, if true, proceed with the elimination of 32-bit tools.

  • Design-time builds link, validate and sign packages, colliding with the real build (WIX0301 / WIX7010), from @Jonathan727, suggests that when ReSharper is running inside Visual Studio, design-time builds run the full build of a .wixproj. Without ReSharper, only compilation runs, which is Blazingly Fast™ in comparison. The creator of the issue also provided a pull request, which Rob has volunteered to review.

  • Consider .NET (Core)-only WiX release, from @barnson, is an issue I opened after noticing that a number of packages released around .NET 11 last week no longer support .NET Framework. WiX itself supports both .NET Framework and .NET (formerly known as .NET Core but confusingly renamed). In many places that takes the shape of using the netstandard2.0 target so code is compatible with both .NET Framework and .NET.

Even more issue triage

We also triaged issues currently assigned to the v.Future milestone, which is where we stash issues we know we want to work on but not necessarily when we want to work on them. Most of these we left alone as we don’t intend to work on them for WiX v8. But we’ll keep them in v.Future as we contemplate the bigger work we want to accomplish in WiX v9. Or even WiX v10.

by Bob Arnson on Wednesday, November 18, 2026

Get Setup Matters in your inbox

Be the first to know when a new post is up.