I sketched this test example:

static void Main(string[] args) { try { test(0,0); } catch (Exception e) { Console.WriteLine(e); throw new Exception("ttt", e); } } static void test(int a,int b) { var t=a / b; }

For some reason, only the message ttt is shown.

In the previous VS, it was possible to call a modal window and examine the exception.

I know that in VS 2017 the modal window was replaced, however, an internal exception should be displayed there.

enter image description here

The idea should be something like this:

enter image description here

As you can see there is a Details button and with arrows you can switch between exceptions.

  • five
    you are not new at all - is it really so difficult to format the code (ctrl + k aligns and to the left too!), and not to leave a curved ladder in each question? - PashaPash ♦
  • 3
    @ Andrew, even if so, what's wrong with that? Someone can help afterwards - Anatol
  • Always looked through the detais ... - Qwertiy ♦
  • one
    @Qwertiy, yes, but in my case it wasn’t even = ( - iluxa1810

1 answer 1

Hmm ... Found a solution:

If you set Enable native code debugging in project properties, then everything works.

However, it is interesting how to make this default behavior for all new projects.

It seems to understand how to fix it without ticking the Enable native code debugging .

Problems with exceptions arise if there is a tick in use managed compatibility mode in the settings. If you remove it, then everything works as it should.

PS If someone has an older version, then you can check how these jackdaws affect debugging in old VS and unsubscribe in the comments. If this is true for older versions, then it makes sense to make the question common to all VS.