Visual studio 2012 - local residents have disappeared

When debugging VS2012, I found that I can no longer access the values โ€‹โ€‹of the variables:

  • The Locals window does not display anything (in the photo below).
  • In the "Observation" window, I am informed "Unable to evaluate expression" for any expression (also in the figure below). My personal favorite is that he cannot evaluate true .
  • And dragging any variable does not show any tool tips.

Image showing no locals

What I tried:

Restart Visual Studio

Computer reboot

Check loading loaded modules for debugging symbols

Uninstall the TeamCity plugin I installed yesterday

Search in the "Tools / Options / Debug" section for anything obvious (and disable other extensions that worked fine)

EDIT: I also tried to create a new solution.

I also noticed that the call stack shows a few empty lines, where I assume that they should be the names of external methods (pictured above). I'm not sure if this is relevant, but worth mentioning.

+8
debugging visual-studio-2012
source share
6 answers

I eventually managed to figure this out on my own, so I will give my solution here if someone else has a problem:

I found that in Tools-> Options-> Debugging-> Symbols it was pointing to the old NuGet character server. For some reason, the wrong symbol server looked like it was shooting all systems of local and immediate windows.

Updating the character server fixed my problems.

+6
source share

I will add this answer as I had the same problem with a different resolution.

I mistakenly closed the window of local residents and could not find it, as it was not with other windows in the VIEW menu. I found it on the Windows DEBUG menu.

or optionally:

Ctrl + Alt + V, L

+6
source share

I will add this answer as I had the same problem with a different resolution.

I also got this in a web project. Neither restarting Visual Studio, nor any other solution in this thread bypassed it.

My solution was to restart IIS. After that, I rebuilt the project and started it, and the locals worked again.

+3
source share

This happens when your Optimize code is marked in the project properties in the Build section.

+1
source share

I had the same problem updating Visual Studio 2013 Update 5 on Windows 10 when using remote debugging.

According to another SO question, locales / variables are split into remote debugging tools.

I haven't found a solution yet, but I'll upgrade to Visual Studio 2015, so I haven't looked for it either ...

0
source share

Please check the answer here .

In a nutshell, you need to open: Tools> Options> Debugger> General and enable the flag [ Use compatible compatibility mode ] at the end of the list.

0
source share

All Articles