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.
Since Microsoft have declined to bring back the basic setup and deployment project type Visual Studio Installer, i think that the first step to to achieve this is to get fire workers and managers who decided to decline bring back the basic setup and deployment project type Visual Studio Installer with 5.828 votes here, on user voice.
RE: You really need to bring back the basic Setup and Deployment project name Visual Studio Installer.
ME: Keep VS clean of ThirdParty please. No more InstallShield LE "WE HATE IT" just like Dotfuscator Community Edition.
Please, keep VS clean. If we want to attach "ThirdParty", we'll do it manually.
It can be great! use only VS for all process: planing, developing, testing, deployment (including Visual Studio Installer as an option for those who want/need to use it)
InstallShield "limited edition" SUCKS OUT LOUD! It is unusable and there is NO SUPPORT from either company. Including Install Shield **** edition makes me question whether we want to continue to use Visual Studio as a development tool. Get rid of that POS and go back to Windows installer or something that MICROSOFT actually SUPPORTS.
So you replace the MSI Project Tool with a solution that costs me another $700 just to get the 'Express Version?' the Premier edition costs $4500.00 - People don't upgrade to Visual Studio 12 if you can possibly help it, if you value the MSI Project Tools.
The replacement is ridiculous! After years of faithfully promoting MS and developing on your platforms since 1995 and convincing my customers not to go to other platforms - you basically turned against me and removed a valuable tool. That move is going to cost me hours of work replacing it. Would it have killed you to keep it?
We have used the Visual Studio Installer for years with great success, even for our Windows services. VS2012 no longer includes VS Installer so we have to use InstallShield Limited Edition. This tool does not even let us manage dependencies without upgrading to a paid version. This is a disappointing drop from VS2012. First Crystal Reports, now VS Installer. What will you drop next?
We have more information on the next version of InstallShield Limited Edition that will be included in Visual Studio 2013.
We’d like to thank you all for your comments on this UserVoice entry. We have been discussing the comments on InstallShield Limited Edition (ISLE) raised here with Flexera and we are currently working with them to address the top issues. At this stage we have no plans to include the former Visual Studio Setup Projects in future product versions but we will continue to work with Flexera and the community to ensure Visual Studio customers’ setup needs will be met with no-cost tooling that supports a broad range of scenarios.
Tony Goodhew, Program Manager, VS Pro.
Hai Microsoft please provide Setup project back
C++ developer commented
Come on you outsourced MS developers, let me finally switch from VS2010 to 2013, missing support for setup project doesn't let me do it!
Bring back the setup project you lazy morons.
I wonder how many votes this would have received if it were still open?
What are you afraid of?
Not implementing the most requested feature?
I honestly wish I was able to ignore my customers like this. Actually, I still wouldn't - I have pride.
I'm glad I kept my VS2010 ISO, seems like there is still a need for it afterall
I wonder how much flexera paid Microsoft to get them to do this bad idea...
The install shield option is horrible, what a mess!
Phil Griffiths commented
VS setup project templates have been around for ages, they worked well for simple deployment to servers or PCs....why remove something that works? Why sod up user interfaces so that they look like the original versions of Windows? Microsoft is letting its developers down.........Mr Tony Goodhew, Program Manager why not listen to the people who buy your products and ultimately pay your salary?
Install shield is a step back from the original simple package and deployment wizard. It is a shame I have to manage my applications installer from VS2010 and and my code package from VS2012. Who's idea was this anyways....
Myles Skehan commented
Interesting. Internal applications only require a lightweight installer (Services, Applications etc) vs deployment project were perfect. I mean they really made my life easy. LE not so.
It is fascinating that a feature with 5K+ votes and now CLOSED to voting is being ignored by Microsoft. I think you need to change the name of the site.... It may be our voice but it will still be ignored. Plus one vote from me
Christian Ruud commented
The ****** installhield project crashes visual stuio half of the time, takse ages when it works, and it won't install my windows service. It doesn't do anything. I've followed the guides for doing it, but it doesn't even give me an error message. It simply finishes the installation without the installer class from the service project beeing run at all
Christo Bezuidenhout commented
Sigh.. InstallShield LE is ****. I first couldn't believe that the old trusty setup project was gone. They are bloody idiots for removing it.
Tried it; hate it.
No one wants InstallShield, is it difficult to understand that?
Vs setup projects were/are simple as fast to program. I don't want to learn a new suite just to make a setup that puts all the files in the correct place and, adds the exe to the path! And please don't come with the: "It's more powerful", "It has more support", "It is easier". Just say: "We want to give more money to Flexera"
Caesar Moussalli commented
Microsoft are destroying them self ....... just return the setup project
Dennis Geasan commented
I've just been thru the install of VS2013 Professional and "InstallShield LE 2012/2013 beta". So far it has been good. I now have a 'Setup' project which in most ways is the same as the VS2010 setup project plus there is some new stuff I didn't have before. I'm still on the learning curve for this aspect of building an application but I'm not finding anything particularly onerous or difficult with InstallShield LE. It is a bit different from the old way but in the 2013 version it appears most everything is there that I had used in 2010. And I like the availability of an upgrade that adds functionality for more complicated installation requirements. Most of the extra stuff that costs money are features that I didn't see in the 2010 setup tools, at least in VS2010 Professional license level. So I say give it a whirl! It's included for no extra money and so far it works.
Q109154: Error -5036 ERRDOC
building an InstallShield project, the following error may occur: Error -5036: Internal build error. This error may also indicate "Fatal Error." This error...
InstallShield Limited Edition gives just error messages. Does NOT work with 2013
Stu Fraser commented
Perhaps this wouldn't be so bad if some actually supported the **** they force us to use.
Right now Flexera support isn't worth the paper I wipe my **** on
Dan Walker commented
I pretty much agree with the people that are saying this is a bad move. ISLE is not an option. It's the worst thing since the square wheel.
VB6 - VS2010 has had a basic (but usable) setup project type, and now you take that away from us while at the same time showing us cool new *toys* like CodeLens but not including it for all paid versions.. only the people that give you MOUNTAINS of money can have toys. Those that bring you a meager wheelbarrow-full - well, we dont get toys, and we can't have the tools we've come to rely on.
I'm completely on-board with the whole "Bite me, I'm moving to Apple" sentiment.