ASNA Knowledge Base
Technical references, how-tos, and trouble-shooting for ASNA products
Visual Studio’s default ending of a debug session is to leave all associated processes running. But, in most cases, it’s better to also end those associated processes when you end debugging. This is especially true with ASNA Wings and Mobile RPG, but even a traditional ASP.NET app can get tripped up by a dangling IIS Express process.
The good news is that this is an easy problem to resolve–using the Debug menu’s Terminate All not only ends Visual Studio’s debugging session but it also ends all associated processes. Once I learned about Terminate All, I never looked back. I always use it to end a debugging session.
Quick access to “Terminal All” isn’t directly available from Visual Studio’s debug tool bar at the top of Visual Studio. However but this GIF shows how to to add “Terminate All” to your debugging toolbar.
