in

ASP.NET Weblogs

Alex Chang's WebLog

A fix for when Visual Studio .NET is slow in starting up/opening

One of our developers had been suffering from extremely slow load/start-up time with the Visual Studio .NET 2003 on his developement machine (it took more than 1 minute to get through the splash screen). He tried uninstalling and re-installing VS.NET, but the problem still persisted. So today, I set out to find a solution. After about an hour of googling and searching on the web, forums, blogs, and newsgroups (it seems that there aren't that many mentionings of this issue out there), I finally came across a posting that lead us to the fix:
http://dotnetjunkies.com/Newsgroups/microsoft.public.vsnet.ide/2004/3/29/97325.aspx

What caught my eye was that, as mentioned in this newsgroup posting, we also noticed that the slow start-up problem only occurred when the developer's workstation was connected to the network. Visual Studio.NET would load without delay when we disconnected the network cable from his machine. The newsgroup posting pointed out that this is an issue with the MRU list (Most Recently Used list). We think that our developer may have tried to access/open a solution or a project across the network some time in the past. So Visual Studio.NET must've cached the file references in its Most Recently Used list. So everytime the Visual Studio.NET launched, it may have been trying to find those files on the network (which may no longer have existed). The recommended fix was to set the number of the display items in most recently used list to 1 (1 is the minimum number, default is 4 I believe) from the Tools->Option menu to clear the MRU list.  However, after setting the MRU list to only display one item, the problem still remained! After further searching on "Visual Studio .NET MRU list", I found one of the Developer PowerToys (http://www.gotdotnet.com/team/ide/) called VSTweak.  This nifty tool has a MRU Lists Manager that allows you to clear recent files and projects.  After clearing out the MRU lists, the Visual Studio .NET launched in a heartbeat without any delay.  Woo hoo!

Hope this is of help for some developers out there.

Published May 04 2004, 09:18 AM by AChang

Comments

 

jledgard said:

Glad I was able to help. (I wrote the MRU piece and a bunch of VSTweak.)
May 9, 2004 1:15 AM
 

Henrik said:

Thanks!!! This saved me a lot of time, was just about to format my harddrive.....

Regards
Henrik
June 1, 2004 8:40 AM
 

Kristopher said:

We had a simliar problem with one of our Win2003 Server boxes using FP server extensions with VS.NET (projects taking > 5 minutes to load). The log authoring option was enabled for the site, however, the FP process did not have write access to the author.log file.

Disabling logging or granting the appropriate permissions corrected the problem.
July 10, 2004 11:49 AM
 

Philippe said:

My vs 2k3 instance would take about 5 minutes to load and 5 minutes to add a simple file to my project. This was happening to accounts on the domain but not local accounts. The MRU trick mentioned didn't help (this list was empty). After a while, only my account and the administrator account exhibited this weird behavior. I removed myself from the vs debuggers group (in admin tools) and now it works normally.

At least vs.net 2k5 ran fine all throughout this process.
July 23, 2004 3:35 AM
 

Raterus said:

Thanks, this worked great!
August 9, 2004 4:07 PM
 

FocusedWolf said:

Wow can't wait to see if this works! thx m8.
August 19, 2004 5:04 PM
 

TrackBack said:

^_^,Pretty Good!
April 10, 2005 2:19 AM
 

at2000_zm said:

VS can load the app very slow if you have set many breakpoints. i have come across a link that provides excellent solution to this problem. it can also be used for other purpose also.

saurabhramya.googlepages.com/save%26loadbreakpointsinvisualstudio

June 7, 2008 9:36 AM

Leave a Comment

(required)  
(optional)
(required)  
Add
Terms of Use