Edit Question - KnowledgeHub

Title Body

Configuration: Windows 7, 64 bit Microsoft Visual Studio Professional 2012 RC Version 11.0.50522.1 RCREL Running VS in administrator mode The VS solution contains a web application, with target: .NET Framework 4. When I press F5, the solution builds... and nothing else happens. Happens with both IIS or the VS Dev Server. Happens with Platform Target of "Any CPU" or "x86" If instead, I use the Debug / Attach to Process... menu, after a few seconds, I get: "Debugger is Busy" - Debugger is performing a remote operation that is taking longer than expected. This dialog stay until I click "Terminate" and confirm it. Then this dialog appears: "Microsoft Visual Studio" "Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor named [COMPUTER NAME]. The network connection to the Visual Studio Remote Debugger has been closed." After clicking OK, the 'normal' "Attach to Process" window finally shows up. In it, the list of "Available Processes" is empty. Any suggestions or clues? The main points that I wonder about: Why is the list of processes empty? It is not surprising that the debugger does not work if it cannot see any processes. Why is it trying to do "remote" debugging, when it is just accessing the local computer? (Cross posted on social.msdn )

Tags (comma-separated) Cancel