Here’s the exception I received today:<\/p>\n
Isn’t it lovely? Do the authors think I have a little leprechaun sitting on the user machine and waiting for my command to retrieve And if not, what do they expect my handling for oddball exceptions to be like? Perhaps something like<\/p>\n <\/code><\/p>\n Not gonnna happen. A good exception should have everything in its System.Reflection.ReflectionTypeLoadException. Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.<\/code><\/p>\nthe pot of gold<\/strike> the LoaderException<\/code> property?<\/p>\n<\/p>\ncatch (StrangeExceptionVarietyOne ex)\n{\n Log(ex.ToString());\n Log(ex.FunkyPropertyOne);\n}\ncatch (TotallyObscuredExceptionTwo ex)\n{\n Log(ex.ToString());\n Log(ex.TotalObscurerAdditionalDataCollection);\n}\ncatch (ReflectionTypeLoadException ex)\n{\n Log(ex.ToString());\n foreach (var loaderEx in ex.LoaderExceptions) Log(loaderEx.ToString());\n}\n...<\/pre>\nToString()<\/code>. As in “for debugging purposes, AggregateException<\/code>‘s ToString<\/code> implementation outputs a string rendering all the contained exceptions<\/i>“. This is a good exception. This is an exception I like to work with. Why can’t all exceptions be like that?
\n