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.
Jeff
shared this idea
451 comments
-
Anonymous
commented
Anybody from Microsoft care to comment? Single sentence maybe? No?
-
Hesham Mahmoud commented
I simply can't see why would you remove it
-
Anonymos
commented
Anything about the reason why this was deprecated???
Still can't belive it. -
John
commented
I simply cannot believe that MS have dropped this support - MS are fast becoming non-friends of developers and I've been using VS for a decade now.
Why do they keep doing this stuff to us??
-
Miguel Ganilho Santos
commented
Without it I'll downgrade to VS2010!
-
Richard Beverly
commented
Can you please stop the insanity. If you introduce a project type please stick with it. Database projects.... setup projects.... reporting projects..... integration projects. We invest time and money into these artifacts and with every new release of VS there are changes with little support for upgrade paths.
-
Biff Gaut
commented
Dropping the ability to deploy is an inexplicable decision - what the heck is going on in Redmond the last few years? Alienating your base will not push us to Azure, it will just alienate us.
-
debuggio
commented
Please, bring setup project back!
-
Jack
commented
please do, installshield is pants
-
khaleel zrb
commented
we want this setup because we not have money to purchase installshiled
-
Anonymous
commented
without it, deployn a setup becomes tidious for beginnes! Aaaaaah!
-
Anonymous
commented
MS, please bring back the old Setup projects. We don't need more features!!
I will stay in VS 2010 and I hope until my retirement (just 10 years) if it isn't so. -
Anonymous
commented
bring back the basic Setup and Deployment project name Visual Studio Installe
-
Pep
commented
This is a really bad decision!!! Luckily we migrated our setup project into Inno Setup - there is .vdproj to Inno Setup conversion extension (http://visualstudiogallery.msdn.microsoft.com/5e57fe9a-ae5d-4740-a1c3-7a8e278e105b) so we saved a lot of time.
The next time I think a C++ projects will be banished from Visual Studio, won't they?! -
Ashish Gupta
commented
It is very bad that such an basic deployment tool has been removed from the VS with out much of a choice and warning.
Migrating from VS 2010 to 2012 is a pain now.
-
Anonymous
commented
Stop wasting our time and money, and bring back the old setup and deployment project!!!
-
Emile Abou-Mrad commented
BRING BACK THE GOOD OLD SETUP AND DEPLOYMENT PROJECT. Or at least give us a believable explanation on why you removed it.
-
Ibrahim
commented
I am at a loss for words because I find it oh so difficult to comprehend the mindset that felt that removing the basic setup and deployment project could have any beneficial results for the visual studio eco system.
Bring it back!
-
Caesar Moussalli
commented
The worst Decision in VS .... since 2002
-
Wayne
commented
Seriously??? You mean I need to revert back to VS2010???
Microsoft, what happened to you? It seems that too many things have caused me to raise as eyebrow at your apparent lack of understanding the audience. This is why I quit putting all my effort into Microsoft like I used to, and started getting more into Google et al.
Microsoft...you are becoming has-beens. Knock it off already.
