I’ve pinged the owners offline about this. The best way to track this, report this issue to us and have others up-vote it – would be to Help -> Send Feedback -> Report a Problem.
From: [email protected] <[email protected]> On Behalf Of Greg Keogh Sent: Tuesday, May 8, 2018 11:19 AM To: ozDotNet <[email protected]> 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
