0

When I launch my ASP.NET Core Web Api project in VS Pro the resulting Swagger page is opened in a new browser places on top of an existing Chrome Browser window. This is driving me crazy! Opening the same project in VS Community Edition opens the Windows where I last closed it. It remembers the setting and it creates a new taskbar icon for the window.

How can I make VS Pro behave the same as Community Edition?

Holm76
  • 216
  • 2
  • 11
  • Do these help? https://stackoverflow.com/questions/42673989/open-site-in-new-tab-of-existing-chrome-instance-when-debugging https://stackoverflow.com/questions/42095299/visual-studio-do-not-open-new-browser-instance – Timothy G. Nov 10 '22 at 14:00
  • No. Looked at those as I rote this thread. Its weird that Community and Pro have different settings! – Holm76 Nov 10 '22 at 15:18
  • @TimothyG. I stand corrected. This is indeed the option I was looking for it seems. Flopping the option in the screenshot below also changes the value of Tools/Options/Debugging 'Enable JavaScript debugging for ASP.NET'. – Holm76 Dec 07 '22 at 11:03
  • The question was not focused. One of the other commenters found it confusing. Also I found a solution. Or rather it turns out that the controller was already being loaded automatically. I just hadn't noticed! Then I found some code by which I could prevent controllers from being loaded. I appreciate your help. Sorry I deleted it but it suddenly looked like a stupid thread now that I figured out the LogController service was already loaded... DUH! – Holm76 Dec 16 '22 at 14:07

1 Answers1

0

Script Debugging setting is the culprit. If disabled Chrome will launch on top of existing Chrome windows. If enabled it will start a new Chrome windows where it was last closed.

enter image description here

Holm76
  • 216
  • 2
  • 11