How to disable the new debug window in VS2017

I'm using Visual Studio 2017 RC and getting very frustrated with the new Chrome window that pops up when you click Debug.

Issues with the Debug Chrome Window:

• Takes ages to start/"attach" website (I think it's attaching all the javascript debugging which I don't need because I use Chrome DevTools for that anyway)
• Not dockable (as a tab) with other Chrome windows
• Doesn't remember form history. If I'm testing out forms I can't autocomplete form data, so I have to type the whole lot out every time
• Doesn't remember url history. If I'm testing a specific page on my site, I can't quickly select the url from Chrome url bar dropdown. Have to type the url in full
• Extensions aren't enabled so I can't use my ruler or color picker extensions
• Chrome window closes when debugging stops so I have to open up a new window to keep browsing the local site

Does anyone know how to disable this new Debug style window and go back to how it was in VS 2015?

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:

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

3. 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.