Question

…will it effectively become an empty try-catch in the release build?

Or will it never make to the build?

try
{
   // do stuff...
   // do stuff...
}
catch
{
    Debugger.Break();
}

I know that Debugger calls won’t be included – obviously, but does that apply to the catch I wrapped it in, too?

And is it a bad thing? It’s just for debugging purposes – I want to see the exception right where it occurred, not where it leaves me after it bubbles up the stack. It’s just more convenient.

Answer 1

This will result in an empty catch-block. To avoid this you can use conditial compilation sequences:

private void DoSomething()
{
#if DEBUG
    try
    {
#endif
        //do something
#if DEBUG
    }
    catch
    {
        Debugger.Break();
        throw;
    }
#endif
}