Hit Breakpoint When Caused by the Debugger

c# .net debugging visual-studio visual-studio-2008

After some research on this topic, I learned about FuncEval, and after reading lots of things about FuncEval I was led to the following article: Stop Mid Func Eval, Nested Break States by Mr. SteveJS. In the article he explained that starting in VS2005 you could hit a breakpoint caused by a FuncEval if the evaluation was done from the "Immediate Window" instead of the Watch or "Quick Watch" windows. So, in the above example, entering

?t.X

in the Immediate Window caused the breakpoint on the get accessor to be hit.

Related

How to create an extension to deal with multiple core data entities
How to get the transpose of a html table?
Cardinality as "size of a set" [closed]
How prove this inequality $(\sum a_{1}^{1.5})^2\ge \sum a_{1}\sum a_{1}a_{2}$
Detailed proof of $\zeta(s)-1/(s-1)$ extends holomorphically to $\Re(s)>0$
Better Notation for Partial Derivatives
If $f: \mathbb{C} \to \mathbb{C}$ is analytic and not linear, then $z, f(z), f(f(z)), \dots$ are linearly independent functions over $\mathbb{C}.$
$R$ with an upper bound for degrees of irreducibles in $R[x]$
Possible values of prime gaps
Intuition for $N(\mu, \sigma^2)$ in terms of its infinite expansion
Differentiability of Convolutions
When is an element of a free module over a principal ideal domain contained in a basis?