CODEWITHSUNDEEP
asp.netvisual-studiodebugginginternet-explorerbrowser
sker
sker

Reputation: 18382

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

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?

Upvotes: 502

Views: 207946

Answers (23)

Irf
Irf

Reputation: 4617

Looks like it has changed for VS 2022,

Now it has a dedicated UI,

Right Click the project (in Solution explorer) -->> select Properties (you'd see the below screen) then follow :-

enter image description here


enter image description here

"uncheck" this checkbox for it to not open automatically.

*** OR *** you can click the menu bar, Debug > Properties

enter image description here

and you can reach the Step-2 "launch profiles" directly from here.

or a shortcut:

Select the project ( in Solution explorer) and press Alt + Enter and then follow from there..

Upvotes: 20

Arvind
Arvind

Reputation: 49

Complete solution in simple steps Visual Studio - 2022

  1. Open Visual studio
  2. open Solution Explorer (Ctrl + Alt + L)
  3. Right click on your project
  4. click on "properties"
  5. Properties window
  6. In the left panel , click "debug"
  7. Under "General" , there is "Open debug launch profiles UI"
  8. A new dialog box (launch profiles) will be there
  9. look for launch browser and untick the checkbox Launch profile dialog box
  10. close all dialog box, you are done

Thanks

Upvotes: 0

esenkaya
esenkaya

Reputation: 418

Tools > Projects and Solutions > Web Projects > Stop debugger when.....

Check if you want to open new page and close when stop debugging. Uncheck if you want new tab and keep it even when you stop debugging.

Upvotes: 0

The Memebot
The Memebot

Reputation: 3559

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

enter image description here

Upvotes: 290

somedotnetguy
somedotnetguy

Reputation: 938

For VS2022 and ASP.NET Core:

Another shortcut is: to click the small dropdown button on the right side green-triangle button with the project's name on it, which usually launches the debug build. and then the last option "{project name} Debug Properties" which launches the dedicated UI window directly.

enter image description here

From there follow @irf's advice:

"uncheck" the option for it to not open automatically.

enter image description here

Upvotes: 1

Arad
Arad

Reputation: 12852

Here's what did it for me:

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

enter image description here

Upvotes: 9

Anjan Kant
Anjan Kant

Reputation: 4316

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.

Upvotes: 45

rboy
rboy

Reputation: 2165

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

Upvotes: 1

Lukas Klein Haneveld
Lukas Klein Haneveld

Reputation: 31

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 :)

Upvotes: 1

Buddhika Chathuranga
Buddhika Chathuranga

Reputation: 1468

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.

Upvotes: 22

Greg R Taylor
Greg R Taylor

Reputation: 3676

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

Upvotes: 146

DKR
DKR

Reputation: 5744

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

Upvotes: 30

Pawel Krakowiak
Pawel Krakowiak

Reputation: 10100

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.

Upvotes: 501

Siavash
Siavash

Reputation: 3009

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

Upvotes: 3

Alexa Adrian
Alexa Adrian

Reputation: 1858

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

Upvotes: 24

chri3g91
chri3g91

Reputation: 1410

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"
      }
    }
}

Upvotes: 8

Siddhant Rimal
Siddhant Rimal

Reputation: 968

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

Upvotes: 5

Aaron Powell
Aaron Powell

Reputation: 25107

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.

Upvotes: 12

Alberto
Alberto

Reputation: 853

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

Upvotes: 1

Joao Costa
Joao Costa

Reputation: 1013

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"
      }
    }
}

Upvotes: 83

Rex Miller
Rex Miller

Reputation: 2746

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.

Upvotes: 9

Cody Gaut
Cody Gaut

Reputation: 31

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.

Upvotes: 3

stepank
stepank

Reputation: 456

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.

Upvotes: 8

Related Questions