Should not swallow unhandled exceptions if debugger is attached.

[MattGal]

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.

[davidfowl]

/cc @BillHiebert inorder to throw exceptions on f5, we need to pass a flag on launching for console apps in VS.

[davidfowl]

Closing this an opening a tooling issue.