The official source of product insight from the Visual Studio Engineering Team
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.
Too little, too late.
Installshield (extremely) Limited Edition is never, ever going to do what we need because Flexera can't canibalise their own market.
What an incredibly short-sighted, arrogant decision by Microsoft. This does absolutely nothing for developers that rely on you (have you honestly ever seen a single *positive* comment about the change?) and for what? So that you don't have to support a deployment project kit that, let's be honest, hasn't had much work done to it in years (but still does what we need. DLL custom tasks, for example?).
Did someone at Microsoft get their palms greased by flexera for this woeful decision?
Stop tinkering around the edges by seeing what you can tease out of flexera and just fix this godarn awful mistake.
Is it run objective c in VS 2013 ?
Please bring back the setup project in VS 2013!
"...many customers shared feedback through the UserVoice site regarding additional features they’d like to see added to InstallShield..."
Sure, some did, but most of the 6000 comments were asking you to please leave the Setup/deployment project in Visual Studio. This is "spin" if I've ever seen it.
Look, I've been trying to see the good side of this but honestly, after having my forth ISLE deployment crap itself and leave me manually coping and maintaining project DLLs I'm going to start looking at other options for development tools. I don't want to spend weeks learning how to do something simple like deploy a tiny little windows form application that only took me 3hrs to create
You would of thought the number of comments here, on the uservoice and in the VS2013 feedback survey that maybe Microsoft might of thought there was a problem with Installsheild.
Microsoft, like always, are right. It's their user's that are wrong.
The desktop is dead - stop creating applications for it. No body needs a working setup and deployment solution any more.
Metro is the way to go - stop holding on to the 15+ years of investment you have. It's not their fault the Metro walled garden is a failure, it's the arrogance of Microsoft's customers.
Please, listen to your customers. Just hear us. We need vdproj back.
I agree that MSFT makes me feel that developers are increasingly being thrown under a bus.
Lack of migratable setup and deployment is really a BAD thing.
Installshield LE is really just trialware when many essential functions are not available unless buying the full version.
One of the absolutely necessary functions that are not part of LE is running SQL scripts. How can anyone have an installer these days without the ability to also deploy database scripts. Zero value for web-based applications.
InstallShield Limited Edition does NOT support custom actions that use a DLL - so it's completely useless and cannot convert any useful custom actions in existing setup project.
Please bring back the setup project in VS 2013!!!
Frankly we all need the VS2010 features maintaned in the new versions. This is necessary for low price applications that have considerable development investment required due to "per Office Version" strategy.
I have tried the beta version of Installshield LE for x64 without success.
In response to Stephen who wrote ".... What? You still develop those old school on-premise and desktop apps? Wow, you need to re-imagine those as Windows Store and Azure apps! ..."
No application that has technology research behind will ever rely on on-line development. It's like asking car manufacturers to post their tech innovations and research on line for anyone to look at it (after investing hundreds of millions). It's naive to think that anyone going to rely on Microsoft or Adobe or any other company's security with the increasing number of hacking events that have occurred lately.
Microsoft will always have to provide on-premisses desktop development or else someone else will!
Don't really give a rats *** about where the setup project comes from. But honestly if you expect us to use ISLE could there at least be some sort of support.
As far as I see it, their community forums are the only support, and they aren't worth the effort it takes to sign up