Stop Visual Studio from launching a new browser window when starting debug?

asp.netVisual StudioDebuggingInternet ExplorerBrowser

asp.net Problem Overview

I already have a window open with the web site I'm debugging. I don't need VS to launch another one for me every time I need to debug.

Is there a way to stop this behavior?

asp.net Solutions

Solution 1 - asp.net

Open your startup project's properties (Project → {ProjectName} Properties... from the main menu or right click your project in the Solution Explorer and choose Properties), then navigate to the Web tab and under Start Action choose Don't open a page. Wait for a request from an external application.

You will still be able to use any browser (or Fiddler, whatever) to access the running application, but it won't open the browser window automatically, it'll just start in the background and wait for any requests.

Solution 2 - asp.net

For VS 15.7.1 Tools → Options → Projects and Solutions → Web Projects → uncheck Stop debugger when browser window is closed.

Solution 3 - asp.net

Updated answer for a .NET Core Web Api project...

Right-click on your project, select "Properties," go to "Debug" and untick the "Launch browser" checkbox (enabled by default).

enter image description here

Solution 4 - asp.net

In an ASP.Net 5 project this can now be set for each launch profile.

Open the file launchsettings.json under the Startup Project Properties folder and add "launchBrowser": false to the profile you are configuring, such as in:

"profiles": {
    "IIS Express": {
      "commandName": "IISExpress",
      "launchBrowser": false,
      "environmentVariables": {
        "Hosting:Environment": "Development"
      }
    }
}

Solution 5 - asp.net

I have solved my problem by following below steps. Go to Tools >> Click on options >> click on projects and solutions >> web projects >> uncheck "Stop debugging when browser is closed" optionenter image description here

Solution 6 - asp.net

In Visual Studio 2019, I resolved the same issue as below:

Go to your Visual Studio options Tools >>> Options >>> Project and Solutions >>> Web Projects then finally untick option >>> Stop debugger browser window is closed, close browser when debugging stops

Step 1:

enter image description here

Step 2: untick option >>> Stop debugger browser window is closed, close browser when debugging stops

enter image description here

Step 3:

Then finally click on >>> OK button, these are all the steps to resolve the issue.

Solution 7 - asp.net

This workaround works for me for VS 2019

> Tools => Options

Then type Projects and solutions in the search box.

Select the Web Projects.

Then deselect the option below.

> Stop debugger when browser window is closed, close browser when debugging stops.

This works for me. Hope this will help.

Solution 8 - asp.net

As I did not had the mentioned option in my VS which is Visual Studio Enterprise 2017, I had to look for some other option.

Here is it what I've found:

Go to Tools -> Options -> Debugging tab(General) and uncheck "Enable JavaScript debugging for Asp.Net(Chrome and IE).

enter image description here

Solution 9 - asp.net

You can use the Attach To Process function, rather than pressing F5.

This can also allow you to navigate through known working sections without the slowdown of VS debugger loaded underneath.

Solution 10 - asp.net

When you first open a web/app project, do a Ctrl-F5, which is the shortcut for starting the application without debugging. Then when you subsequently hit F5 and launch the debugger, it will use that instance of IE. Then stop and start the debugging in Visual Studio instead of closing IE.

It works on my machines. I'm using the built in dev web server. Don't know if that makes a difference.

Firefox will also stay open so you can debug in either or both at the same time.

Solution 11 - asp.net

There seems to be one case in which none of the above but the following helps. I'm developing a project for Windows Azure cloud platform and I have a web role. There is indeed a radio button Don't open page in Project -> {Project name} properties... as was pointed out by Pawel Krakowiak, but it has no effect in my case whatsoever. However, there is the main cloud project in solution explorer and there is the Roles folder under it. If I right click my web role in this folder and choose Properties, I get another set of settings and on the Configuration tab there is the Launch browser for flag, after unchecking it a new browser window is not opened on application start up.

Solution 12 - asp.net

Here's what did it for me:

Go to Project Properties > Debug > Uncheck "Launch Browser" > Save.

enter image description here

Solution 13 - asp.net

Joao Costa answer also holds true for .Net core 2 projects.

launchsettings.json --> "launchBrowser": false

