7

I recently downloaded visual studio 2017 because developing xamarin apps, has many utilities in more, that make me comfortable.

That said, I wonder if any of you have already downloaded and if the tooltip problem in debugging, I do not see anything. And so it is impossible to work. But panel "Locals" work. I searched online but it is still too early to find help. If anyone has had the same problem and solved tell me. Thank you.

enter image description here

i have tryed to reinstall, but don't work.

Mr. Developer
  • 3,295
  • 7
  • 43
  • 110

3 Answers3

4

Common problem, but there are several different solutions and I think I know what your problem is. Using Xamarin? Shared project? Can see some local variables but nothing inside of an async method?

  1. Everyone will tell you to check that your solution configuration is set to DEBUG and not RELEASE. This is the basic answer, "Set to DEBUG, clean, rebuild..", and to go a bit deeper, you can select Configuration Manager from the dropdown to check that not only is the project you are debugging set to DEBUG, but so are all of the (if any) projects that are dependencies. enter image description here

  2. But I'm thinking your project properties is the issue. If you are doing Xamarin and have a shared project or portable project (probably the one that has the async method that wont allow you do debug correctly!) In the portable project properties, under Build -> Advanced, change Debugging information to full and you should be good to go! enter image description here enter image description here

RobDigital
  • 515
  • 1
  • 7
  • 19
  • Changing the Debugging information in Advanced Build Settings worked for me. It was already on "Full" so I changed it to something else before going back to "Full", and now tooltips are showing! – Daren Apr 23 '19 at 10:59
1

check if your build configuration for projects is set to 'Debug'. Also look at this one -> debug watch stopped working

Community
  • 1
  • 1
xird
  • 775
  • 1
  • 8
  • 16
1

I had the same problem. workaround:

1) Place current debugger statement (the yellow arrow) one line back. 2) Execute current statement again.

This worked for me. enter image description here

Rudy Meijer
  • 210
  • 2
  • 7