Visual Studio 2005 takes *forever* to load a project

March 14, 2007 · 1 min read

I don't know if anyone else has experienced this, but it is getting pretty annoying.

I have a VS2005 project that is version controlled with VSS.  When I open the project, it takes up to 4 or 5 minutes to open.  This time I did a little digging, and see that the devenv.exe CPU is at from 15 to 40%.  Watch the network, and I see that it is very busy reading data.  Nothing else going on, it is definitely VS2005...  Most likely going to my VSS server. 

By the time the project finally opens, it has used 3.5 minutes of CPU, and received over 300MB over the LAN, and sent over 50MB.

The entire directory tree of this project, including the dll's and exe's that are not version controlled, is only a little over 10MB. 

Anybody else ever see such a problem?   Any suggestions?   I'm stumped...

Edited 3/15/2007:
If you look in the feedback, you'll see someone suggested turning off AntiVirus.  I don't know why VS2005 / VSS has this problem, while earlier versions seem just fine with the AntiVirus turned on, but sure enough, I turned off Norton's "Auto-Protect" temporarily, and my 5 minute load came down to about 30 or 40 seconds.

This article is part of the GWB Archives. Original Author: Brian Biales

New on Geeks with Blogs

  • We Won The One Award I Actually Care About

    Full Scale made the Inc. 5000 for the fifth year straight, the 12th listing across my three companies. Here is why the one award you cannot buy is worth stopping for.

  • Your Customers Build the Features Now

    I let a tool I liked sit dead for a year rather than build the features I wanted. An MCP server meant I never had to, and your customers can do the same to your product.

  • Get the Size of a Directory in Linux the Easy Way

    du -sh for the quick answer, ncdu for the cleanup, df for the disk itself: every command for checking directory size in Linux, plus why du and df never agree.

  • Vim Search and Replace: The Ultimate Guide

    One :%s command replaces every match in a file before a find dialog would even open. The Vim substitute patterns worth the muscle memory: flags, ranges, capture groups, and multi-file edits.