Menu
Go to Project Properties > Debug > Uncheck "Launch Browser" > Save.
To find this setting, open the Visual Studio Options dialog from Tools menu and select Options. From there, locate Web Projects from the Projects and Solutions navigation tree. Now untick the option box that says "Stop debugger when browser window is closed, close browser window when debugger stops."
Tools -> Options -> Search for "browser" -> View Source in "external editor" -> put the path to your preferred.
Start Visual Studio, on the File menu select New, and then select Project. In the New Project dialog box, select Visual Basic or Visual C# as the programming language. In the Templates pane, select ASP.NET Empty Web Application, and name the project SofiaCarRentalWebApp. Click OK to create the solution and the project.
I've discovered that Turning off Javascript debugging means that sites open in a new tab of an existing Chrome instance. From what I've seen the in Visual Studio debugging is not as good as Chrome's dev tools so turning this off is not an issue for me.
UPDATE
As of VS2017 15.7.1 (and still the case in VS2019 16.0.0 and VS2022 17.0.0 PREVIEW) this fix no longer works and I've found I've had to additionally uncheck Stop debugger when browser window is closed
There is solution to that problem. Very Simple please follows the below Steps.
Now start project, it will not open in new chrome Instant but in a already running Chrome Instant.
You can disable the website from being launched at all from the debug settings.
Once the web application is running you can launch the website from the taskbar.
The "Browse With..." menu option appears to launch the website without running the debug session in VS2017 which might not be what you want.
I wanted to share the reason of the issue as well as the screen shot. The reason for which it opens a new window is because JS debugging is enabled. Chrome is launched with debugging enabled so a new instance is required. If you want to revert to the old behavior from Visual Studio 2015, you can do so but you would have to disable JS debugging. See below:
Original Source
Original Discussion on Visual Studio Forum
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