Home/ Questions/Q 4274338
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-21T07:50:00+00:00

I created a library with many utility functions to perform some tasks and placed

  • 0

I created a library with many utility functions to perform some tasks and placed it in it’s own DLL.

Throughout the methods in this library, i’ve placed Debug.Assert statements to verify the state of the application.

The problem is, when the Assert is firing (the condition is false), it presents the dialog, clicking “Abort” on it causes the entire application that uses this DLL to crash.

This poses 2 questions:

  1. Can this be avoided? i’d expect this to throw an exception without exiting the application.

  2. How come a DLL can cause the application that loads it to exit? isn’t this a security breach?

Thanks

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    If you want to have an exception thrown, why dont you just throw an exception?

    Change

    Assert(var);

    to

    if(!var)
  throw new Exception("var was false");

    Assert will leave the application, assertion are here to protect you from coder’s mistake. If a function should never receive a null pointer, and if it does then it would be a mistake, then an assert would be the right tool.

    If you want to express an exceptionnal situation, than the exception is the tool you are looking for

    • 0