CODEWITHSUNDEEP
visual-studiovisual-studio-2015visual-studio-debugging
baochan
baochan

Reputation: 381

The Diagnostic Tools window does not support debugging using the 'Script' debug engine

I am getting this message in the Diagnostic Tools window in Visual Studio 2015 when debugging a C# MVC web application.

I've checked solutions to a similar problem: Visual Studio 2015 diagnostics tool does not support current debugging configuration but using administrator mode and disabling "Use Managed Compatibility Mode" do not help. I've also tried disabling Options -> Debugging -> Just-In-Time -> Script, which still has no effect. It's the only reference I can find to 'Script' and I don't know how to change my debug engine.

I've also tried this solution from the web about setting the Visual Studio locale to the same as the OS, but they're both using US English. https://blogs.msdn.microsoft.com/devops/2015/05/06/known-issue-for-diagnostics-tool-window-in-visual-studio-2015-rc-the-diagnostic-tools-failed-unexpectedly/

Can anyone tell me what I'm doing wrong?

Upvotes: 2

Views: 2233

Answers (2)

Jack Zhai
Jack Zhai

Reputation: 6436

If you create a default MVC web app, and then debug your app, could you use the Diagnostics tool in your side? I test it in my side, it works well using the default settings, my OS and VS all are the English version. So you use the same language version, am I right?

If possible, you could check the following steps:

  1. Reset your VS settings:

    Open VS, TOOLS->Import and Export Settings Wizard->Reset all settings->select “No, just reset settings, overwriting my current settings”->Choose a Default Collection of settings(I often use the General or C#).

  2. Please use the latest VS2015 with update 3.

  3. Maybe you could download and install the match VS version as your windows directly, debug it again.

Upvotes: 2

Mystic Lin
Mystic Lin

Reputation: 375

My error message is

The diagnostic tools failed unexpectedly. The Diagnostic Hub output in the Output window may contain additional information.

Try to modify the Environment Variable TEMP as following rules and reopen Visual Studio. That works for me, maybe it also works for you. My IDE is Visual Studio Enterprise 2015 Update 3.

It must only one path in TEMP. For example,

Fail:%USERPROFILE%\AppData\Local\Temp;C:\OTHER_PATH
Fail: %USERPROFILE%\AppData\Local\Temp\;C:\OTHER_PATH
Pass: %USERPROFILE%\AppData\Local\Temp

Upvotes: 2

Related Questions