"profiles": {
    "IIS Express": {
      "commandName": "IISExpress",
      "launchBrowser": false,
      "environmentVariables": {
        "Hosting:Environment": "Development"
      }
    }
}

Solution 14 - asp.net

I looked over the answers and didn't see the solution I found mentioned. If it was, my apologies. In my case, currently using Visual Studio 2015. In the solution explorer, right click on the Project file and click properties. Go to the Debug tab and this should have info for how you're launching "IIS Express or Web(DNX)" for the first two drop downs, and then there should be a checkmark box for "Launch URL:". Uncheck this option and your browser won't be automatically launched everytime you go to debug your application. Hope this helps someone out.

Solution 15 - asp.net

While there are several excellent answers, ranging from usual suspects to newer solutions, I would like to provide one more to the fray that addresses what you should do when you are working on a solution with multiple projects.

Before I arrived at this solution, I kept looking at bindingInformation in the applicationhost.config of the solution, tirelessly looking for any hint of why things were simply not working.

> Turns out, the simple thing that I overlooked was that different projects have individual settings too. > > So, besides Project > {Project-Name} Properties... > Web > Start Action on my Backend Project, I also had to Go to Website > Start Options... > Start Action on my Frontend Project. Once there, I selected Don't open a page. Wait for a request from an external application and have been happy ever since!

Backend Settings Frontend Settings

Solution 16 - asp.net

You can right click on your project, then choose Properties , on Debug tab you should uncheck launch browser checkbox.

Solution 17 - asp.net

CTRL+ALT+ENTER if your amends are front end only

http://blogs.msdn.com/b/webdev/archive/2013/06/28/browser-link-feature-in-visual-studio-preview-2013.aspx

Solution 18 - asp.net

If you're using the Web Publish feature in IIS, then the solution I found was to edit the publish configuration and remove the Destination URL from the configuration (leave it blank).

If this is defined, then every time you publish the project it will open the URL specified in the Destination URL (which is a redirect URL).

Reference: https://support.winhost.com/kb/a1604/visual-studio-publish-web-deploy.aspx

Solution 19 - asp.net

You can now also get to the Web properties by clicking the dropdown arrow next to the Run button!

  1. Click dropdown button next to "Run"
  2. { Project name } Properties
  3. Click "Web" in the list on the left
  4. Under the "Start Action" segment, click Don't open a page.

You're all set!

PS: This works for me, I'm on version 16.5.5 of VS Professional 2019 :)

Categories
Recommended asp.net Solutions
Recommended Visual Studio Solutions
Recommended Debugging Solutions
Recommended Internet Explorer Solutions
Recommended Browser Solutions

Previous Solution:

How to make an image center (vertically & horizontally) inside a bigger div

HtmlCss

Next Solution:

How can I make grep print the lines below and above each matching line?

LinuxGrep

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionskerView Question on Stackoverflow
Solution 1 - asp.netPawel KrakowiakView Answer on Stackoverflow
Solution 2 - asp.netThe MemebotView Answer on Stackoverflow
Solution 3 - asp.netGreg R TaylorView Answer on Stackoverflow
Solution 4 - asp.netJoao CostaView Answer on Stackoverflow
Solution 5 - asp.netDKRView Answer on Stackoverflow
Solution 6 - asp.netAnjan KantView Answer on Stackoverflow
Solution 7 - asp.netBuddhika ChathurangaView Answer on Stackoverflow
Solution 8 - asp.netAlexa AdrianView Answer on Stackoverflow
Solution 9 - asp.netAaron PowellView Answer on Stackoverflow
Solution 10 - asp.netRex MillerView Answer on Stackoverflow
Solution 11 - asp.netstepankView Answer on Stackoverflow
Solution 12 - asp.netAradView Answer on Stackoverflow
Solution 13 - asp.netchri3g91View Answer on Stackoverflow
Solution 14 - asp.netCody GautView Answer on Stackoverflow
Solution 15 - asp.netSiddhant RimalView Answer on Stackoverflow
Solution 16 - asp.netSiavashView Answer on Stackoverflow
Solution 17 - asp.netAlbertoView Answer on Stackoverflow
Solution 18 - asp.netrboyView Answer on Stackoverflow
Solution 19 - asp.netLukas Klein HaneveldView Answer on Stackoverflow