In more complex code with more scoped variables, I basically see a wall of red icons - nothing at all is evaluated. Instead I get the error icon and 'Could not evaluate expression'. Here both this and user are in scope and instantiated, but the debugger doesn't show the evaluated values/references for those objects to drill into. In this example, you can see a couple of scoped values in the debugger. If you still have issues or simply can’t update to Update 2 yet, then the rest of this post is still relevant. It appears that the issues discussed in this post have been addressed in Visual Studio 2013 Update 2, so updating to Update 2 (or later) might be the best path for avoiding the funky debugging behaviors described in this post. I was trying to debug my application on a breakpoint and when I hit the break point, none of the debugger member and watch expressions were working - specifically everything shows 'Could not evaluate expression' in the debugger. Last week I ran into a really strange problem with an older WebForms application on Visual Studio 2013.
0 Comments
Leave a Reply. |