The dark side of errors
I just run into this one, and it completes very nicely my previous post about good errors.
Can you figure out what the problem is? I know what the Western Regional Power Committee is doing in my application, but that exception is the epithom of bad error messages, the only thing that tops it is code that calls System.Environment.FailFast("bye!"), which cause an ExecutionEngineException.
The root cause of this error message? A missing referrer header. But you really don't want to know how I got to that explanation.

Comments
Comment preview