Home/ Questions/Q 6056283
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-23T08:21:33+00:00

I am debuggin a subtle bug that is thrown from a .net custom component

  • 0

I am debuggin a subtle bug that is thrown from a .net custom component (no source and obfuscated). The component throws a NullReferenceException in its OnPaint() method which makes calls to subscribers, including my code. I am 100% sure that the problem is in my code. The problem is that visual studio debugger does not stop at the point where the exception is thrown, as it should (I enabled NullReferenceException in the Debug/Exceptions dialog).

This is the first time I encountered such a problem in visual studio. Any ideas on identifying offending code, please?

Kemal

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Likely the problem is your code isn’t throwing the NullReferenceException, however it is probably returning null at some point. You could try adding guard conditions at the end of your functions that ensure you are not returning null, such as an Debug.Assert(retVal != null, "Returned null in function").

    If you are sure you own code is throwing a NullReferenceException, make sure you turn on thrown exceptions, rather than user-unhandled ones.

    • 0