Z
Zytan
I have the simplified build ("show advanced build configurations"
turned off), so that pressing F5 runs in DEBUG mode with the
debugger. When an assertion fires, I find that I cannot 'watch' some
data, it explains that "Cannot evaluate expression because the code of
the current method is optimized". I know that I can go into Project-
My question: WHY is the DEBUG build optimizing code? Shouldn't that
only occur for RELEASE builds? And, is my simplified build settings
("show advanced build configurations" turned off) causing this
"optimize code" to be set for both DEBUG and RELEASE, whereas maybe it
would only be set for RELEASE?
Zytan
turned off), so that pressing F5 runs in DEBUG mode with the
debugger. When an assertion fires, I find that I cannot 'watch' some
data, it explains that "Cannot evaluate expression because the code of
the current method is optimized". I know that I can go into Project-
Properties->Build->"optimize code" and turn this off.
My question: WHY is the DEBUG build optimizing code? Shouldn't that
only occur for RELEASE builds? And, is my simplified build settings
("show advanced build configurations" turned off) causing this
"optimize code" to be set for both DEBUG and RELEASE, whereas maybe it
would only be set for RELEASE?
Zytan