The official source of product insight from the Visual Studio Engineering Team
UPDATE: We’re happy to announce the availability of the Visual Studio Installer Projects Extension. This extension provides support for Visual Studio Installer projects in Visual Studio 2013. You can download the extension from the Visual Studio Gallery. To learn more check out this blog post on Visual Studio Installer Projects extension.
We believe it is important to provide Visual Studio developers a no-cost setup tooling solution to deploy applications to the various platforms you target. In Visual Studio 2010 we partnered with Flexera Software to included InstallShield Limited Edition, a free version of Flexera’s installation development solution, with Visual Studio. InstallShield Limited Edition added capabilities not found in Visual Studio Setup Projects, such as TFS and MSBuild integration, support for creating new web sites and ISO 19770-2 Tagging support.
When we deprecated the Visual Studio Setup Project in Visual Studio 2012, many customers shared feedback through the UserVoice site regarding additional features they’d like to see added to InstallShield Limited Edition based on their previous experiences with Visual Studio Setup Projects. These scenarios tended to coalesce around these areas:
While designing Visual Studio 2013 we reviewed the feedback developers shared with the Flexera Software team and looked for ways to improve the InstallShield Limited Edition extension for Visual Studio to align with the needs you have expressed. For this new release, Flexera Software will add several new features in InstallShield Limited Edition including:
Some customers have reported issues during project conversion particularly when converting setup projects that included custom actions. Our joint goal is to ensure that all Visual Studio Setup Projects migrate seamlessly to InstallShield Limited Edition so your work and investment can move forward. This includes projects with custom actions and they should migrate appropriately. We are working closely with Flexera Software to understand why projects and custom actions fail to migrate so we’d like those of you who have migration failures to submit a detailed bug on the failure using the Visual Studio Connect site. Look for updates on this issue as we learn more.
The changes above will be available not only for Visual Studio 2013 users but also for existing Visual Studio 2012 customers. You can get the Beta release for InstallShield Limited Edition by going to:
Please try out this new version and tell us what you think!
Tony Goodhew – Program Manager, Visual Studio IDE Services
After the better part of 19 years spent in Visual Studio (and precursor tools) Marketing, Tony decided that he should either make a career of it or try something new. He joined the IDE Services team as a Program Manager in early 2012 and has been working on Visual Studio extensibility and the Visual Studio Industry Partner Program since then. While not known for enjoying pina coladas and getting caught in the rain, his version of paradise would include a cheeseburger.
And what is even worse than the UI limitations is the fact that Limited Edition Install Shield does not support Custom Actions in .dll assemblies. This is something I've used heavily in .vdproj setup.
Somebody at Microsoft should be fired for doing this. I have to wonder what kind of malfeasance or incompetence was behind this awful decision.
Piss-poor decision to pull vdproj support from Visual Studio.
How can this possibly be a good decision on Microsoft's part?
Please bring back vdproj support!!!
If you like your Setup and Deployment project, you can keep your Setup and Deployment project, period!
Has there been a fix for migrating VS2010 setup projects to VS2013?
How does "Support for installing x64 applications and services" actually work?
When I compile I get error -7143: Component installs to a 64-bit folder but is not marked as a 64-bit component. This may result in an incorrect installation path for this component's files.
My Visual Studio 2013 Configuration Manager is set to x64 deployment and my project output destination folder is set to [ProgramFiles64Folder]. What am I missing here?
Do you believe in any word you are saying? If do, than lucky you politician.
We developers are spending to much man hours to migrate to sh*tty IS LE WHATEVER software. Hey, it is LIMITED, and we paid for PROFESSIONAL Visual Studio 2013! The year is 2014, and instead of being more simple it is getting more complicated to create setup project. Say Hi to Jimmy Buffet.
I think MS were forced to drop Deployment & Package Wizard due to legal or monopolization issue...
ISL is cheap and worth nothing
Please re-open visualstudio.uservoice.com/.../3041773-bring-back-the-basic-setup-and-deployment-project-, and please drop this low-quality product.
Please bring back the setup project in VS 2013! We don't want to depend on another third part vendor.
We believe it is important to provide Visual Studio developers a no-cost setup tooling solution to deploy applications to the various platforms you target.
I am laughing my *** off at this.
How about this.... We believe it is important to provide Visual Studio developers a no-cost setup tooling solution to deploy applications to the various platforms you target THAT FUCKEN WORKS YOU FAT CHEESEBUGER EATING DONKEY
I've spent several hours searching how to configure the ISLE plugin in VS2013 to generate a single image msi file. It would be very helpful to have a definitive answer as to whether this is possible and if so how to configure this option.
The only reason that I didn't upgrade from VS 2010 to VS2013 is The disappearance of Project Setup Deployment to third party vendor and find difficulty of how to use it.
Sorry, I mean VS2012
Reading all these comments would be funny if it wasn't so sad and frustrating. Clearly tone deaf is the Visual Studio IDE Services team.