When debugging an ASP.NET Core application, using Visual Studio 2015, I cannot see the variable, parameters and field values, when, for example, I hover them. I cannot add them to the watch as well. I am running in debug.
Asked
Active
Viewed 3,061 times
10
-
1Are you running on CoreCLR or Desktop? What VS version are you using? – Victor Hurdugaci Feb 22 '16 at 07:01
-
1Visual Studio 2015 Ultimate, targetting both .NET Core and Desktop. – Ricardo Peres Feb 22 '16 at 08:21
-
Sorry, I should have been more explicit. In the about page, look for the full VS build number. Also share the web tools package version which is on the same page – Victor Hurdugaci Feb 22 '16 at 15:18
-
Microsoft Visual Studio Enterprise 2015 CTP Version 14.0.25008.00 Update 2 CTP Microsoft .NET Framework Version 4.6.01055 Installed Version: Enterprise ASP.NET and Web Tools 2015 (RC1 Update 1) 14.1.20203.0 ASP.NET and Web Tools 2015 (RC1 Update 1) – Ricardo Peres Feb 22 '16 at 15:36
-
Myself and a colleague of mine are having the same issue. I'm also using Microsoft Visual Studio Enterprise 2015 CTP (version 14.0.25008.00 Update 2 CTP), my colleague uses the Community edition. We tried safe mode and that didn't help. Reported via the tools in VS. – Johan B Feb 24 '16 at 09:39
-
1Thanks, nice to see that I'm not alone! :-) – Ricardo Peres Feb 24 '16 at 12:35
-
We tried playing around with the dnvm changing the runtime and architecture, but no joy. Also happens in a clean project. – Johan B Feb 25 '16 at 09:17
-
I asked Microsoft directly, but got no response, yet... – Ricardo Peres Feb 25 '16 at 12:01
-
To be fair, it's a CTP and they clearly stated they will not support it. "We do not advise that you use it in a production environment." and of course I ignored their advice, because why not? Wel... – Johan B Feb 25 '16 at 12:25
-
1Well, if nobody tries it, then who will spot these problems? :-) – Ricardo Peres Feb 25 '16 at 14:09
-
Can you check if it works with VS2015 Update 1? – Ricardo Peres Feb 25 '16 at 14:09
-
What do you mean update 1? The debugging worked fine in update 1 (and its CTP) until we updated. – Johan B Feb 26 '16 at 10:04
-
I wasn't sure of that. – Ricardo Peres Feb 26 '16 at 12:29
-
@VictorHurdugaci any updates on this issue? – Johan B Mar 03 '16 at 08:47
-
It has been reported to Microsoft, but no dates yet. – Ricardo Peres Mar 03 '16 at 10:33
-
I'm curious. Did you got a chance to try out Update 2 RC yet? This update has resolved the issue entirely for us. No 'Use Managed Compatibility Mode' necessity. :) – Johan B Mar 10 '16 at 09:39
-
I am using it, but it didn't resolve anything, unfortunately. – Ricardo Peres Mar 10 '16 at 23:27
2 Answers
7
We might have found a solution (or at least a workaround) for the problem. If we go into Tools > Options > Debugging and enable Use Managed Compatibility Mode then we can inspect all the values we like.
I hope this solves the issue for you as well.
Update: Visual Studio 2015 Update 2 RC fixed the issue for me, but unfortunately not for the OP.
Johan B
- 890
- 3
- 23
- 39
-
1Thanks! Enabling `Use Managed Compatibility Mode` works for me on Visual Studio 2015 Update 2 RC – slowkot Mar 30 '16 at 17:11
-
1
3
This behavior happens with 1.0.0-rc1-update1, but not with 1.0.0-rc2-16357. If possible, upgrade. Microsoft is aware of it.
Ricardo Peres
- 13,724
- 5
- 57
- 74
-
2This update attempts to fix it: https://msdn.microsoft.com/en-us/library/mt695655.aspx – Ricardo Peres Apr 25 '16 at 21:52