JScript Debugger– “Unable to attach the process. Another debugger might be attached to the process” – while application is running from Visual Studio. [ Solution ] January 20, 2012Posted by Abhijit Jana in .NET 4.0, ASP.NET 4.0, ASP.NET 4.5, Tips and Tricks, Visual Studio, Visual Studio 2010, Visual Studio 2011.
Tags: ASP.Net, codeproject, Debugging, Visual Studio
IE Developer Toolbar – JS Debugger Error “Unable to attach the process. Another debugger might be attached to the process” .
1. Run an ASP.NET application from Visual Studio.
2. Once application launched, Press F12 in browser to launch Developer Toolbar.
3. Move to “Script” Tab and Click on “Start Debugging” . Put necessary breakpoints on the script function as required before click.
On click of “Start Debugging”, you will receive below error message. which says, already another debugger attached and you can not attach with current IE Process for debugging.
Follow the below steps for resolve this issue.
1. Go back to Visual Studio and Select “Detach All” from “Debug” menu.
2. Now click on “Start Debugging” from IE Developer Toolbar. No error , and you can continue with debugging and other work.
Behind the scene :
Visual Studio automatically instantiate an Internet explorer process to launch the web sites. You can check the process level using “Process Explorer”.
Which mean, while your site is running in browser, “iexplore.exe” ( Process for Internet Explorer) is already attached . One of the most simplest way to check this out is, navigate to Debug > Windows> Processes . This will list out all attached process with in visual studio . For any typical ASP.NET web application which is running from visual studio will have two process and iexplore is one of them.
That’s why when you are trying to attach the same process from IE Developer tool bar, it is throwing error “Unable to attach the process. Another debugger might be attached to the process” .
So now we know what was the causing the issue and let’s have a look what we did to resolve this.
As a resolution, we used “Detach All” from debug menu, which actually detach all the process which is attached with visual studio except local ASP.NET Development server process ( WebDev.WebServer40.EXE ).
Note : “Detach All” will detach all the attached process apart from ASP.NET Development server. Because detaching the development server is nothing but stopping your application. If you want to stop, either stop debugging or “Terminate” the local development sever process.
“Detach All” will remove iexplore.exe from the list of attached process. So, you can go ahead and start the debugging in IE Developer toolbar.
Detaching a Particular Process Instead “Detach All”
If there are multiple processes attached and if you want to detach only “IE Process”, you can simply do it from process attach window, by selecting “Detach Process” from the content menu of the “iexplore.exe”. This will help you to retain on other process in attached state.
To know more about Processes Window, check out this post How to get list of attached processes in Visual Studio while debugging ?
Hope this helps !