Windows Installer XML (WiX) toolset

The WiX Toolset v3.0 released 8 years ago today. Since then we've released 10 versions that maintain a high level of backwards compatibility. For most that commitment to backwards compatibility makes it easy to pick up the bug fixes, features and ... [More] security updates each new release offers. Sometimes supporting backwards compatibility means we end up dragging along quite a bit of legacy. Like a dependency on .NET Framework v3.5. But v3.14 is a "stepping-stone" release to WiX v4.0 so it's time to move to a more recent .NET Framework. Sound good? I thought so. Let's code! [Less]

During our last WiX Online Meeting, I talked myself into volunteering to study how other projects use labels in their issues. Here’s what I came up with: Some repos prefix their labels to sort them into “namespaces,” like resolution and area. ... [More] Generally prefixes are common in repos with many dozens of labels. WiX doesn’t have … Continue reading "Labeling issues in WiX" [Less]

During our last WiX Online Meeting, I talked myself into volunteering to study how other projects use labels in their issues. Here’s what I came up with: Some repos prefix their labels to sort them into “namespaces,” like resolution and area. ... [More] Generally prefixes are common in repos with many dozens of labels. WiX doesn’t have that many issue labels so I propose that we don’t need them. Instead, we should just document the labels we use. [Less]

During the final weeks of WiX v3.11 it was challenging just to find time to code much less write about the code. So our fun "Let's Code" sessions here were postponed while I focused on simply finishing WiX v3.11. But we are successfully past WiX ... [More] v3.11 so let's talk about WiX v3.14. Actually, how about we create WiX v3.14 right now. Sound good? I thought so. Let's code! [Less]

Today we release WiX Toolset v3.11. If you already installed v3.11.0.1701 from the weekly releases then you are already up to date. No need to do anything. For everyone else, here's why you might want to upgrade to WiX v3.11.

On Cinco de Mayo 2017, we released WiX v3.11. WiX v3.11 RTM is v3.11.0.1701. You can download the WiX Toolset v3.11 build tools and Visual Studio extensions here. The primary goal of the WiX v3.11 development cycle was to support Visual Studio 2017. ... [More] We met that goal, with more than the usual number of challenges, … Continue reading "WiX v3.11 released" [Less]

On Cinco de Mayo 2017, we released WiX v3.11. WiX v3.11 RTM is v3.11.0.1701. You can download the WiX Toolset v3.11 build tools and Visual Studio extensions here. The primary goal of the WiX v3.11 development cycle was to support Visual Studio 2017. ... [More] We met that goal, with more than the usual number of challenges, due to the scope of changes in Visual Studio 2017. In previous versions of WiX v3. [Less]

Today we released the second WiX v3.11 Release Candidate. This is a bug fix release where we addressed as many of the issues found in the first release candidate as possible. The net result is pretty good leaving only a couple VS template related problems. Or so we think. Your validation will help us know for sure.

Today we released the WiX v3.11 Release Candidate. The focus of WiX v3.11 was support for Visual Studio 2017. So it seemed only appropriate that our schedule align with the release of VS 2017. It took some creative brainstorming at FireGiant and some community heroics to get it done. But get it done we did. But what did we get done?

Last week and weekend was phenomenal for WiX v3.11 (detailed summary here). Everyone pitched in and we went from 24 issues to 7. We're now at 8 issues because a solution for supporting VS2017 support is under development. The only problem is that I ... [More] own 5 of the 8 remaining issues. So I best be getting to work. I'm skipping the oldest bug because I don't feel like writing documentation tonight. Instead, I'm digging into two issues related to Burn: #5265 and #5307. Let's code! [Less]