Error in Visual Studio 2026: 'VisualStudio.SpellChecker.Common, Version=2025.12.13.0 not found

[graymatter00]

Using Visual Studio 2026 v18.1.1.

Create a new project using the C# ASP.NET Core Web App (Model-View-Controller) template.

The following error, and many more like it, is produced, referencing the project node in the Solution Explorer.

Severity	Code	Description	Project	File	Line	Suppression State	Details
Warning (active)	AD0001	Analyzer 'VisualStudio.SpellChecker.CodeAnalyzer.CSharpSpellCheckCodeAnalyzer' threw an exception of type 'System.IO.FileNotFoundException' with message 'Could not load file or assembly 'VisualStudio.SpellChecker.Common, Version=2025.12.13.0, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.'.
Exception occurred with following context:
Compilation: GraymatterEnterprises
SyntaxTree: C:\Users\tonyg\Projects\Graymatter-v2\GraymatterEnterprises\Data\Migrations\00000000000000_CreateIdentitySchema.cs

System.IO.FileNotFoundException: Could not load file or assembly 'VisualStudio.SpellChecker.Common, Version=2025.12.13.0, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.
File name: 'VisualStudio.SpellChecker.Common, Version=2025.12.13.0, Culture=neutral, PublicKeyToken=null'
   at VisualStudio.SpellChecker.CodeAnalyzer.CSharpSpellCheckCodeAnalyzer.AnalyzeSyntaxTree(SyntaxTreeAnalysisContext context)
   at Microsoft.CodeAnalysis.Diagnostics.AnalyzerExecutor.ExecuteAndCatchIfThrows_NoLock[TArg](DiagnosticAnalyzer analyzer, Action`1 analyze, TArg argument, Nullable`1 info, CancellationToken cancellationToken)
-----

Suppress the following diagnostics to disable this analyzer: VSSpell001	GraymatterEnterprises	C:\Users\tonyg\Projects\Graymatter-v2\GraymatterEnterprises\GraymatterEnterprises.csproj	1		

[EWSoftware]

I'm not able to reproduce this. Perhaps uninstall the extension and reinstall the latest release. Once thing you can try is go into the settings folder (%LOCALAPPDATA%\EWSoftware\Visual Studio Spell Checker) and delete the AnalyzerCodePath.txt file. It's used to find the assemblies for the code analyzer but there was an issue with a prior release related to it. Removing it should recreate it and resolve any issues related to that.

[graymatter00]

Hi Eric. Sorry for the delay in replying.

1. I have uninstalled and re-installed the extension a number of times without change.

2. I deleted the AnalyzerCodePath.txt file as instructed. No change. However, that file was not recreated. The only file in that folder after restarting VS with the extension installed is VSSpellChecker.editorconfig.

3. I can reproduce the error on all the C# solution/project templates that I've tried. That is;

4. I'm using .Net10 but have tested it with .Net9, 8 and 6. Same error.

5. All other extensions seem to be operating correctly.

6. Below is a complete Error List from a newly created Blazor Web App project.

ErrorList.txt

Any assistance is appreciated.

[EWSoftware]

I'm still not able to reproduce this issue. I created a new project from the Blazor Web App template and accepted defaults for all the settings. When opening any of the files, they're spell checked as expected. Can you try creating a simple console app and see if it spell checks as expected and recreates the analyzer path file?

[graymatter00]

I re-enabled the extension and created a C# console app, as requested. Same result.

I've attached a video of the app creation, showing the result. I've also attached screenshots confirming the VS 2026 version, and File Explorer showing that AnalyzerCodePath.txt has not been re-created. And I've attached the previously existing AnalyzerCodePath.txt file that I deleted as instructed by you earlier. (I kept a copy.)

I have also run the same tests on a second computer with a near-identical setup, with exactly the same result.

Could it be that I don't have a required VS component or SDK installed?
Could it be a conflict with another extension?

Screen.Recording.2025-12-31.105752.mp4

AnalyzerCodePath.txt

[EWSoftware]

I doubt it's a missing component or SDK since it doesn't have dependencies other than the core editor and Roslyn language services. It would likely have been reported by many more users too if that were the case. A conflict with another extension is possible. You'd have to disable them and if the code analyzer works, try adding them back one at a time to figure out which one is causing the conflict. If you willing, you could download the code and try running it under the debugger to see if you can find out why it isn't resolving the assembly reference. It can point out where to set the breakpoint to trace through that part of it.