Let Other Processes Run When Debugging One Process -- Visual Studio Magazine

Let Other Processes Run When Debugging One Process

When you hit a breakpoint in Visual Studio, everything stops. If you'd rather other processes keep running, you can enable that.

By Peter Vogel
12/20/2016

If you've set multiple start projects to run when you start debugging, you may have noticed that when you hit a breakpoint in any project, all the other projects stop also. If you'd prefer that they kept running (so that, for example, you can access them through the Immediate window), you can have that.

Just go to Tools | Options | Debugging | General and uncheck "Break all processes when one process breaks" (don't take that word "break" too seriously -- it means "break" as in "breakpoint").

About the Author

Peter Vogel is a system architect and principal in PH&V Information Services. PH&V provides full-stack consulting from UX design through object modeling to database design. Peter tweets about his VSM columns with the hashtag #vogelarticles. His blog posts on user experience design can be found at http://blog.learningtree.com/tag/ui/.

Printable Format

comments powered by Disqus

Featured

Oh Data! Microsoft Ships First Major OData Update in Nearly 8 Years

Microsoft today shipped a preview of OData .NET 8. OData v7.0 was released in August of 2016.
Full Stack Hands-On Development with .NET

In the fast-paced realm of modern software development, proficiency across a full stack of technologies is not just beneficial, it's essential. Microsoft has an entire stack of open source development components in its .NET platform (formerly known as .NET Core) that can be used to build an end-to-end set of applications.
.NET-Centric Uno Platform Debuts 'Single Project' for 9 Targets

"We've reduced the complexity of project files and eliminated the need for explicit NuGet package references, separate project libraries, or 'shared' projects."
Creating Reactive Applications in .NET

In modern applications, data is being retrieved in asynchronous, real-time streams, as traditional pull requests where the clients asks for data from the server are becoming a thing of the past.
AI for GitHub Collaboration? Maybe Not So Much

No doubt GitHub Copilot has been a boon for developers, but AI might not be the best tool for collaboration, according to developers weighing in on a recent social media post from the GitHub team.