Create an account


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Changes to script debugging in Visual Studio 15.7

#1
Changes to script debugging in Visual Studio 15.7

We’re always looking for ways to make developing with Visual Studio faster.  One of the tasks developers do many times a day is launching debugging sessions.  We identified that script debugging added about 1.5s per F5, but only about 15.5% of people actively debugged script using Visual Studio.

Based on the above, in Visual Studio 15.7 we made the decision to turn off script debugging by default to improve the overall experience for most users. If you want to turn the capability back on, you can do it from Tools | Options | Debugging | and check “Enable JavaScript debugging for ASP.NET (Chrome, Edge, and IE):

We also added the following dialog when you attempt to set a breakpoint with script debugging disabled:

When script debugging is ON, Visual Studio automatically stops debugging when the browser window is closed. It will also close the browser window if you stop debugging in Visual Studio. We added the same capability to Visual Studio when script debugging is OFF under Tools | Options | Project and Solutions | Web Projects:

With this option enabled:

  • Visual Studio will open a new browser window when debugging starts
  • Visual Studio will stop debugging when the browser window is closed

The following matrix shows you all the available options and the expected behavior for each combination:

Enable JavaScript debugging for ASP.NET (Chrome, Edge and IE) Stop debugger when browser window is closed What happens when you start debugging What happens when you stop debugging What happens when you close the browser window
TRUE TRUE New browser window always pops up New browser window always goes away, with all open tabs Debugging stops
TRUE FALSE New browser window always pops up New browser window always goes away, with all open tabs Debugging stops
FALSE TRUE New browser window always pops up New browser window always goes away, with all open tabs Debugging stops
FALSE FALSE Opens new tab if browser window already exists Browser tab/window stays open Debugging continues

If you want Visual Studio to return to its default pre-15.7 behavior, all you have to do is enable script debugging in Tools | Options | Debugging | and check “Enable JavaScript debugging for ASP.NET (Chrome, Edge, and IE). If you notice any unexpected behavior with these options please use report a problem in Visual Studio to let us know. If you have any feedback or suggestions regarding this change please let us know on uservoice or simply post a reply to this post.

Reply



Possibly Related Threads…
Thread Author Replies Views Last Post
  New experimental Razor editor for Visual Studio xSicKxBot 0 1,589 09-10-2020, 05:51 AM
Last Post: xSicKxBot
  New experimental Razor editor for Visual Studio xSicKxBot 0 1,642 07-17-2020, 04:41 AM
Last Post: xSicKxBot
  Configuring Azure Services and emulators using Visual Studio xSicKxBot 0 1,580 06-04-2020, 09:16 AM
Last Post: xSicKxBot
  Configuring Azure Services and emulators using Visual Studio xSicKxBot 0 1,662 05-07-2020, 11:41 PM
Last Post: xSicKxBot
  Updated Razor support in Visual Studio Code, now with Blazor support xSicKxBot 0 1,744 07-23-2019, 11:08 AM
Last Post: xSicKxBot
  Updated Razor support in Visual Studio Code, now with Blazor support xSicKxBot 0 1,716 04-29-2019, 09:17 PM
Last Post: xSicKxBot
  Web and Azure Tool Updates in Visual Studio 2019 xSicKxBot 0 1,836 04-05-2019, 08:03 PM
Last Post: xSicKxBot
  Changes to the web and JSON editor APIs in Visual Studio 2019 xSicKxBot 0 1,775 03-07-2019, 04:41 PM
Last Post: xSicKxBot
  Razor support in Visual Studio Code now in Preview xSicKxBot 0 1,946 03-05-2019, 02:41 PM
Last Post: xSicKxBot
  Changes to the web and JSON editor APIs in Visual Studio 2019 xSicKxBot 0 1,855 02-21-2019, 09:02 PM
Last Post: xSicKxBot

Forum Jump:


Users browsing this thread:
2 Guest(s)

Forum software by © MyBB Theme © iAndrew 2016