Recently I’ve been getting pretty annoyed by my Visual Studio 2008, which has been taking longer and longer to do my favorite menu item, Window > Close All Documents. Today was the last straw — I decided 20 seconds to close four C# editor windows really isn’t acceptable for a machine with four gigs of ram, and so I went to look for some fixes.

Here are some of the good ones I found that worked. Use at your own risk of course!

Disable the customer feedback component

In some scenarios Visual Studio may try to collect anonymous statistics about your code when closing a project, even if you opted out of the customer feedback program. To stop this time-consuming behaviour, find this registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0\Packages\{2DC9DAA9-7F2D-11d2-9BFC-00C04F9901D1}

and rename it to something invalid:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0\Packages\Disabled-{2DC9DAA9-7F2D-11d2-9BFC-00C04F9901D1}

(source)

Clear Visual Studio temp files

Deleting the contents of the following temp directories can fix a lot of performance issues with Visual Studio and web projects:

C:\Users\richardd\AppData\Local\Microsoft\WebsiteCache
C:\Users\richardd\AppData\Local\Temp\Temporary ASP.NET Files\siteName

(source)

Clear out the project MRU list

Apparently Visual Studio sometimes accesses the files in your your recent projects list at random times, e.g. when saving a file. I have no idea why it does this, but it can have a big performance hit, especially if some are on a network share that is no longer available.

To clear your recent project list out, delete any entries from the following path in the registry:

HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\8.0\ProjectMRUList

(source)

Disable AutoRecover

In nearly four years, I have never used Visual Studio’s AutoRecover feature to recover work. These days, source control and saving regularly almost entirely eliminates the need for it.

To disable it and gain some performance (particularly with large solutions), go to Tools > Options > Environment > AutoRecover and uncheck Save AutoRecovery information. (Cheers Jake for the tip)

(source)

August 24th, 2009 | 7 Comments
7 Responses to “Does your Visual Studio run slow?” Leave your Comment
  1. Arjan’s World » LINKBLOG for Aug 24 2009 says:

    [...] Does your Visual Studio run slow? – Richard Dingwall Yeah it does? Everyone’s VS runs slow. Here is how to – hopefully! – speed it up a little [...]

  2. Ron says:

    Running slow due to development of heavy page size. Any way to hide the gridviews I aren’t working on during development???

  3. Jake Scott says:

    You can disable auto recover files.. have a read of the comments on this blog post…

    “I’ve opted out of autorecover before. On one of my computers, every 5 minutes the UI would become unresponsive for several seconds because AutoRecover was processing. It was very annoying. So I turned it off.”

    http://blogs.msdn.com/saraford/archive/2008/02/14/did-you-know-where-visual-studio-saves-auto-recovered-files-in-the-case-of-an-unexpected-shutdown-151.aspx

  4. Richard says:

    Cheers Jake, added it to the list

  5. Dev1000000 says:

    >>> auto recover files..

    You can stop trying to help me now microsoft! A common MS theme is to try to help users too much at the expense of performance and usability. Really needs to be a setting in all MS products for “user level”. If I’m an experienced developer, let me set the “user level” accordingly.

  6. Matt says:

    If you find that deleting a file directly from the IDE takes a long time, empty your recycle bin. I have no idea why this only seems to affect an IDE delete but it does make a BIG difference

  7. Neil says:

    @Matt – I found this too, but thought it was TortoiseSVN causing the problem.

    btw, now I run CCleaner often and it deletes all these temp files and Recycle bin files in one shot.

Leave a reply

We love to hear your views.