Burn moves to a new foundation.

A week ago a very big accomplishment happened very quietly. The development team inside Microsoft responsible for creating the .NET Framework 4.0's (NETFX4) bootstrapper finished the initial transformation into the WiX toolset's bootstrapper, Burn. Yes, you read that right. Burn will now be based on the same code that shipped the .NET Framework 4.0 to hundreds of thousands of Beta users.

First, a little bit of history. At the beginning of July 2009, I described what Burn is all about. Back then I had hopes that Burn would be useable by the end of month or, at least, mid-August. At the end of July, the NETFX4 bootstrapper team approached me and suggested that we consolidate bootstrapper efforts. It took a bit of convincing but, by the end of August, I agreed that we should start from the NETFX4 bootstrapper codebase instead of the code that was under development in WiX.

So I wrote a high level feature requirements document that basically summarized my introduction to Burn plus its container support. The NETFX4 bootstrapper team took those requirements and built a plan to enhance the NETFX4 bootstrapper to reach feature parity with the Burn under development in WiX. The plan's execution took a bit longer than expected since the team was unexpectedly attacked by some extra Visual Studio 2010 work and the H1N1 virus (yes, swine flu literally wiped the team out for a few weeks). Despite the challenges, the NETFX4 bootstrapper team delivered and I finished the integration of the code into the WiX toolset last night.

With this new foundation in place, everyone can really get involved. I'll be talking more about Burn again. In particular, I'll explain how you can get started using the bootstrapper. I'll also focus on what changes you should expect as we add more features and incorporate feedback into the code. There's still plenty of work to get done but having a consolidated effort on a single bootstrapper is a huge benefit for everyone involved.

I look forward to your feedback about how Burn works for you and what should be done to make it better.

 

PS: For those of you that build the WiX toolset, this initial drop of Burn requires some libraries that are only available in Visual Studio Professional or better. It's high on my list to remove this requirement so that WiX v3.5 will build with freely available tools like WiX v2.0 and WiX v3.0 do.

 

8 Comments

Comment by wcoenen on Friday, January 15, 2010 5:31 AM

Burn still lives, hurrah! :-) I'm looking forward to instructions on how to start using it.

Comment by Eric on Friday, January 15, 2010 10:57 AM

Incredible news! One of the biggest pain points in previous .NET frameworks was the limited bootstrapper and the fact that every year it seemed like a new bootstrapper was being created from scratch.

Thank you!

Comment by Peter Darrow on Friday, January 15, 2010 10:57 AM

Great, really looking forward to this. Does the WiX team have an estimated release date for 3.5 final with Burn? Are there many pains in upgrading an installer from 3.0 -> 3.5?

Comment by Rob Mensching on Friday, January 15, 2010 4:26 PM

wcoenen, yes Burn lives. I'm sorry I went dark on it for the last few months. There were so many changes going on that I didn't want to publish a lot of misinformation. Even now there are a lot of changes still coming but I'm now far more confident that I know what the final product will look like.

I hope to get instructions how to use Burn available for the next build.

Comment by Rob Mensching on Friday, January 15, 2010 4:31 PM

Peter, the original goal was to release WiX v3.5 about a month after Visual Studio 2010 was released. Unfortunately, with the delays incurred with the foundation shift, I *think* we're looking at something more like September. A lot of that will be dependent on the feedback from user's like you.

Upgrading from v3.0 to v3.5 should be completely transparent. There are *no* breaking changes in v3.5. If there are it's a bug and we'll fix it. Of course, if you pick up any random build of v3.5 you'll be getting whatever quality we have at the time. Again, the bugs you file on those builds will help us finish v3.5 faster. :)

Comment by Enkidu on Saturday, January 16, 2010 1:46 PM

Rob, this is great news! A comprehensive and feature-rich bootstrapper is one of the greatest gaps when delivering software. Thanks for closing this gap.
I'm looking very forward for migrating my installer stuff to the bootstrapper. Please continue your great work!

Comment by Nick on Monday, January 18, 2010 11:48 AM

Hopefully this is the thing I have been building with MsBuild and Something.BootstrapperProject files?

I was wondering why you guys were wanting to re-invent bootstrapping...

Comment by Peter Ibbotson on Friday, January 29, 2010 10:11 AM

Bit late but one use case I have is to produce a single setup.exe that if it can find a .net framework (and windows installer) on the distribution media use that, otherwise do a download from the net.

A lot of my customers are not internet connected but can use a CD to perform upgrades or initial installs so this is something that I'd love to have and having a single setup.exe reduces the chances of us screwing up and putting the wrong thing on disk.

Finally are any good books on WiX and Windows installer? While the docs are ok I'm finding wrapping my head around it all little overwhelming at the moment.

Leave a comment
optional