Update 1:
After Updating visual studio to version 2015 update 2 RTM the problem still exist.
Update 2 patch available 4/12/2016 :
Thanks to Patrick Nelson.
a patch has been released
You can download the patch here.
Update 3 8/16/2016:
Latest vs 2015 update 3 KB3165756 has the same problem do not update
Version Used:
Latest stable version on visual studio update 2 rc
Disabled all my extensions and also restarted my all settings
Steps to Reproduce:
Expected Behavior:
To be able to debug the asp.net application
Actual Behaviour:
I can't explore context of variable inside visual studio editor or immediate windows i get the following error in immediate windows
error CS0103: The name 'myvariable' does not exist in the current context
using trial and error method i found a workaround for know that will bring back context debugging.
from tools > options > debugging > general then enable
This is a bug that was introduced in Visual Studio 2015 Update 2. Essentially the debugger is unable to inspect local variables in dynamic modules. We released a hotfix for it today.
You can download the patch here. Documentation for the patch is here. Let me know if the patch does not fix your particular scenario.
and also (Use Managed Compatibility Mode - Enabled) please make sure json configuration file has this sections
"frameworks": {
"dnx451": { },
"dnxcore50": { }
},
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