A question came up recently on stack overflow concerning the
display of newlines in the immediate window.   The author noted
that any .ToString method which contained a newline printed
incorrectly when evaluated in the immediate window.  For example
given the following ToString implementation  public override
string ToString() {     return "Hello" + Environment.NewLine +
"World"; The immediate window would display the following. 
Noticed how the newline was printed as the actual escape
sequence instead of a physical newline.    This behavior is not
limited to ToString calls but will occur for any place an
expression evaluates to a raw string.   This behavior in the
immediate window case is a fallout from the architecture of the
debugger components.   The current level of fidelity in the
debugger APIs prevent the expression evaluator from knowing
which window it is providing data for.  It is simply asked to
evaluate expressions and provide data with very little in the
way of context.  In some ways this is a go