... it might be that you opened a project/solution from a network share which is no longer available, or that is slow to refresh etc... I had this problem myself with Visual Studio .NET 2003 (not Visual Studio 2005 so far, so I'm not sure if this is also affected or not), and took a while to figure out what the problem was.
Procmon and some patience to go through the log pointed me to an interesting registry key: HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\7.1\ProjectMRUList (the same key exists for VS 2005, but it's under *VisualStudio\8.0\ProjectMRUList). This key contains the path of the last 20 solutions I opened/created; what's interesting is that by default Visual Studio does not show all the recent solutions opened (in File menu or in the Start Page) but just the last 6 (I usually change this value to 10), but despite that it reads all the values and (I guess) verify if the solution is still available, thus the delay...
To solve my problem I simply deleted the values pointing to a solution from a network share et voilà, Visual Studio was loading at the usual (reasonable) speed.
Cheers
I use Yellow Cup's MRU Cleaner rather than directly editing the registry. So far I've had no problems with it.
Here's a link...
http://www.csharper.net/blog/mru_cleaner_1_0_0_4___vista_ready_and_stupid_dope.aspx
Seems interesting... I'll give it a try, thanks for the hint :-)
If you find that this does not work, check the other MRU registry entries under visual studio - I was still having long load times on projects after visual studio loaded (small projects too...) - it was the MRU list for the web service references. In VisualStudio\<version>\ServiceReferences\MRUList
You guys are the nuts. Thank you thank you. Such a simple fix that I would never have discovered without the WWW.
Happy xmas :)
Thank you so much! I also had to wait for 30 seconds every time I stopped debugging. This fixed my problem.