DID YOU KNOW?
Do you know how to understand exceptions in DOTNET when they occur? Below is the exception of a program that has crashed:

Unhandled Exception: System.DivideByZeroException: Attempted to divide by zero.
at System.Decimal.FCallDivide(Decimal& result, Decimal d1, Decimal d2)
at System.Decimal.Divide(Decimal d1, Decimal d2)
at Calc.Features.Divide(Decimal First_Num, Decimal Second_Num)
at Calc.CalcMain.Main(String[] args)

When I got this message on my screen, I didn’t understand anything thing at first. But if we look closely, we can retrieve bits of information from it.

On the first Line, we see this:
“Unhandled Exception: System.DivideByZeroException: Attempted to divide by zero”

From this particular line, we can understand 3 things. The first one is the “Unhandled Exception”. This immediately tells us that this is an exception and it could be handled (stopped) but it wasn’t done by the programmer.

The second thing is the Exception in question, that is: “DivideByZeroException”. Thus, if you do a search in the .NET SDK about this exception, you can get details of how this particular exception is triggered and how it must be properly handled.

Then at the end we have: “Attempted to divide by zero”. This is like a clear error message to a simple computer user that tells him how the error occurred and to the programmer, how the exception was triggered.

Next we have a couple of sentences that start with “at”. These are sort of a record of where the bogus code transited. There is a particular way to read this message. Eventually, this must not be read from top to bottom but the reverse:

The “at Calc.CalcMain.Main(String[] args)” tells us the Main Function where all started.

The “at Calc.Features.Divide(Decimal First_Num, Decimal Second_Num)” is the Method that is responsible to divide two numbers. Thus this is where the error occurred.

The others are too obscure for us to take attention. Now we already know what the bug is, how it occurred and how it can be stopped.