You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was debugging a legacy application that throws NullReferenceException in .NET Framework code (which is bug, of course) and found the root source is nested IscException (of FbException) that returns null value from Message property. According documentation https://msdn.microsoft.com/en-us/library/system.exception.message.aspx it is supposed to have an empty string value, not a null value.
The text was updated successfully, but these errors were encountered:
description: I was debugging a legacy application that throws NullReferenceException in .NET Framework code (which is bug, of course) and found the root source is nested IscException (of FbException) that has null value in Message property. According documentation https://msdn.microsoft.com/en-us/library/system.exception.message.aspx it is supposed to have an empty string value, not the null value.
=>
I was debugging a legacy application that throws NullReferenceException in .NET Framework code (which is bug, of course) and found the root source is nested IscException (of FbException) that returns null value from Message property. According documentation https://msdn.microsoft.com/en-us/library/system.exception.message.aspx it is supposed to have an empty string value, not a null value.
summary: IscException.Message should not have null value => Property IscException.Message should never return a null value
Do you have some code where it's visible? From the looks I don't see a path a where it could be left uninitialized. Just to make sure there's nothing else hidden around.
Submitted by: Petr Vones (pvones)
Votes: 1
I was debugging a legacy application that throws NullReferenceException in .NET Framework code (which is bug, of course) and found the root source is nested IscException (of FbException) that returns null value from Message property. According documentation https://msdn.microsoft.com/en-us/library/system.exception.message.aspx it is supposed to have an empty string value, not a null value.
The text was updated successfully, but these errors were encountered: