WiX v3.0 released.

It is my pleasure to announce that WiX toolset v3.0 is now officially declared Production/Stable. The final build number is 3.0.5419.0. You can download it from here or here.

The journey to release WiX v3.0 started about four and a half years ago. While WiX v2.0 was locking down and getting ready for it's release, we had a lot of ideas how to improve the language and better build integration with Visual Studio. Obviously, those ideas would destabilize WiX v2 so we decided to spin up an independent WiX v3 effort.

Early in the project it was clear that WiX v3 was a major improvement over WiX v2. Developers flocked to it for the file and directory short name generation feature alone. MSBuild integration in Votive was also a huge hit. Additionally features like @Id and Component/@Guid generation, smart cabbing, heat, and the best Windows Installer patch generation tools on the planet make WiX v3.0 a very important release.

When Visual Studio team members joined the WiX v3 effort it became clear that WiX v3 was also going to be the most stable release of the WiX toolset ever. There were over 900 bugs resolved during the course of the project. But a more important number to me is that we've postponed fewer than 10 bugs and each of them have a workaround. Comparatively, WiX v2 released with over 100 known issues all of which were fixed in WiX v3. All of this makes WiX v3.0 the most reliable set of tools you can use today to create Windows Installer databases.

We have also faced our fair share challenges while working to release WiX v3.0. We had to make a painful cut and remove Burn from the WiX v3.0 roadmap. That also prevented ClickThrough from reaching its true potential. Many of you probably also remember the in-the-box then out-of-the-box decisions by Visual Studio. That morale boost and breaker led to the decision that WiX v3.0 was ready now and could be released on America's Independence Day. Finally, a less visible but possibly the most difficult challenge that I faced was the complete turn over in the core developers. In fact, one of the things that excites me most about this release, is that everyone is coming back for the ship party.

727998786_64404576f8_m Which brings me to my closing remarks. We're going to have a party. Tonight all over the United States there will be firework displays of varying scales and grandeur. While watching those pyro.exe.technic events light.exe up the dark.exe night sky with gigantic roman candle.exes celebrate with the team that brings you the WiX toolset.

We have a great time working on the WiX toolset and we hope you enjoy the efforts. WiX v3.0 isn't the end for us. It's just the most useable and stable release until we bring you the next one.

And until then keep coding. You know I am.

 

15 Comments

Comment by Christopher Painter on Saturday, July 4, 2009 12:20 PM

Outstanding Rob. Time for me to remove the WiX ship countdown from my blog. Somehow after years of development I knew that the WiX team would make this date.

I do wonder though when the SF site will be updated so that it doesn't say V3 is beta. We will be making a big push towards WiX at work and I need to be able to tell the Engineering Technology Review Board co-members that this is a production release.

Comment by John Vottero on Saturday, July 4, 2009 1:39 PM

Thanks to you and the rest of the WiX team for creating a great tool!

Comment by barryd on Saturday, July 4, 2009 1:44 PM

A wee hiccup - the X86 download has no file extension, which may confuse a few people.

I have to admit there's a small irony in the downloads being zips of MSIs, rather than MSIs.

Comment by Rob Mensching on Saturday, July 4, 2009 1:59 PM

@Christopher, thank you. I think you just need to refresh your browser cache to see the Beta label removed. The site is showing correctly for me right now (unless we missed a spot).

Comment by Rob Mensching on Saturday, July 4, 2009 2:01 PM

@John, thanks much. I'll pass it on.

Comment by Rob Mensching on Saturday, July 4, 2009 2:03 PM

@barryd, thanks we'll look into fixing the extension. The .zip files are required due to a limitation that SourceForge does not allow the same file name released multiple times and the source resolution requirement to keep the .msi file names the same. All of that nonesense will be a non-issue when we switch to using burn in WiX v3.5.

Comment by blaineW on Monday, July 6, 2009 8:42 AM

I agree with John. Wix is an outstanding toolset and the improvements for ver 2 to ver 3 are really impressive.

Comment by mhanney on Wednesday, July 8, 2009 9:15 AM

This is very exciting news. WiX v3.0 will be part of our build & release process for many, many years I'm sure. Thanks Rob.

Comment by Darryl on Saturday, August 8, 2009 7:58 AM

The Wix project was the inspiration that started me writing open source software. I seriously appreciate all the effort you have put in. Wix 3.0 is fantastic already - I look forward to what the next version brings!

Comment by Kevin Burton on Friday, August 28, 2009 2:47 PM

I am sure this is an FAQ. But what is the final verdict on using files that were developed and used with V2.0 with the new release of V3.0? Do I need to "convert" or will it just work?

Thank you.

Kevin

Comment by Rob Mensching on Friday, August 28, 2009 10:21 PM

@Kevin, there is a tool called WixCop.exe that can convert your v2 .wxs files into WiX v3 format. Also, I wrote about the process in detail here: http://robmensching.com/blog/posts/2009/7/7/Tips-on-how-to-upgrade-from-WiX-v2-to-WiX-v3

Comment by Garry Smith on Thursday, October 8, 2009 5:30 PM

Hey Rob

My name is Garry Smith from echoTechnology. One of my developers is recommending we use wix 3.0 for the SharePoint 2010 release of our echo for SharePoint product.

Now my head developer is a low level, in the sandpit love the ants guy, and a smart one at that, so I know WIX is going to be a very powerful tool for our multi tier service deployment and a joy for those that love XML and the command line(like him). However our planning reveals we need to have a sophisticated GUI lead discussion with users during the install of our tool. Can you please recommend how we would create that UI without specifying it in WIX XML as our UI guys are the types of nancy boy develpers that like to paint these things with pretty pictures (And I agree with them)

Comment by Fox Diller on Thursday, May 6, 2010 5:37 AM

Is there any reason why the WiX/Votive Installer would wipe out all of our Visual Studio 2008 Team System settings? ReSharper required our license key again, our code window themes were gone, every single setting was reset. We were even asked what development environment we wanted to select.

I recommended this and it destroyed all the settings we had. I can't recommend this great tool any longer. Can you guys help?

Comment by Rob Mensching on Thursday, May 13, 2010 2:52 PM

Fox, no one has ever reported that issue before. If you can start a discussion at wix-users@lists.sourceforge.net mailing list we might be able to track down the problem.

Comment by Adrian Tawse on Wednesday, October 27, 2010 3:54 AM

Hi
I tried to download and run wix3.0 on Windows7 It downloaded OK but any attempt to Run the installation results in Windows saying is is not a valid installer! Any ideas?

Leave a comment
optional