You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 18, 2017. It is now read-only.
As an example, in a traditional desktop app, let’s say I have this:
static void Main(string[] args)
{
int zero = 0;
try
{
int foo = 2 / zero;
}
catch { }
int bar = 2 / zero;
}
If I turn on 1st chance exceptions and F5, I break on foo, and can continue. If I don’t, it’s caught and I break on bar and cannot continue. Makes sense.
Now, if you try the same thing on a K project with 1st chance exceptions turned on, you see the same thing. If you turn them off and happen to uncheck "Just my code" in debugger settings, when it gets to the bar line it just exits. The exception appears to be swallowed (so is only ever really 1st chance) and then goes away.
When the debugger is attached, as is in this case, it'd be great to just re-throw those exceptions.
The text was updated successfully, but these errors were encountered:
- Allow overriding the console host env var
- This allows VS to set it so that exceptions that occur before
the application runs, throw proper exceptions instead of disappearing
with a quick console window when f5 is hit in VS.
- Added SetConsoleHost to PAL
- Handle unwrapping exceptions in the EntryPointExecutor
#1202#726
As an example, in a traditional desktop app, let’s say I have this:
If I turn on 1st chance exceptions and F5, I break on foo, and can continue. If I don’t, it’s caught and I break on bar and cannot continue. Makes sense.
Now, if you try the same thing on a K project with 1st chance exceptions turned on, you see the same thing. If you turn them off and happen to uncheck "Just my code" in debugger settings, when it gets to the bar line it just exits. The exception appears to be swallowed (so is only ever really 1st chance) and then goes away.
When the debugger is attached, as is in this case, it'd be great to just re-throw those exceptions.
The text was updated successfully, but these errors were encountered: