I suggest you ...

Actually implement Exception.ToString correctly. E.g. AggregateException.ToString() { foreach( exception in InnerException )

Actually implement Exception.ToString correctly.

E.g. AggregateException.ToString() { foreach( exception in InnerException ) print out exception.ToString(); }
Exception.ToString() { print out error message and stack trace; }
WebException.ToString() { print out the error response; }

35 votes
Vote
Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
You have left! (?) (thinking…)
Ben Hanson shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

1 comment

Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
Submitting...
  • Ben Hanson commented  ·   ·  Flag as inappropriate

    If there's software out there that depends on Exception.ToString spitting out nothing but useless information I'm also ok with creating a new virtual method in the Exception class. Name candidates include Exception.GiveMeActuallyUsefulInformation, Exception.WhereMyErrorMessageAt, Exception.IJustWantToDebugYou and Exception.F-U

Feedback and Knowledge Base