Windows Phone development (18): Ui Exception Handling of WP

 

Ui exception handling:
In app. XAML. CS, there are two methods:
// Executed when navigation failsCode
Private void rootframe_navigationfailed (Object sender, navigationfailedeventargs E)
{
If (system. Diagnostics. Debugger. isattached)
{
// Navigation failed; force access to the debugger
System. Diagnostics. Debugger. Break ();
}
}

// Code executed when an unhandled exception occurs
Private void application_unhandledexception (Object sender, applicationunhandledexceptioneventargs E)
{
If (system. Diagnostics. Debugger. isattached)
{
// An unhandled exception occurs; forcibly enters the debugger
System. Diagnostics. Debugger. Break ();
}
}

The annotations clearly show that these two methods can be used to help handle errors and exceptions.
Rootframe_navigationfailed is used to handle navigation failures. The second method application_unhandledexception is used to process the application.ProgramAll unprocessed exceptions (Exceptions not caught in a specific stage)
In debug mode, system. Diagnostics. Debugger. Break (); causes the breakpoint to stay here. This is a very practical function, where programmers have the opportunity to view the runtime information.