I suggest you ...

Make the installation of Visual Studio light-weight and fast

Installing Visual Studio takes too long

There's a lot of stuff that the VS installer installs that I probably never is going to use.

Make modules and packages install when needed. The Office-install has had this option for ages, where you can deceide whether you want to install a feature a) now, b) when needed, or c) never. That way the basic install will probably be a lot faster and it will take up less space on our drives (how many terabytes of never-used-features do you think VS is accumulating worldwide?).

I belive you already have the package system to handle this (nuget), so eat some of your own dogfood and show us that the package system can handle app installs as well :)

1,999 votes
Sign in
Password icon
Signed in as (Sign out)
You have left! (?) (thinking…)
Kjetil Klaussen shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

We’re delighted to say that Visual Studio 2017 is now released, including a completely revamped installer in response to this and other feedback. The smallest installation of Visual Studio is one-tenth the size of previous versions and takes on average just three minutes to install. Build-to-build upgrades take just a minute or two. You can select a workload of your choice – we won’t install things that you’re not going to use.

To the proposal, we support in-product acquisition of components on demand. You can just hit Ctrl+Q (quick launch), type the feature you want, and we’ll take you straight into an installation experience for that feature.

Thanks for the great feature request – we hope you like Visual Studio 2017! Download it from http://visualstudio.com.


