When I start debugging my web application either from Start with Debugging (F5) or attaching to the ASP.NET worker process it will load the assemblies from the application very slowly that I can individually read the names of them as they scroll through the status bar of VS2010.
When I start debugging I see that MSVSMON.exe uses 50% CPU and locks at 50% clearly filling up a full core. Also seeing that this is described as Visual Studio Remote Debugging Monitor, I’m confused if this should even be used since I’m debugging everything local to my machine.
I am running my environment virtually connected by RDP if that could be related to this.
Host Machine: Server 2008 Enterprise R2 Dualcore Xeon 2.53ghz
Virtual Instance: Win7 Enterprise 6gb ram full processor allocation
Does this seem normal? Should MSVSMON even be running if I’m debugging locally?
Menu.Debug.DeleteAllBreakpointsWorked for me.