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 debugging
behaviour.

I hit F5 to debug-run a classic ASP.NET 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*

Reply via email to