Sign in
Password icon
Signed in as (Sign out)
  • Rudi Larno commented  ·   ·  Flag as inappropriate

    @smashing-your-customers. I agree they are going the wrong way, and (imho) are loosing a lot of credit with their developer community. They could (and can) build great products/frameworks and let the 'absolute awesomeness' of their products/frameworks sell themselves. The forced MS-Marketing-Push-It-Down-Our-Throats approach of old (regarding Metro/Windows) is in stark contrast to the way the Scott's (Guthrie and Hanselman) are providing an effective, popular and open web-platform.

  • smashing-your-customers commented  ·   ·  Flag as inappropriate

    The only problem I see with this is, how would MS push people to develop for whatever "hot new thing" they're pushing? When Silverlight was all the rage, they knew they had you because tools/support could not be removed during a VS install. Now they're pushing Metro/WinRT apps, and the install options are even less than 2010.

  • Philippe commented  ·   ·  Flag as inappropriate

    If the editor is opened to show a specific file, then it should open fast (possibly in an already opened IDE) and without any errors. For an unknown reason, when I open a file from PureCM, It open a new Visual Studio 2008 IDE insteand of (2010 or 11 Beta) and then display an error message.

    When Visual Studio 11 is opened, it is much faster to drag the file from Windows Explorer (than to open it from our source control software which is PureCM).

    Maybe files should be opened in a more light weight IDE somehow like Express edition. There would be syntax highlighting but not all the extra... but in my opinion, the real improvement would be to delay load all stuff related to project/solution and add-ins so that when opening a simple file, we won't have to wait on that.

  • Hossein Aarabi commented  ·   ·  Flag as inappropriate

    I belive this is planned by MS, according to MS comment on a similar request.

    No edit functionality? hmmm

  • Dennis commented  ·   ·  Flag as inappropriate

    This is essentially what they are doing with ASP.NET MVC4 Beta. Now they just need to stay on that path and do the same thing with all the other project types.

  • Stephen Price commented  ·   ·  Flag as inappropriate

    Yes please! Would love to see VS make notepad look bloated. I mean, these are *just* text files we're talking about here.

  • Odoardo M. Calamai commented  ·   ·  Flag as inappropriate

    Make the MsiInstaller more Friendly and Clean without the bad habit of leave waste User space of clobbered data.
    Cleaning the storage space used for preparing to install any program, must be executed by any installer.

  • Dan Finch commented  ·   ·  Flag as inappropriate

    This would be great. I've installed the VS Integrated Shell with only one language, and it was very snappy.

  • Pawel Pabich commented  ·   ·  Flag as inappropriate

    Create a fast, lightweight version of VS that is focused on code only. Yes, remove all designers.

  • jeffpierson commented  ·   ·  Flag as inappropriate

    @Lex - While what you suggest in terms of using something like LinqPad is what many of us do, there is no reason why Visual Studio couldn't support a more modular lightweight version of it's editor so that we get behavior (think highlighting, shortcut-keys, ...) that is more consistent with what we are used to when working on whole projects/solutions in Visual Studio. Using two tools for the same type of activity is just less productive overall. With my experience at Microsoft back about 8 years or so ago, most developers I worked with wouldn't touch Visual Studio except for a few required cases and instead worked with command line builds and separate editors of choice. Now that VS has MSBuild feature parity for the most part it has improved a lot and I'm assuming that Microsoft's internal developers are warming up to using Visual Studio themselves but I think not having a lightweight editor is probably one major roadblock for them just as it is with other developers who need to work with Visual Studio but not necessarily exclusively. Also note that with a more modular approach it may make strengthening the XAML editor in Blend easier since the same editor could be embedded or opened up externally if needed. Without going on any more than I have, I could imagine lots of benefits could come of this.

  • Asbjørn Ulsberg commented  ·   ·  Flag as inappropriate

    @Lex, although the concrete proposal doesn't necessarily benefit everyone, the spirit behind it (make Visual Studio more modular), does. I hate that Visual Studio is a 1.000.000 lbs gorilla that is chronically unable to quickly open and edit a .cs file in less than 5 minutes. Having to load all of the designers (of which I use less than 0%), incredibly complex configuration options (of which I use less than 10%), intellisense runtimes for languages that aren't in use, etc., is incredibly annoying.

    Visual Studio should be able to open a .cs file in much less than 1 second by only loading the bare minimum set of components required to edit C#. It should open a C#-based solution in at least no more than 2 seconds, by not having installed all of the funky and useless designer **** and configuration options that I just want removed.

  • Anonymous commented  ·   ·  Flag as inappropriate

    I posted the following on another page, but its worth putting here again.

    We don't always need the ability to compile, just a lightweight text editor is enough.

    How often have you accidently went to open a web.config on its own to pull out a connection string only to groan as you see the VS splash screen sitting there. There are a couple of things you could do here:
    1: make visual studio smart enough to realise when you're opening a single (non .sln/.csproj) file to spin up a lightweight version of the editor. Something like this got installed as a side effect of putting vwd express on my web server. Its very quick, has intellisense and the 'correct' vs color coding
    2: Throw up a prompt - 'Are you sure you want to use VS for this single file?'
    3: Buy out editplus, replace notepad with it and make it the default text editor. Or at least see how they get so much functionality in a 900k exe :)

  • Lex commented  ·   ·  Flag as inappropriate

    It would be nice to have this, but at this stage I'd suggest it's more realistic to look in tools like Linqpad which are built around your lightweight scenario.

  • jeffpierson commented  ·   ·  Flag as inappropriate

    There are times when you just need to open a standalone code file written in something like C# for viewing or editing but don't want the burden of the whole IDE especially with it's slow load time. What I propose is make the Visual Studio Editor a separate invokable application on it's own or make it so that when Visual Studio is started up with a file path(s) feed in as run time arguments, then load the IDE in a minimal state tailored to working with a single file. Providing this functionality would allow some programmers who chose to manage their projects outside of visual studio through build files and such to still use Visual Studio as a powerful code editor instead of falling back on other products like Notepad++, Vim, SciTE, and the like just as was the practice when I worked with Microsoft back in the day. Just simply matching performance of these other tools when of launching VS would go a long way but any other effort to help supporting this mode of development would probably open up the use of products such as Visual Studio Express for general code editing and then may serve as a gate way for developers to get more acquainted with Visual Studios who otherwise would not use it.

  • Sherif commented  ·   ·  Flag as inappropriate

    This isn't fair. They made me think VS 2010 is a very big IDE and its size's increasing year-by-year. VS 2010 Professional is smaller. I hope my voice's heard and the Express became a one small IDE and when they release VS 2012, I won't have to download the size twice.

  • a.jeckmans commented  ·   ·  Flag as inappropriate

    This is already the case except for the Express editions. When you install lets say VS 2010 Professional it will ask you if you want certain features installed or not including support for c++, vb.net, c#, web developer etc.

Feedback and Knowledge Base