I suggest you ...

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.

6,178 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Jeff shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    UPDATE:
    We have just released an extension which delivers the Visual Studio Installer projects functionality present in Visual Studio 2010 for Visual Studio 2013.

    To find out more please read Visual Studio Installer Projects Extension

    Tony Goodhew, Program Manager, VS Pro

    UPDATE:
    We have more information on the next version of InstallShield Limited Edition that will be included in Visual Studio 2013.

    What’s new in Visual Studio 2013 and InstallShield Limited Edition

    ORIGINAL:
    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.

    832 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • GreenhillSoftware commented  ·   ·  Flag as inappropriate

        Thank you, thank you, thank you.
        Round trips back to VS2010 were causing me problems and I do not currently have time to get to grips with WIX.

      • David Lowndes commented  ·   ·  Flag as inappropriate

        Thank you, this is very welcome news.

        Now, how about providing something truly better (not ISLE) for the next version of VS?

      • Anonymous commented  ·   ·  Flag as inappropriate

        This is truly great news!!!
        There are situations where migration to Installshield or WiX is a viable option and I have gone through that migration wherever there was a possibility, but there exists a ton of smaller installer projects that it would take too much time and no actual gain to migrate them.
        In the end, people that were stuck with a situation like this used VS2012/13 for regular devlopment, and vs2010 for compilation of the setup project. Having a backwards compatible extension for the setup project for vs2013 is a great solution that should satisfy everyone.

        Thanks.
        PS. This is the first time I actually see user votes working :)

      • Dennis Geasan commented  ·   ·  Flag as inappropriate

        Good to hear that Microsoft has listened and brought back the VS2010 installer. However, having now used both the old and new installers, I will be staying with the new Limited Edition. True, there is a bit more to learn but it does provide more features than the old and really isn't that tough to learn and work with. And, there is an upgrade path available if necessary. I suggest folks give it a try and then decide. You might like what you see.

      • Mike commented  ·   ·  Flag as inappropriate

        Dear Satya Nadella,
        I would like to thank you for bringing back the basic setup and deployment project type for Visual Studio 2013. Microsoft is going to right direction now.

      • anonymous commented  ·   ·  Flag as inappropriate

        please bring back the simple installer project. I cannot believe MS is ignoring its developer base in exchange for kickbacks from Flexera.

      • Hans Larsson commented  ·   ·  Flag as inappropriate

        I uninstalled VS2010, then installed VS2013. After a while I realized that all my setup-projs should not work. I do not have the time to learn a new installsoftware. The ligthInstallshield is ****. So I reinstalled VS2010 and realized the all the money for buying VS2013 went up the chimney...

      • Tanvir commented  ·   ·  Flag as inappropriate

        please Bring back the basic setup and deployment project type Visual Studio Installer. Because it was simple and quick.

      • ThomasX commented  ·   ·  Flag as inappropriate

        [Reopened because of accidental decline]
        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.

      • Umbara Gedaf commented  ·   ·  Flag as inappropriate

        That's why I will buy the next visual studio from the "torrent shop". It seems I have to spend the money of the VS2013 for the conversion of the deployment project to another installation tool.

      • Riz commented  ·   ·  Flag as inappropriate

        Please bring back the setup project in Visual Studio 2013! Neither we want to depend on another third part vendor nor we want to make it complicated. Setup and deployment project was too simple to handle.

      • James Dennis commented  ·   ·  Flag as inappropriate

        I cannot vote and that is preposterous. I am not pleased with this decision by Visual Studio. This decision appears to have been made without any consideration for their dedicated customers and their business needs. Can the Visual Studio team provide some data that shows that this decision was necessary and inevitable?

      • Jen commented  ·   ·  Flag as inappropriate

        You can't vote because they don't care.

        Having 15k+ votes would be too embarrassing for them to ignore.

      • Phil Leitch commented  ·   ·  Flag as inappropriate

        I can't vote, if I can't vote how can you be made aware that your decision to decline is wrong?

      • Anonymous commented  ·   ·  Flag as inappropriate

        It would be difficult for you to add enough productivity improvements to VS to counteract the huge loss in productivity this is causing me. Please reconsider your decision.

      Feedback and Knowledge Base