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
Sign in
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Jeff shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    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

    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

    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.


    Sign in
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      • Ade 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.

      • Clay commented  ·   ·  Flag as inappropriate

        I've tried InstallShield LE and it crashes my VS2013 instance every single time. I've uninstalled and reinstalled. I can get no support from Flexera because I have the LE edition. Dropping the setup and deployment project from VS and making us use InstallShield LE has been disastrous. What are we supposed to do?

      • Jen commented  ·   ·  Flag as inappropriate

        I know you want to get rid of bloat, but don't get rid of stuff the majority of us actually use, depend on, and now ask for.

        Rejecting 6k votes (a lot more if it was still open) shows your fingers are firmly in your ears. Again.

      • Anonymous commented  ·   ·  Flag as inappropriate

        I have now been looking at most free tools and none of them are as easy to use and complete as the Visual Studio Installer is in VS2010. Also, SQL projects in VS2013 cannot produce an install script if it doesn't have access to the SQL server. VS2010 has no such trouble.

        I guess VS2010 is the latest and greatest Visual Studio from Microsoft. The later ones are simply beta versions with many features lacking.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Hi Team,

        Please bring back the Visual Studio Installer.. which is very simple and clean. Its a basic requirement for many developers.

      • Anonymous commented  ·   ·  Flag as inappropriate


        please bring back the Visual Studio Installer.. which is very simple and clean.

      • Erez Lerner commented  ·   ·  Flag as inappropriate

        Dear Microsoft team,
        Give us a simple solution to this scenario: We have dozens of projects written using VS2010 all with buit-in setup. Now these setup projects will not even open in VS2012.
        Why don't you supply a simple pach to include the old installer support from VS2010?
        This is what we do anyway. When we develop using 2012, we package it using 2010.
        And we think twice before staring a new project in 2012.
        Is that what you wanted???

      • Long John commented  ·   ·  Flag as inappropriate

        Deep down, I'm actually glad that setup/deployment projects aren't supported by VS2012/13 - it gives me a better reason to deny migration than just "UI is shi t, no macros"

      • Morgan Gardiner commented  ·   ·  Flag as inappropriate

        in all of these discussions I have not heard from Microsoft and the Visual Studio folks what the reasoning was behind the decision to no longer support an installer within the Visual Studio Development software. could Someone from MS Visual Studio explain why the decision was made?

      • Anonymous commented  ·   ·  Flag as inappropriate

        @Lars-Erik Aabech:

        Try Inno Setup or NSIS (both are free open-source installation system) which should suit all your needs.
        There is also 3rd party extension which integrates them with Visual Studio so you can again made installers directly in VS without any other IDE.
        (Works for VS 2005/2008/2010/2012 and even for 2013! - www.visual-installer.com)

      • Robert Bissonnette commented  ·   ·  Flag as inappropriate

        So how about it Tony, ready to come back and respond in favor of your customers?

        How many hours of time do you think this decision has cost your customers?
        How much money has been lost because your customers had to either buy another product or wasted undue amounts of time using new language features that you can't use in vs2010? (where most of us are sticking)

        Does Microsoft even care anymore about its image or its customers or is it after money from third parties to bundle up?
        How about you man up and say we made a mistake and we will be bringing back the setup project, instead of just IGNORING us.

        How about you take a look at the number of votes again and figure out just how much of an a** you are being about this by saying it is not a hot or top issue.
        How about you admit that Flexera's solution is not meeting customers' setup needs with no-cost tooling that supports a broad range of scenarios?

      • Anonymous commented  ·   ·  Flag as inappropriate

        Please bring back the setup project in VS 2013! We don't want to depend on another third part vendor.

      • Lars-Erik Aabech commented  ·   ·  Flag as inappropriate

        Installshield still sucks in VS2013. It just crashed my VS, and is generally too hard to learn.
        I want a simple, built-in setup project.
        Depending on partners for something this important for developers is just lazy.

      • Rauf Abid commented  ·   ·  Flag as inappropriate

        Hello Microsoft,
        Installshield LE does not provide single setup solution, It does not allow us to add prerequisite files manually but have some ready made prerequisite already included in it. I really hate this nonsense. Please Microsoft bring back your native setup creation again plzzzzzzzzz.

      • Sheldmandu commented  ·   ·  Flag as inappropriate

        What a pathetic excuse for such a company. At least give us a decent answer for why all of a sudden setup projects were dropped. Oh wait, you cant because the answer is you're getting kickbacks from the 3rd party vendor of a ****** solution that most developer won't want to fork out on anyway. This is exactly the reason why people will just keep sticking with VS2010, which means less revenue from VS sales.

      • netasp commented  ·   ·  Flag as inappropriate

        We will never upgrade our VS 2010 only for that reason, should M$ continue to ignore us, we will have to look elsewhere and I am sure M$ couldn't care less

        very sad...

      • Billy commented  ·   ·  Flag as inappropriate

        Microsoft, give people a good vdproj to wix or installshield converts and people will shut up and resuming thinking you are awesome. The tool from add-in express (wix) and install shield cost and the free versions suck. Microsoft, Apple looks appealing. Once you go Apple, you never go back to Redmond.

      • Billy commented  ·   ·  Flag as inappropriate

        Ridiculous. So, Microsoft is copying Apple (it never does anything original) and betting on its windows store because Apple and Google are doing that. Fine. Just stop throwing the legacy windows app developers to the curb; especially those that cannot kick Microsoft to the curb back, and where it belongs. Come on. Instead of deprecating this outright, why not be like LINQ-to-SQL and have it working, although no updates are forthcoming.

      Feedback and Knowledge Base