I suggest you ...

When debugging a UWP app and an uncaught exception is thrown, the debugger should break at the location from which the exception is thrown

If you create a new WinForms project and add a single line in the constructor of Form1.cs:
throw new Exception();

Then hit F5. The exception is uncaught and the debugger breaks at that line.

If you create a UWP project and add a single line to the constructor in MainPage.xaml.cs:
throw new Exception();

It breaks in the UnhandledException default handler in App.g.cs.

Can you bring back the developer-friendly feature of breaking right where the exception is thrown? When developing for UWP, it makes it much more difficult and time consuming to find even the simplest bugs (ex. null ref exception) because it's not immediately obvious where the exception occurred.

10 votes
Vote
Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
You have left! (?) (thinking…)
Adam Mitchell shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

0 comments

Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
Submitting...

Feedback and Knowledge Base