Exception.Message vs Exception.ToString()

by

Exception.Message contains only the message (doh) associated with the exception. Example:

Object reference not set to an instance of an object

The Exception.ToString() method will give a much more verbose output, containing the exception type, the message (from before), a stack trace, and all of these things again for nested/inner exceptions. More precisely, the method returns the following:

ToString returns a representation of the current exception that is intended to be understood by humans. Where the exception contains culture-sensitive data, the string representation returned by ToString is required to take into account the current system culture. Although there are no exact requirements for the format of the returned string, it should attempt to reflect the value of the object as perceived by the user.

The default implementation of ToString obtains the name of the class that threw the current exception, the message, the result of calling ToString on the inner exception, and the result of calling Environment.StackTrace. If any of these members is a null reference (Nothing in Visual Basic), its value is not included in the returned string.

If there is no error message or if it is an empty string (“”), then no error message is returned. The name of the inner exception and the stack trace are returned only if they are not a null reference (Nothing in Visual Basic).

More Related Contents:

  1. Catch multiple exceptions at once?
  2. Is there a difference between “throw” and “throw ex”?
  3. How to handle AccessViolationException
  4. WPF global exception handler [duplicate]
  5. How slow are .NET exceptions?
  6. Exception messages in English?
  7. Cannot delete directory with Directory.Delete(path, true)
  8. TAP global exception handler
  9. Puzzling Enumerable.Cast InvalidCastException
  10. Can you catch a native exception in C# code?
  11. Avoiding first chance exception messages when the exception is safely handled
  12. .NET – What’s the best way to implement a “catch all exceptions handler”
  13. Troubleshooting BadImageFormatException
  14. Avoiding null reference exceptions
  15. User Activity Logging, Telemetry (and Variables in Global Exception Handlers)
  16. Active Directory COM Exception – An operations error occurred (0x80072020)
  17. Why does a bad password cause “Padding is invalid and cannot be removed”?
  18. Is this a bad practice to catch a non-specific exception such as System.Exception? Why?
  19. Image.FromStream() method returns Invalid Argument exception
  20. Best practices: throwing exceptions from properties
  21. What is ApplicationException for in .NET?
  22. Show line number in exception handling
  23. How to check for valid xml in string input before calling .LoadXml()
  24. Is there a built in .NET exception that indicates an illegal object state?
  25. Why Create Custom Exceptions? [closed]
  26. How do I determine the HResult for a System.IO.IOException?
  27. Catch Application Exceptions in a Windows Forms Application
  28. Could not load file or assembly ‘System.Windows.Interactivity’ [duplicate]
  29. Which types of exception not to catch?
  30. Dynamically changing Textbox’s AutoComplete List causes AccessViolationException, any advice?

Leave a Comment