Debug Visualizers and Why Soap Exceptions suck!
Repeat after me ...Soap Exceptions Do not Serialize. This isn't new information, in fact I have known this for years, however, tonight I managed to fall into the trap of forgetting this small but important detail.
This all started because I was tired of having to drill down in the debugger to see what the real error was for the Soap Exception. I thought maybe, I might just throw together a Debug Visualizer to add to my collection. I kept getting only part of the data, I wouldn't get the Detail property.
All of a sudden it all came back, something about Debug Visualizers needing to serialize the data. In my search to confirm my fear, I did run across a good post on visualizers by Frans Bouma - Tips for writing debug visualizers - you can read that here, it has some good tips if your writing your own visualizers. So yes, the bottom line is Soap Exception and a debug visualizer does not play well. Back to the drawing board on that idea.
So here's my shout out to the owner of the Soap Exception - how about making it serialize so it will work with Debug Visualizers among other things?
Reader Comments