“Since the release of Visual Studio 2010 users can get a limited edition of InstallShield free of charge. I just came across an announcement from Microsoft which has been posted two months ago. Candy Chiang, Program Manager Visual Studio Deployment, announces that in future versions the Setup & Deployment project type - also known as Visual Studio Installer - will be retired in favor of InstallShield Limited Edition. The announcement was posted in Microsoft's MSDN forum for ClickOnce and Setup & Deployment Projects:
“Retirement of Visual Studio Installer Projects from future versions of Visual Studio
Candy ChiangMSFTThursday, July 15, 2010 8:07 PM
In Visual Studio 2010, we have partnered with Flexera, makers of InstallShield, to create InstallShield Limited Edition 2010 just for Visual Studio 2010 customers. The InstallShield Limited Edition 2010 offers comparable functionality to the Visual Studio Installer projects. In addition, you can build your deployment projects using Team Foundation Server and MSBuild. For more information, see http://blogs.msdn.com/b/deployment_technologies/archive/2010/04/20/installshield-limited-edition-is-available-for-download-in-visual-studio-2010.aspx.
With InstallShield available, the Visual Studio Installer project types will not be available in future versions of Visual Studio. [GD: Emphasis added] To preserve existing customer investments in Visual Studio Installer projects, Microsoft will continue to support the Visual Studio Installer projects feature that shipped with Visual Studio 2010 and below as per our product life-cycle strategy. For more information, see Expanded Microsoft Support Lifecycle Policy for Business & Development Products.
I hadn’t seen this…
It kind of bugs me that there’s not going be an in-house Setup solution from Microsoft in the VS box (cough… when they DO have an in-house solution in WiX…cough). Am I not perfectly happy with the current Visual Studio Setup and Deployment projects, but for a very quick and dirty MSI it works just fine. Just seems weird that Microsoft is not going to provide a setup solution. What good is building an awesome app if we can’t deploy it? And forcing us to rely on a third-party product smells bad. I LIKE that there’s options, but being forced to use it is something else…
Are they doing this because in 2012/13/14 they don’t see a need to build MSI’s at all anymore and so feel it’s okay to delegate this to a third party?
Related Past Post XRef:
Free InstallShield Limited Edition 2010 coming to help our VS2010 Windows Installer and TFS/automated building woes