

This article is a guide on how to turn on and use this feature.Įxceptions carry a stack trace with them, so they can provide a wealth of information about where the Exception arose from and why. However, by default, Visual Studio projects don't have this feature turned on. When debugging with the break on all exceptions feature is turned on, it is possible to get information about what went wrong immediately. Exceptions are an excellent way to tell the debugger or logging tools that something went wrong.

However, developers should design apps and APIs so that under regular use, exceptions do not occur. An app should throw exceptions when something exceptional happens.
