Bring back the basic setup and deployment project type Visual Studio Installer.
You really need to bring back the basic Setup and Deployment project name Visual Studio Installer. It was a clean, simple, and effective installer for home grown applications that were to be deployed internally. I downloaded and used InstallShield LE and it's too complicated and overblown to build simple effective install/uninstall capabilities. Why did you remove it to begin with? We have to support desktop applications for the foreseeable future.
Jesper Funk commented
Make our life easy again and give us the setup project template back in vs 2012 at once! Keep it simple is the main target for us.
why i have to use vs2010 to create setup project, please bring back the setup project in vs2010
This is one of the things I don't like about Microsoft. In this way they don't make friends.
More than 10 years I am developing software, .Net from the very beginning. All the time I never needed InstallShield, why should I use it now ???
That's really very rude !!!
عمار القرشي commented
yes bring it back or we will migrate from MS technologies to another technologies
Setup Guru commented
Please bring it back - it was doing the job without much effort to use such complicated deployment systems like Cruise Control or to list every and each single new file like Wix.
Bring it back the Deployment Project. And if improve it!!!
This is very bad step by Microsoft. Please bring back the basic Deployment Project.
Is this a joke or new reality? I and many of those who I know do not consider this to be a small deal. As such - it's a deal breaker. We do not care if MS ever put a small letter notice on one of their millions of pages stating that setup projects will be deprecated without decent alternative and migration plan. Decision like that is hurting productivity and expressing the truth by thousands of us, screaming right into your ears, on your very own pages cannot go unnoticed. If it will - time to move on to alternative platforms that will let us focus on making a dough and not wasting our time in writing probably pointless messages like this one. WOW.
Harrison Moccio commented
All of the internal line-of-business applications I have developed for my company have been packaged with MSI installers. It allows for quick deployment in emergency situations and revision control. This is one of the last major hurdles we're facing when it comes to upgrading from VS2010. ClickOnce deployment is not expansive enough for our needs, while we find 3rd party wizards like InstallShield too bloated and overtly complicated -- MSI was a perfect balance.
Faisal Ahmed Farooqui commented
please bring it back, millions of developers are suffering due to this.
Faisal Ahmed Farooqui commented
yes pls bring back setup and deployment project in VS2012. millions of people would suffer due to this.
Gian Piero Anselmi commented
Just few reasons to integrate setup technology
1) Compatibility is broken
2) ALM is not complete without deployment solutions
3) WIX should really be sponsored by MS since its inception
4) IS, in its complete form, is very expensive
5) integrating 3rd party "light" tools has not been a winning solution for MS customers since Visual Basic 4 (see, for example, ComponentOne)
6) MSIExec is a MS service do dev should be able to develop against it with MS tools
jens bylehn commented
Yet another blunder... First the start menu..then blend now this...
MS eager to become something else makes them forget to check for babies in the bath water before throwing it out.
Don't remove things that people use and like ! Especially don't replace it with solutions that does not work, that's like ******* of people twice...
Is MS actively trying to alienate both users and developers alike ?
Dependencies? No! Existing solutions pre VS2012??? NO!! I don't mind changing but give us something that works and lets us migrate our existing solutions. Wouldn't Microsoft want to encourage rather than discourage adoption of VS2012? I guess not
Please bring back the Setup and Deployment project in Visual Studio 2012 ASAP.
Ed Chavez commented
@DG - its not "gone" they (wrongly) forced devs to use a *3rd party tool* instead of simply offering another option.
The 3rd party tool is free for the most basic version. But yes, that's not the point. They shouldn't have deprecated! The 3rd party tool doesn't even get to parity with ease of use! See my comment on issues regarding dependencies - big fail on this 3rd party tool (non existent issue with the original Setup and Deployment tool in VS 2005 - 2010!!!).
DG commented · Just Now · Delete
What is wrong with Microsoft? Some of the decisions they're making are really baffling and make no sense. Why take away something that is a vital part of a complete tool system. Now VS2012 is incomplete with the setup project gone. How does this work to Microsoft's advantage? Or am I missing something here?
If WIX was the way forward and is indeed being used by VS Team.. then why not include it as a replacement IN the VS2012 suite?
This "use ISLE" or "WIX" is never helpful.
I'd love a better replacement to VDPROJ and if you see WIX as this replacement.. then so be it. Build out the toolkit. Really support it for all projects: NT-service, desktop, metro, etc.
Ed Chavez commented
While you can suggest a 3rd party tool so Developers can choose, it was folly to deprecate your own tool for a 3rd party only option!
ISLE can't even cleanly identify dependencies, tags these as "warnings", which means the build will not fail (and it should fail with this fatal error!). Of course the build will *not work* without the dependencies! What kind of build tool does that??? Never had to go through hoops for this simple task!
The exclusion of a simple setup and deployment project type is keeping many of my clients from 'upgrading' to VS 2012. Please bring this project type back!