Accelerate Visual Studio Part III. IDE performance

After writing the last article , I realized that I still have a certain amount of information that is not related to speeding up the compilation of the solution, but allowing some improvement in the performance of Visual Studio itself while working on the code. And since we are still working on a fair amount of time on the code, it is much more pleasant to do this in a fast-running IDE. Unfortunately, in this article there will be no graphs, since it is very difficult to measure how much a menu or some window has become faster to open. Nevertheless, I hope that someone can find something valuable in these tips and save himself some time.


Add / nosplash to Visual Studio launch shortcut
To be honest, the launch time will not decrease much, but psychologically it will seem that Studio is loading faster.

Disable the F1 button
This is done in “Environment-> Keyboard”. You don't use this button anyway, right? And if you accidentally click, then, depending on the version of VS, new windows will start to open or the browser will start up - all this for a very long time.
')
Turn off the animation
"Environment-> General-> Animate environment tools". Leave the animation fans beautiful. And after all we are severe programmers, to us to what.

Disable Start Page
It takes time when launching a studio (especially if it climbs the Internet for all sorts of news and advice). Disabled in “Environment-> Startup”.

Turn off "Track Active Item in Solution Explorer"
Do you really use it? If not, turn it off. Disabled in Projects and Solutions

Turn off a variety of beautiful
Here it is written about it in more detail. Disabled in “Environment-> General-> Visual experience”

Removing extra plugins
Each plugin is a minus to the productivity of the Studio. If you have something extra - delete.

Disable IntelliSense
If you use IntelliSense and are completely satisfied with the functionality and operation of this feature - you are a rare person. Perhaps you should get acquainted with such plug-ins under Visual Studio as ReSharper and Visual Assist X. They are well worth their price, replace IntelliSense and do a whole bunch of other useful things. If you have one of these plugins, it makes sense to disable IntelliSense. There is no regular way to do this, so we will shamanize.

• Close Visual Studio.
• Delete all .ncb files for your solution.
• Delete or rename the file C: \ Program Files \ Microsoft Visual Studio 9.0 \ VC \ vcpackages \ feacp.dll (the “9.0” part is different for different versions of Visual Studio).

Update : Habrayuzer Paul suggests that in VS 2010 IntelliSense is turned off already through the settings.

Starting Studio and compiling a project before coming to work
On my working machine every morning, an hour before my arrival at work, a script is launched that closes Visual Studio, makes update code from the repository and starts Studio in a new way and compiles the solution in it. Coming to work, I see an open IDE in which the current state of the solution is immediately visible (compiled / not) and the update procedure log, which makes it clear what has changed since yesterday evening. All this saves me 10 minutes daily.

Good luck to you!