Change of plans for WiX v3.5.

About a year ago we started WiX v3.5. At that time we decided on a new plan for WiX v3.0 that moved the Votive for Visual Studio 2010 and Burn features out of WiX v3.0 into WiX v3.5. The goal was for v3.0 to ship earlier. That worked out well because WiX v3.0 released last July.

Through the summer, the plan to deliver WiX v3.5 right around the time Visual Studio 2010 shipped seemed sound. Votive for Visual Studio 2010 in WiX v3.5 stabilized basically on schedule. However, in September, we moved Burn development to a new foundation and Burn still needs a lot of work.

Of course, two weeks ago Visual Studio 2010 shipped which means we should be finishing WiX v3.5 soon. Lots of people want a stable drop of the WiX toolset that supports Visual Studio 2010. Unfortunately, with the current plan we're a year out.

So we need a new plan.

WiX v3.5

This release is now all about Votive for Visual Studio 2010. The goal will be to finish as quickly as possible. If the IIS7 custom action stabilize quickly they'll stay in this release. Burn is out though.

  • Votive for Visual Studio 2010
  • IIS7 custom action (if it stabilizes quickly)
  • [cut] Burn

It would be great to have this release out in July, basically a year after WiX v3.0. That is aggressive so my confidence is low. As the bugs drop, I'll start tracking the progress here just like I did for our last release.

WiX v3.6

