It’s always fun to see an error message you’ve never seen before – even after using a product for almost 10 years. While trying to check the value of an object while sitting at a breakpoint:
Cannot evaluate expression because we are stopped in a place where garbage collection is impossible, possibly because the code of the current method may be optimized.
Microsoft has very strict guidelines about the verbiage used in their programs. I can’t believe they let an error message pass through using the word “we” in it. It’s good to know that the .NET compiler feels that we’re all in this together. Additionally, the use of the word “impossible” and the vagueness of “possibly because” and “may be” are very out of place.
I’ve never seen an error message so clearly state “That absolutely cannot be done. I know why, but I don’t know why.”