Menu
When debugging asp.net code (running against IIS, and using Visual studio 2013) and in a breakpoint and trying to evaluate a variable using quick watch i quite often get "unable to evaluate expression".
deleting the .suo from the asp.net project folder seems to resolve the issue (After reloading the solution)
Is this a recognised bug? getting this a lot now in Visual studio 2013 on more than one machine.
516
Evaluate a complex expression in the editorClick Run | Debugging Actions | Quick Evaluate Expression Ctrl+Alt+F8 .
In the Visual Studio toolbar, make sure the configuration is set to Debug. To start debugging, select the profile name in the toolbar, such as <project profile name>, IIS Express, or <IIS profile name> in the toolbar, select Start Debugging from the Debug menu, or press F5.
I faced it today with VS2013.
Goto Tools --> Options --> Debugging --> General --> Scroll to the bottom for "Use Managed Compatibility Mode" and Select the option.
Screenshot from the blog(url below): 
Restart you debugging. Hope it helps others.
What Helped Me is below!
Visual Studio 2013 Could not evaluate Expression Debugger Abnormality turned out to be very helpful.
Also, you could see @Dreamers answer Unable to debug managed code using visual studio 2013
69
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
