Windonws 7 64-bit and VS2010
In F12 developer tools for IE11 on Windonws 7 64-bit and VS2010, when I click the Debugger tool icon or press Ctrl + 3 to open the tool, I'm not able to debug my java-script files.
When I click the Debugger tool icon, i'm presented with the message in the screenshot above & I can't see the javacsript files my current page calls, so I'm unable to debug my javascript code.
Any one knows why I could be getting this message? I have tried everything mentioned at the following link with out success. VS2010 and IE10 Attaching the Script debugger to process iexplore.exe failed
A debugger is already attached" when using the F12 Developer Tool in I.E. 11 or whatever version. However, if you use the V.S. command: View in Browser (Ctrl+Shift+W) this will run the script and allow I.E's script debugger (F12 Dev Tool) to engage and work.
"The script debugger failed to connect to the target process. A debugger is already attached". when using the F12 Developer Tool in I.E. 11 or whatever version. However, if you use the V.S. command: View in Browser(Ctrl+Shift+W) this will run the script and allow I.E's script debugger(F12 Dev Tool) to engage and work.
After the process is running, select Debug > Attach to Process or press Ctrl + Alt + p in Visual Studio, and use the Attach to Process dialog to attach the debugger to the process.
You can use Attach to Process to debug running apps on local or remote computers, debug multiple processes simultaneously, debug apps that weren't created in Visual Studio, or debug any app you didn't start from Visual Studio with the debugger attached.
I was encountering this problem with VS 2012 & Win 7 and also VS2013 and Win8.1:
Perplexed for half a day, looking up things online, finally figured it out myself.
Learn the difference between these in Visual Studio: F5 vs (Ctr+Shift+W)
F5 will engage VS debugger and you will get the:
"The script debugger failed to connect to the target process. A debugger is already attached"
when using the F12 Developer Tool in I.E. 11 or whatever version.
However, if you use the V.S. command: View in Browser(Ctrl+Shift+W) this will run the script and allow I.E's script debugger(F12 Dev Tool) to engage and work.
The easier way for me was:
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With