Before asking the actual question let me explain why I decided to post in SO instead of SuperUser or any other Chrome-related community for that matter. Even though the answer may have to do with Chrome itself the question is heavily related to Visual Studio 2022 and I highly doubt that any user in those other communities would be able to provide a sufficient answer.
To debug an ASP.NET Core Web App (MVC) I select the "IIS Express" profile in Visual Studio 2022 and the Google Chrome browser to launch when debugging starts.
I like the "Stop debugger when browser window is closed, close browser when debugging stops" option, which I believe is checked by default in Visual Studio 2022.
I have never had any problems with the Chrome window that the debugger opens, attaches to and then closes when I click "Stop Debugging" in Visual Studio. All other opened Chrome windows were never affected in any way and would always remain open when debugging was stopped.
But the last couple of days whenever I click "Stop Debugging" in Visual Studio all opened Chrome windows get closed! This is super annoying. I am pretty sure that only the debugger's Chrome window used to close when debugging stopped.
I did some trial-and-error by deleting Chrome profiles and even uninstalling and re-installing Chrome but to no avail. When I select Microsoft Edge in Visual Studio everything works as expected. That makes me think Chrome is to able and not Visual Studio but I cannot really pinpoint what might have changed and would very much appreciate any ideas, workarounds or hints.
UPDATE: Let's take one step further and make the question a little bit more technical. Is there any way I can configure the way Visual Studio 2022 debugger attaches to the Chrome browser so that other, unrelated-to-the-debugging-session browser windows do not close when the debugging session ends?
