But here is what it looks what ended up solving it. Debug Breakpoint Corruptionįirst let me say that we managed to make the problem go away, although since we weren't able to repro the failure outside of my specific environment it's hard to say exactly what the problem is. To be fair, I've been working on various different projects (there are about 15 projects that I use on a regular basis plus many test and 3rd party projects) and this one is the only one where I've run into this behavior, so this is most likely a very rare edge case (and I feel oh so lucky about that!).Īs I've been in Redmond on the Microsoft Campus for the MVP Summit this week I pinged some of the VS debugger folks and they were kind enough to let me show them the issue in person today and together we poked around to try and figure out what's causing this problem. Unfortunately it looks like in this particular case it ended up causing a problem. With this new feature the existing behavior of Property evaluation (which are essentially functions) has also changed and this new behavior is now the default. The Visual Studio 2013 Debugger introduces a new feature which allows evaluating the result value of functions. #MICROSOFT WEBMATRIX VS EXPRESSION WEB 2015 CODE#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. #MICROSOFT WEBMATRIX VS EXPRESSION WEB 2015 UPDATE#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. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |