This post originated from an RSS feed registered with .NET Buzz by Darrell Norton. Original Post: Why is Visual Studio debugging so slowly? Feed Title: Darrell Norton's Blog Feed URL: /error.htm?aspxerrorpath=/blogs/darrell.norton/Rss.aspx Feed Description: Agile Software Development: Scrum, XP, et al with .NET Latest .NET Buzz Posts Latest .NET Buzz Posts by Darrell Norton Latest Posts From Darrell Norton's Blog

There are many possible causes for Visual Studio (2002 and 2003) to run slowly during debugging.

Antivirus software can really slow down the process, so check there first.

Many times it's a domain issue such as an authentication timeout. Check the event log for errors.

Setting Enable Unmanaged Debugging to true in project properties can also cause debugger slowness. Try setting it to false. Native debugging is slower in general than managed code debugging, so if you don't need to debug Native code, turn it off in the options.

Another possible cause is if you had a Beta or Release Candidate version of Visual Studio .NET installed. There may be no problem initially and it occurs intermittently after a solution gets larger with multiple projects in it.  See Microsoft Support article q312115.

Policy files in projects used in Enterprise Templates can also slow things down. Make sure your strongnamed project does not have any policy file (*.tdl) included.

Sometimes IIS can get "hosed." Uninstall and reinstall IIS, and then run aspnet_regiis -i.

If that doesn't work try repairing the .NET Framework in:

1. Click Start, point to Settings, click Control Panel, and then double-click Add/Remove Programs.
2. Click "Click here for support information".
3. Open the Repair.htm file, which is installed to the version directory for the .NET Framework.
4. Follow the instructions in Repair.htm.