WiX v3.5 Final Build.

# by Rob Mensching on Wednesday, January 19, 2011 9:41 PM

tags: wix,

WiX v3.5 escrow has been a bit bumpier than I would have liked. We started with the Thanksgiving Day build. Then we had the end of December build that seemed for sure to be the last one. In the end, we did one more build today. The changes were small so we're only going to sit on this build for a week or so. We're really down to the wire. You know what to do, right?

Download, please.

The last two bugs taken were to fix some typos in the zh-HK WiX UI localization file and re-add the setupbld.exe to the MSI that were accidentally removed when ClickThrough was pulled out. Neither of these changes changed any code and we haven't take a bug fix in quite a while, so WiX v3.5 feels done.

Please, integrate the WiX v3.5.2519.0 build into your build process and let us know. In a week or so, that build could very well declared "Production".

tags: rob, mensching, wix, escrow, production

5 Comments

Comment by Christopher Painter on Thursday, January 20, 2011 4:13 AM

I'd love to, but I still have concerns about the way you can't have 3.0 and 3.5 installed side by side. I can mitigate that on the build side but on the developer side we use Votive and have hundreds of wixprojs on multiple branches. Some are on maintenance we can't migrate them forward. I'm not sure how to make this easy on the developer side.

Also a nice summary everything that's new and improved for 3.5 would be helpful in deciding if it's worth the effort.

Comment by Dave Smalley on Friday, January 21, 2011 9:10 PM

Chris -

I have the same issues. Virtual machines cover a multitude of sins.

Comment by Pichat on Sunday, January 23, 2011 4:08 AM

Hi! I will also wait until it becomes officially stable, a documentation about changes and the status of localisation would be nice to have.

Greetings from Sweden

Comment by Christopher Painter on Sunday, January 23, 2011 5:26 AM

Sure, I can do VM's at home. After all I have my own Hyper-V server complete with DC's, WDS, WSUS, RAS, SCCM, SQL, TFS (Server and Team Build Agent) and a variety of Integration Testing VM's.

But at my day job, I have somewhere between 100 and 150 people using WiX. I don't think VM's would work for them.

Maybe some hack will come to my mind. Maybe we put 3.5 on all developer machines and duplicate the targets file so that 3.0 projects will load in 3.5 as is. Then maybe on the build box we'll inject which version of WiX to use and rewrite the wixprojs to point to the right one.

Perhaps someone will have a great suggestion but either way it all feels like a hack.

Comment by Nick on Tuesday, January 25, 2011 2:02 PM

Think I found a bug.

If I heat-harvest a directory that has an "x64" sub-directory in it, it will give me an entry like so:

Directory Id="x64" Name="x64"

Which results in this:

[omitted].xml(14301) : error LGHT0204 : ICE99: The directory name: x64 is the same as one of the MSI Public Properties and can cause unforeseen side effects.

I manually corrected it:

Directory Id="x64__" Name="x64"

RobMensching.com /Blog because setup isn't just xcopy

WiX v3.5 Final Build.

5 Comments