WiX v3.10.1 is a maintenance release of WiX v3.10 with the following important fixes:
Download it here.
As you can see, we had a couple of problems with Windows XP support. Though I ran a few manual tests on XP during and at the end of v3.10, that wasn’t sufficient to uncover the bugs. Next time, I’ll put out an explicit call for testing support from folks still supporting Windows XP and Windows Server 2003. We’re going to need your help to keep bitrot at bay!
Here’s what Rob had to say about this release.
Update: WiX v3.10.1 has been released.
As planned, WiX v3.10 was released on (American) Labor Day. The RTM build is v22.214.171.1243.
Download it here.
Update: Rob also had words about WiX v3.10.
Burn and WixStdBA
- @rseanhall updated the build to use the latest Sandcastle help-build tool and to acquire it via NuGet. [issue]
- @robmen added an error message that detects when strong-name verification skipping hasn’t been set up for a developer build. [pull request]
- @rseanhall made maintaining history easier by merging individual history messages into the master history.md. [pull request] [pull request]
- @robmen fixed an error message. [issue] [pull request]
- @heaths added support for the Windows 10 SDK. [pull request]
And the rest
After shipping “the” WiX v3.10 release candidate back in June, we finished off a couple of features that required us to wait for Visual Studio 2015 RTM to be released. We also took a couple of trivial, small, and minor changes. So it’s time for another release candidate, to make sure WiX v3.10 is ready to ship.
Download it here.
If you find a bug, please report it as soon as possible.
Update: Here’s what Rob has to say about RC2.
Here’s what happened since RC1:
The WiX v3.10 Release Candidate build is now available! The focus of the WiX v3.10 release is supporting Visual Studio 2015 and Windows 10. As anticipated — almost like it was intentional — we’ve also fixed a number of bugs and implemented a small number of small features, but nothing big or risky.
We’re now ramping up the bug bar on WiX v3.10. That means bugs have to be really serious to get approved for v3.10. Don’t let that stop you from reporting bugs–we have plenty of numbers left in the v3.x series.
The plan for the RTM release of WiX v3.10 is to wait. Windows 10 ships 29-July and presumably Visual Studio 2015 ships shortly thereafter. As soon as Visual Studio 2015 RTM ships, we’ll put out a call for eyes to take a look and help verify that WiX continues to work with the RTM bits as expected. We’ll allow a short time to get feedback, then declare RTM.
Please download the RC release and help us get v3.10 across the finish line!
After a brief hiatus for releasing WiX v3.9 R2, weekly builds for WiX v3.10 have resumed. WiX v126.96.36.1993 is now available — and you might have noticed an oddity in the version number.
When we started discussing the need to ship a maintenance release for WiX v3.9, we realized that we had no way to easily differentiate a maintenance release from the original “final” release — or any other pre-release build, for that matter.
Traditionally, WiX version numbers have been based on using three fields: major.minor.build. You likely know why: Because Windows Installer uses three version fields and ignores the fourth. Unfortunately, when you want to keep using major.minor versioning, that leaves only one field to identify a particular build.
So we decided to switch things around a bit. We’re now versioning the WiX bundle as major.minor.release.build. The release value is currently zero and will stay that way until/unless we ship a maintenance release. For example, WiX v3.10 RTM might be v188.8.131.520 and a theoretical WiX v3.10 SP1 might be v184.108.40.2063.
The MSI packages in the WiX bundle continue to be versioned as major.minor.build.0, so that major upgrades keep working. The same is true of WiX executables. That means that, for example, Candle.exe from the aforementioned theoretical WiX v3.10 SP1 would have a version of v3.10.2323.0.
I’d rather all the versions — bundle, MSIs, and executables — have the same version number but tagging the bundle with release information is important enough to make this change.
Unfortunately, the new versioning scheme means that new builds of WiX v3.10 are always seen as “less than” any of the already-released WiX v3.10 builds with the old numbering. That means that if you have v3.10.1124.0 installed, for example, v220.127.116.113 will not be seen as an upgrade. The WiX BA blocks downgrades by hiding the big Install button:
The workaround is to uninstall any other build of WiX v3.10. Then v18.104.22.1683 will install normally.