Skip to main content

Return to Answer

edited body
Source Link
Sabuncu
Sabuncu
  • 5.2k
  • 5
  • 58
  • 94

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 "Immidiate"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.

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 "Immidiate 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.

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.

Source Link
dugas
dugas
  • 12.3k
  • 3
  • 46
  • 53

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 "Immidiate 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.