The visualizer encountered an internal exception and must be closed

Question

I use Visual Studio 2022. When I try to use the IEnumerable visualizer, I see this error

The visualizer encountered an internal exception and must be closed

• I reset all Visual Studio settings, but problem is still here

• I have not used the "Use Managed Compatibility Mode" option

Analiese

same happened with me after updating VS2022 to 17.7.4 – Memorandum

Answer 1

This worked for me. Open VS 2022, then go to [Tools] -> [Nuget Package Manager] -> [Package Manager Console]. Run 'Install-Package Newtonsoft.Json' This will install the latest version which matches the version required by VS2022 in my case.

Winnifredwinning

yes. this worked! – Memorandum

Answer 2

While @gregohumber's answer provides a fix, it requires modifying packages for the project in question which may not be viable (or desired). It also strikes me as strange that Visual Studio would interact with the dependencies of one's own project, which seems to be a bug in at least some cases (like here).

I'd recommend the workaround discussed in this SO answer:

1. While debugging, check the path of the Newtonsoft.Json.dll file being loaded (Debug > Windows > Modules)
2. Copy the appropriate DLL from the Visual Studio installation directory ([VS Install Path]\Common7\Packages\Debugger\Visualizers\Newtonsoft.Json)
3. Replace the DLL from your application's build directory with the VS version

Yellowweed

Answer 3

If possible, please share a minimalize reproduce sample.

Please make sure the Just My Code is enabled:

and if this issue is caused by the new version of Visual Studio, you could download and install the older version Visual Studio via this:

Release Dates and Build numbers of Visual Studio

Headway

This option was active, I have tested in active and inactive mode, but the problem was not solved. After installing Visual Studio 2022, I had to install 2019. When I noticed this problem, I assumed it had something to do with it, so I uninstalled Visual Studio 2019, but it didn't fix the problem. I deleted version 17.7.4 and reinstalled it, but the problem is still there. Therefore, this problem probably appeared after the update and it is better to wait until the next version to fix it. – Analiese

@FarzanehTalebi I am sorry, VS2022 old versions are here: learn.microsoft.com/en-us/visualstudio/releases/2022/… You can have a try of the old versions. :) – Headway