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.
I've fought with Install Shield LE for months before I came across this place to complain to Microsoft and to find out it wasn't me not understanding what I was doing, but it was really Microsoft screwing everybody. Put the setup and deployment back in! Now!
1. Just finished installing VS2012.
2. Went to open one of my solutions, a WinForm application.
3. Was notified that the .vdproj could not be loaded.
4. Researched and discovered that the Setup project is not supported in VS2012
5. Cancelled open of solution
6. Closed and uninstalled VS2012
7. Will not recommend upgrade to VS2012 to my customer
I am also missing the installer. It saved so much time! Packaging windows services was a breeze, now, it's a mess!
Well Microsoft, you've heard everyone - so come on, what are you going to do about it for the next version? Many of us are sticking with earlier versions of VS because of this decision even though we'd otherwise like to use VS2012.
While the deployment projects weren't without their problems, they were less that either learning WiX or adopting InstallShield.
maulazyhola . commented
You guys are really crazy hehe... why the **** did you remove this nice feature. I don't have time (as most people sure don't as well) to read tutorials on how to use InstallShield LE.
I've been working with VS2012 for two months now, and it was such a great experience until today when I found the lack of the old setup wizzard.
Please take our opinions into account, hundred of developers can't be wrong.
Seriously,wtf? What was the use-case scenario for removing this?
Yes fire those idiots who took the bribe for this abomination!
Bring back the setup installer. Nobody will use the vs2012. It's pure abomination.
Robert Huang commented
Microsoft, what's matter with you? Your search engine is ******, your mobile OS is ******, your cloud platform is ******. Now the last value you left: developer-friendly is almost gone. I don't believe that there's no objection like us from inside of your corporation. Whoever made this decision should be fired immediately!!
I've been programming on MSFT platforms since the 80s, and one of their most staunch supporters until about 2008, Until then I would defend MSFT without reservation. Removing support for installation projects is just one of countless issues I've had to deal with in the past 5 years however, which has been a nightmare of continuous problems. My support for MSFT has mostly dried up now, and someone there should take notice. If MSFT can lose the support of someone like me, then then they have more problems on their hands than just worrying about Apple, Google and others who have been stealing their thunder for years now.
While i understand the desire of MS to make a buck, why would they not license a copy of the Flexera product which fully supports the abilities of the current MS installer technology included in the VS2010 product and build in a COMPLETE converter so there is no pain to upgrade to their next version vs2012? I mean really, when we are paying several thousand dollars for the development tools they still seem to go out of their way to make it difficult even for their premier customers with the "Ultimate" editions.
I am currrently trying to convert one (just one) installer for a WPF application which has exactly one custom activity - which is not supported as is. Instead i have to build an executable which cannot directly communicate with the install process via the well known mechanisms for properties. Additionally, i cannot use relative paths but must manually edit the ISLE project file to "make it work" with MSBuild on another box. Which if anyone modifies the project or just resaves it, i need to redo the changes EACH AND EVERY TIME!
Really, Microsoft? How many customers did you consult before making this decision to remove the suport for the "basic" installer included with VS2010? Better yet how many "ULTIMATE" owning customers did you consult? I would bet not many - maybe none at all?
Ok, after another hours of trouble with VS 2012 Ultimate I REALLY have enough from VS 2012 Ultimate. I eliminated it and returned to VS 2010.
I am using Visual Studio 2012 Ultimate. I did not succeed installing the "InstallShield 2012 Spring LimitedEdition". After a nightmare of finally getting the correct download-site, and downloading the package, there is NO chance to get it running within Visual Studio 2012. The installation generates a subdirectory within Visual Studios install directory (C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\ProjectTemplates\SetupAndDeployment) but there is NO SetupAndDeployment within Visual Studio to finally use that product.
Now: I cannot generate my install package. Of course I am stressed, now: I MUST deploy, but MICROSOFT hinders me!!!! What a mess!!!
every last year and better.. and every new year something missing
Christian Sanabria commented
why did you eliminate it?? we need it to create web application installers
simply ... Visual Studio is mess ! every time Microsoft release something new ,always are making things more difficulty to work with.
except from the setup and deployment feature that has been removed the User interface is REALLY REALLY BUT REALYYYYY UGLY and NOT FRIENDLY . and what's the reason? the reason is for performance as they said! where in our days the computers are highly delivered with enough good CPU speed and enough memory ! yes you hear well performance is the reason ! i couldn't work more that 1 hour with VS2012 because of the user interface and i really get nervous when is see those stupid black and white icons . Please stop doing what ever you think and before do something ask to get some feedback of what would be good and what not.
nitin jain commented
Need basic setup and deployment project option back in VS2012
Joe Hanna commented
It is simply contempt for the average developer trying to make an honest dollar using the Microsoft platform.
Every release of VS since 2008 has left something or someone behind. They are arrogant enough to deem people who adopt technologies that they have built and we have embraced as unimportant. Who is that made the Windows platform popular? Developers, developers, .... oh you get the idea.
Stop treating us guys that support you with contempt. I now have to maintain three installations of Visual Studio to get my work done.
Steve Littleford commented
Do what you like in terms of pushing us in a direction Microsoft, but leave the old installer there so we can keep our businesses running in the mean time.
Jon Kerr commented
The Clickonce publisher is not a replacement for the old Setup and Deployment system! It is too inflexible and the way it "hides" the executables makes it extremely difficult to troubleshoot anything but the most basic projects.
Bring back the Setup and Deployment system!
way too many idiots workings and getting rid of futures that are necessary for enterprise environment. No wonder companies don't want to adapt to windows 8 and developers wants to move away from VS 2012