[wix-users] ETA for WiX 3.11 release?

Rob Mensching rob at firegiant.com
Thu Jan 5 04:00:06 PST 2017

"It's just too ugly this time." I basically agree with that.

Personally, I'm waiting for RTM. I just don't have time to mess around with RCs since "the new MSFT" seems quite willing to change/break anything right up to RTM. Other people have time to poke at the RCs.

 Short replies here. Complete answers over there: http://www.firegiant.com/

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Christopher Painter
Sent: Thursday, January 5, 2017 3:50 AM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: Re: [wix-users] ETA for WiX 3.11 release?

Yes.  I found the thread you talked about, Heath's blog and the nuget package that has the wrapper to do it.

It didn't work... blew up with exceptions.  I left a comment on Heaths blog as such.   I also left a comment regarding the WIP.   I'm not currently using Burn.   I simply use the propertyrefs  and CopyFile elements that cause a copy to happen if the property has a value.   But this is static... say 2008,10,12,13,15.    It's not dynamic for multiple instances.   So it'd also be interesting to consider temp records to register with all found instances.

I guess where I'm left is....

Good news:  If I manually copy all my WiX and IsWiX components in place it all still seems to work!  Whew.

Bad news: what you said.  You made a comment like you were waiting for someone to do the work but from reading the tea leaves I'm not sure you guys approve of the custom action and COM object called for in the WIP.  I don't blame you... I'm guessing this is one of those we don't have much choice.  I'd love to help but I don't have the C++ chops to be honest.  I only do C#/DTF CAs these days.

Going forward:  I'm just going to have to follow your lead.  Whatever WiX does to burn and the .net extensions to support all of this is just what I'll have to go with.  I'm not going to hack something together myself ahead of a WiX release. It's just too ugly this time.

My final though is that this is further evidence of why I keep my application code and installer code in two different solutions.    This way a developer can jump to the bleeding edge in the solution they really care about.

More information about the wix-users mailing list