Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Visual Studio 2013 stopped showing variable values when debugging

In a particular project I recently started the debugger started acting funny. When I'm debugging and it is paused at a breakpoint, Data Tips don't show up, some of the variable values don't show up in the Locals and Autos windows, and there are some strangely named variables in the Locals window (the ones starting with "CS". The other ones are my variables):

enter image description here

I can't for the life of me figure out what is different about this project than my other ones. I'm running Visual Studio 2013 in Windows 8.1. The project is a Windows Phone 8 project, with the only added references being Fody, PropertyChanged.Fody, HttpClient et alius, and JSON.net.

Any help would be appreciated.

like image 285
SonofNun Avatar asked Mar 08 '14 21:03

SonofNun


People also ask

How can I see the variable value while debugging in Visual Studio?

When stopped in the debugger hover the mouse cursor over the variable you want to look at. The DataTip will appear showing you the value of that variable. If the variable is an object, you can expand the object by clicking on the arrow to see the elements of that object.

How do you see variables in VS code?

Display a data tipSet a breakpoint in your code, and start debugging by pressing F5 or selecting Debug > Start Debugging. When paused at the breakpoint, hover over any variable in the current scope. A data tip appears, showing the name and current value of the variable.

Which of the following Windows displays the variables while debugging?

The Autos and Locals windows show variable values while you are debugging. The windows are only available during a debugging session.


2 Answers

I had the same problem here (also using windows 8.1 and VS 2013)

To fix it you need to open in VS Tools | Options | Debugger | General and enable the flag [Use Managed Compatibility Mode], which essentially gives you the VS 2012 function evaluation behavior.

enter image description here

Reference: http://weblog.west-wind.com/posts/2013/Nov/21/Visual-Studio-2013-Could-not-evaluate-Expression-Debugger-Abnormality

like image 181
André Junges Avatar answered Oct 04 '22 13:10

André Junges


[Build] => [Clean solution] has fixed this issue for me when nothing else has worked including emptying the symbol cache.

like image 32
Jeff Avatar answered Oct 04 '22 14:10

Jeff