This release is all about Burn. Burn will not get cut from a release again. WiX v3.6 is where Burn will ship with all the features I described before. If the IIS7 custom action doesn't stabilize in time for WiX v3.5 we'll also finish it here. Finally, to reduce our build and test matrix I plan to drop support for Visual Studio 2005.

  • Burn
  • IIS7 custom action (if it doesn't ship in v3.5)
  • [cut] Votive for Visual Studio 2005

At this point Burn is something like four years late. Unfortunately, Burn probably won't be completely done for another year. Our first goal is to get Burn installing the WiX v3.6 toolset and hopefully be mostly stable by end of September.

WiX v4.0

This release will be all about simplification. Over the last decade, the WiX toolset grew into an extremely powerful tool for your Windows installation needs. In that push we've added more and more functionality but sometimes the features came at a cost of complexity. In WiX v4.0 I want to take time to make the toolset easier to build and easier to use. My hope is that some of us can start WiX v4.0 at the end of the year.

Conclusion

Burn is cut from its WiX release for a second time. I know a lot of people will be disappointed by that (I know that I am extremely disappointed by it). However, I believe there are more people that will be happy to know that a stable WiX toolset release that supports Visual Studio 2010 is just around the corner.

As always, please feel free to send me feedback.

 

22 Comments

Comment by Christopher Painter on Thursday, April 29, 2010 6:27 AM

Rob-

I have many products that I maintain at various stages of their life cycles. Currently I have v3.0 using VS2008 integration. If I install v3.5, will that cause any issues? I believe my understanding is you can't have v3.0 and v3.5 installed side by side but that v3.5 will be schema compatible with v3.0 and offer both vs2008 and vs2010 integration.

Is that about right?

Comment by Rob Mensching on Thursday, April 29, 2010 6:56 AM

Yes, that is all correct.

VS2005 support (of medium quality) is in v3.0 and v3.5. VS2008 is supported in v3.0, v3.5 and v3.6. VS2010 support will be in v3.5 and v3.6.

There are no other breaking changes between v3.0 to v3.6. If you find one, please file a bug.

Comment by Terry Humphries on Thursday, April 29, 2010 8:51 AM

What's the best alternative to burn?

Comment by Neil Sleightholm on Thursday, April 29, 2010 10:42 AM

IIS 7 support is quite high on my list of features, could I suggest it ships in some form with 3.5 and then there are 3.51, 3.52 drops with more fixes?

Comment by Jennifer Oppenheim on Thursday, April 29, 2010 12:12 PM

I agree with Neil Sleightholm's comment. IIS 7 support is important to me and I hope it will be included in some form in 3.5. I have no plans to migrate to VS 2008 or 2010 and so would not benefit if IIS 7 support were only in 3.6.

Comment by Brian Pearson on Thursday, April 29, 2010 12:51 PM

Would love IIS7 support sooner rather than later.

Comment by cbezop on Friday, April 30, 2010 5:11 AM

Hi Rob,

In our Wix process we have the simple Custom UI dialog. We have a plan to improve the look and feel of the installer. How we can create the Custom UI in WPF and how to intagrate that in WIX.

Regards
Cbezop

Comment by Navid Azimi on Friday, April 30, 2010 10:49 AM

I'm in agreement here. Without IIS 7 support, the WiX toolset is truly incomplete. I have been doing my best in identifying and filing bugs to make sure we reach stability soon.

Thanks for all your efforts, Rob.

Comment by Alan Low on Saturday, May 1, 2010 12:55 AM

Getting a stable, production quality version of WiX available for Visual Studio 2010 is certainly my wish.

Built in IIS 7 support would be great, but as APPCMD is so flexible it isn't too much pain to create some custom actions where needed.

It is a shame about Burn, but I think you've made a great decision Rob to delay it in order to concentrate on the overall stability of v3.5.

Comment by srini on Saturday, May 1, 2010 5:46 AM

all of our installers are in WIX 3.0 with Visual studio 2008. now can we use the same installer with wix3.0 with visual studio 2010?
please suggest me what to do... can we use wix 3.0 with visual studio 2010? if not what is the reason?

Comment by Christopher Painter on Saturday, May 1, 2010 9:55 AM

I was playing with WiX 3.5 today and I'm a little concerned by the fact that it does a major upgrade of 3.0 and doesn't allow for side by side installation. When I open my WiX 3.0 solutions it wants to automatically upgrade my wixprojs to the latest targets file with out asking me if I want to do this.

This would be problematic at my day job where I support over a dozen branches and not all of them will want to upgrade to a new WiX while some will. If I can only have one version on my box at a time this will be a huge pain point.

Comment by Juan Tamad on Wednesday, May 12, 2010 7:36 AM

I am a software packager using Wise Package Studio and Installshield but quite amused to see how WIX can automate the build and packaging process. I am not a programmer but I am very interested to learn something about the full automation the WIX can handle.

There are too many articles to read and I am quite confuse where to start. Can you point or give me the step by step procedures as well as the scripts how to achieve a full automation of creating MSI through WIX?

I want to automate the packaging I do in simple packages like files and registries,few Custom Actions, etc. Help would be greatly appreciated. Thank you.

Comment by Dan on Wednesday, May 12, 2010 2:11 PM

I want to express my agreement that getting 3.5 out ASAP is the right priority. VS2010 and .NET 4.0 have been out for a while, and people (like my team) will want to build stuff with it and install it, especially those who began working with the betas or RC.

Comment by Christopher Painter on Thursday, May 13, 2010 7:34 PM

My team is looking at VS2010, MSBuild 4.0 and TFS 2010. We keep our merge module projects in a different solution then our .NET projects.

I have to be honest though, what does jumping to WiX 3.5 really buy me? The same thing that I have now only using VS2010 IDE instead of VS2008? Maybe a few bug fixes?

I showed the developers that if I stick with 2008/3.0 I can still build it with MSBuild 4.0 and WiX 3.0 on the build box; no VS IDE needed at all.

That seems to make them happy enough for now.

Comment by Bryan Batchelder on Monday, May 17, 2010 3:33 PM

I would definitely like some kind of IIS7 support in Wix 3.5. Even if it is a subset of everything planned for a later release. Please don't cut it entirely from 3.5.

Comment by svk on Wednesday, July 14, 2010 7:51 AM

By when can we expect wix 3.5.
Eagerly waiting for it.

Comment by Dave on Thursday, July 15, 2010 10:53 AM

Not allowing 3.0 and 3.5 to run side by side is a back breaker for me! I'm at a company with about 50 developers. Most projects are using Wix 3.0 within Visual Studio 2008 and we use TFS. My most recent project I decided to use Visual Studio 2010 using .NET 3.5 which sounds like I need wix 3.5. However, since we are all using TFS, I can't just upgrade to 3.5 cuz if I do work on any other project I would have to upgrade those Wix projects also which would then force every other developer would need to upgrade to Wix 3.5 also - just because one developer doesn't have 3.0 anymore...

Am I missing something here?

Comment by Pally Sandher on Monday, July 19, 2010 8:30 AM

@Dave
At worst you'd need to maintain 2 .wixproj files for each project, a v3.0 & a v3.5.
Is it really that difficult to get your dev team to upgrade to v3.5 across the board? You're going to have to do it sometime anyway.

@svk -> http://wix.sourceforge.net/downloadv35.html

Comment by Christopher Painter on Friday, July 23, 2010 6:44 PM

Yes, it really is that difficult for me. I have a team of about a dozen build and install guys that support several hundred developers. We are supporting various products / baselines at different points in their life cycle. On our newer baselines it's almost all WiX 3.0 and InstallShield 2009 but I can easily find active branches with VS2003, VS2005, IS12, IS2008, IS2009 and WiX 3.0.

Our typical install has about 15,000 files and a dozen prereqs and we do about 100,000 builds a year.

Comment by Ran Davidovitz on Thursday, July 29, 2010 12:58 PM

The question is - Is 3.5 stable enough to be used for production already?

Comment by Krishen on Thursday, September 9, 2010 9:58 AM

Ran's question is mine too.

Comment by Mike Diack on Monday, January 24, 2011 5:11 AM

Hi Rob / Someone on the team....

Wix 3.5 has been escrow/RC ish since last autumn ("fall"). Is there a guesstimate as to when it'll go final/rtw?

I'm currently re-syncing with 3.5.2519, having been working with .2430 and it's predecessors.

Mike

Leave a comment
optional