The WiX Toolset team did their first v3.10 weekly release: v3.10.1124.0
Weekly releases are basically developer beta test builds and are not final releases. This release is interesting to me because it includes Visual Studio 2015 support. I’ve tested this build with VS2015 Preview and IsWiX 2.5.14324.3 and I find everything is working just fine. I can now relax knowing that I’m well ahead of the curve in supporting the next release of Visual Studio.
When IsWiX was first developed, we targeted Visual Studio 2008. I dove into VS extensibility trying to figure out how to get the addin story to work. I got it to work but the solution left a little bit to desire. The first problem was very embarrassing: the icon was a big smiley face.
The API / method that registered the addin with the menu supported 2 techniques. One was an orginal index from a Microsoft Office icon library and the second involved creating a resources dll. I didn’t have the skill or the time to go down the second road so I stuck with the smiley face telling myself that I’d go back and fix it. As the days, weeks, months, years went by I failed to do so.
The second problem was that occasionally Visual Studio would just decide to drop the addin from the menu. You had to run a devenv /resetaddin command to get it back.
Today a new version of IsWiX is released that solves these problems. I’ve scoped the “old” addin to VS 2008, 2010 and 2012 and created a “new” addin using VSIX extension that targets VS 2013 and 2015. This new extension registers IsWiX in Help | About and Tools | Packages and Extensions and gives a nice blue flame icon with the new text “Launch IsWiX” under the tools menu.
That’s right, IsWiX now supports VS2015! There is a caveat though. The IsWiX multiproject solution templates ride on top of WiX infrastructure. WiX as of v3.9 does not yet support VS2015 so although IsWiX has correctly registered with VS2015 the project templates will not show up until WiX is ready to support VS2015. We are way ahead of the curve though so I expect all of this will come together prior to VS2015 shipping next year.
I’m sorry for letting the yellow icon live for so long and for doing back to back weekly releases. I finally get a fired up on this issue making it now or never.
Three and a half years ago, I wrote an article titled Installation Collaboration Workflows using Free Tools. I’d like to add a few comments based on recent events.
Over the past couple of years Microsoft has been doing some really cool things to help out the community. The first was making Visual Studio Online ( Cloud hosted Team Foundation Server ) free to teams of 5 or less. This is a really big deal because now you have “process in a box” infrastructure provisioned in minutes that features high availability, monitoring and disaster recovery all for the low, low price of…. FREE!
In the past Microsoft had Visual Studio Express for free but it lacked the ability to extend the IDE. At the same time they had the Visual Studio Shell which did. This created a way of developing .NET applications and packaging installers for them but in a very disjointed manner. Now Microsoft has released Visual Studio Community Edition which is on par with Visual Studio Professional. Now you can do both your application coding, installer coding and connect to that shiny TFS cloud instance for the low, low price of…. FREE!
Additionally Microsoft has open source the .NET core libraries. Awesome!
Windows Installer XML has been free and open source for 10 years. IsWiX has been free and open source for nearly 5 years. Combine all of above and a independent consultant like myself now has everything needed to be productive without spending a whole lot of money. A laptop, internet connection and a
guest bedroom corner office is all you need to either start a business or give back to your favorite open source project.
Looking back over the past year, I’ve written 95% of my installers using WiX and 5% using InstallShield. I still like InstallShield but the ROI just isn’t there for most of my customers. I’ve been approached by many customers who were about to purchase InstallShield and after a needs analysis I explained to them that I could author their MSI using WiX for a fraction of the cost of the InstallShield license alone. To do setup development collaboration with InstallShield you have to invest thousands of dollars in multiple licenses of DRM laden proprietary software. To do it using WiX and IsWiX is free and integrates into a development ecosystem (Visual Studio) already understood by your customer.
Thanks for reading. Please feel free to reach out to me if you want more information on this topic.
I’m sorry that I haven’t been blogging or working on IsWiX much this year. There just isn’t a lot of time left over after my day job, consulting, passion for SCUBA diving and family time. Still, I’ve managed to get a small release of IsWiX released on our CodePlex site today. This release adds support for authoring 64bit components, parses the MSI Product Version automatically when using TFS 2013 and has some minor improvements to the Files and Folders UI.