Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

How to disable the new debug window in VS2017

People also ask

How do you disable the Debug option Enable just my code?

To enable or disable Just My Code in Visual Studio, under Tools > Options (or Debug > Options) > Debugging > General, select or deselect Enable Just My Code.

How do I get rid of Debug pop up?

Control Panel>Internet Options>Advanced. Put a checkmark in "Disable Script Debugging (Internet Explorer)" and "Disable Script Debugging (Others)". Apply/OK out.

How do I stop debugging in Visual Studio 2017?

To end a debugging session in Microsoft Visual Studio, from the Debug menu, choose Stop Debugging.


I'm not sure if this came with the latest VS 2017 Update, but inside Debug -> Options you can disable it now.

Just uncheck the highlighted one: enter image description here


For thoose, who have the 15.7 update and unchecking the JavaScript options doesn't do the trick, found a solution here:

https://blogs.msdn.microsoft.com/webdev/2016/11/21/client-side-debugging-of-asp-net-projects-in-google-chrome/

Tools > Options > Projects and Solutions > Web Projects, uncheck “Stop debugger when browser window is closed”


This is not an issue, rather a new feature in VS 2017. Previously we could only debug JS and TypeScript using IE in debug mode (of VS). But now they have introduced debugging JS and TS inside VS using Remote Debugging feature of Chrome. If you are running your application in debug mode (pressing F5) and Chrome is selected browser, Visual studio 2017 will try to open a remote debugging session with Chrome on a dedicated port. With remote debugging,

  1. The browser is launched in plain mode, i.e. no extension and no history etc. Remote debuggin doesnt work with an existing instance of Chrome already running.

  2. You always see this window for a while. At this point, VS is trying to attach the remote debugger to VS

enter image description here

  1. To go back to VS 2015 experience of debugging, change the debugging target from Chrome to IIS Express.

This post describes this feature in detail. https://blogs.msdn.microsoft.com/webdev/2016/11/21/client-side-debugging-of-asp-net-projects-in-google-chrome/

A kind of quick work around is to press F5 and launch the debug session and forget about the newly opened Chrome window. Go to your normal Chrome instance and just open your site in new tab. You will still be able to debug and do everything because IIS Express will still be running your app at that port.

Update: The answer given below by @Steveadoo is the right way going forward. The option shown in his screenshot controls how chrome is launched for debugging. Uncheck it if you want to stick to your regular Chrome instance.

Hope this helps.


Here is the Microsoft blog about this new functionality, and how to revert.

https://blogs.msdn.microsoft.com/webdev/2016/11/21/client-side-debugging-of-asp-net-projects-in-google-chrome/

Here is the path I followed to disable:

Debug > Options > Debugging > General > (uncheck) Enable JavaScript debugging for ASP.Net (Chrome and IE).