WiX v3.5 status or the lack thereof.

There was a comment on my WiX toolset bug count entry asking about the status of WiX v3.5 and more importantly the bootstrapper often referred to as Burn. The short answer is there is no status to report. Work on WiX v3.5 has not started in earnest because we are all focused on addressing the bugs in WiX v3.

Each week I hope we can finally turn our attention to creating the much needed WiX toolset bootstrapper. But each week our bug count has inched back up and it takes a concerted effort to get the count back down. Trust me, I'm excited to get into Burn. However, our first responsibility is to ship a high quality WiX v3 and then deliver a kick ass bootstrapper in WiX v3.5.

In the meantime, keep on coding. You know I am.

 

2 Comments

Comment by Tim Dunham on Wednesday, February 11, 2009 12:02 PM

Rob, I'm brand new to WiX but I've been tasked with creating new installers for our product, which requires multi-instance support. We've been investigating different ways of doing this using instance transforms, but we've been struggling to get this working. One idea that we're looking into right now is to not use transforms, but rather use the MSI API to change the necessary data in the MSI database on the fly for each instance. This would be done inside our own bootstrapper, which would be responsible for managing all of the product guids for each available instance. One significant reason that we like this approach is that we can contain all of the complexity of multi-instance installs inside our bootstrapper, making it easier to roll this out to other product teams in our company that also need to do multi-instance installs but who don't know WiX. We'd like to know what you think about this approach and if there are any pitfalls we should be aware of. Are we totally crazy here? Any input is appreciated. Thanks, Tim

Comment by quirrel on Tuesday, May 26, 2009 9:01 AM

Tim, thath sounds crazy as first thought. Are you any further with your ideas, as we are facing the same problem in future

Leave a comment
optional