Greg, the dev stated below: From: Bill Hiebert Sent: Wednesday, May 9, 2018 2:04 AM To: David Kean <david.k...@microsoft.com> Subject: RE: Web debugging problem
Yes. Script debugging was disabled by default which means the debugger is not tracking the Browser anymore. To work around this, we added a feature which tracks the launched browser and will stop debugging when the browser is closed. This feature has option to turn it off and most likely this customer has it turned off – I think you could get into this state if you installed one of the early 15.7 previews and then upgraded. Normally, the feature is on be default. He can do a couple of things 1. Enable Script debugging from the Tools\Options\Debugger\General page (or we added a quick way to do this from the debug dropdown) [cid:image002.png@01D3E76D.0D102610] [cid:image004.png@01D3E76D.0D102610] 1. If he never uses script debugging, make sure the new option to stop debugging when the browser is closed is set: [cid:image005.png@01D3E76D.0D102610] From: David Kean Sent: Monday, May 7, 2018 6:51 PM To: Bill Hiebert <bill.hieb...@microsoft.com<mailto:bill.hieb...@microsoft.com>> Subject: FW: Web debugging problem Bill, was there a change around this? From: ozdotnet-boun...@ozdotnet.com<mailto:ozdotnet-boun...@ozdotnet.com> <ozdotnet-boun...@ozdotnet.com<mailto:ozdotnet-boun...@ozdotnet.com>> On Behalf Of Greg Keogh Sent: Tuesday, May 8, 2018 11:19 AM To: ozDotNet <ozdotnet@ozdotnet.com<mailto:ozdotnet@ozdotnet.com>> Subject: Web debugging problem Folks, I just accepted a VS2017 update to 15.7.0 and it downloaded 745 updates in 3.38GB. It might have caused a change in ASP.NET<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2FASP.NET&data=02%7C01%7Cdavid.kean%40microsoft.com%7C48bb24470ea046835ca108d5b481be84%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636613391732922732&sdata=JXRW0MgVjLRxMkrq12pdmTyYMJYbKOgq9tVOub8o81Y%3D&reserved=0> debugging behaviour. I hit F5 to debug-run a classic ASP.NET<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2FASP.NET&data=02%7C01%7Cdavid.kean%40microsoft.com%7C48bb24470ea046835ca108d5b481be84%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636613391732922732&sdata=JXRW0MgVjLRxMkrq12pdmTyYMJYbKOgq9tVOub8o81Y%3D&reserved=0> project, it launches IE11 and it works normally. When I close IE11, VS2017 continues debugging and I have to Shift+F5 to stop it. Before this morning, I'm sure that closing IE11 used to stop debugging as well. This is really irritating and web searches only hint that turning off "Edit and Continue" will fix it, but it has no effect in either Local IIS or IIS Express. I can't find any other clues on this matter. Anyone else got any ideas? Thanks Greg K
