-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AD1000 warning after recent update #283
Comments
Where are you seeing these? I know it doesn't load the analyzer but I didn't see any errors when testing the combined 2017/2019 version in VS 2017 on my PC. |
Okay, I don't have the error list open or use it that much so I missed it. I was expecting the usual info bar or dialog box if it failed to load so thought it was just ignoring it. I'll have to separate the 2017 version out into its own extension that doesn't include it since the version of code analyzer API used by 2017 is too old and is missing some key features I need to support what I need to do. |
Where is this older version as I'm in the same boat? Severity Code Description Project File Line Suppression State |
Older releases can be downloaded from the Releases page |
After the last update (I believe version 2023.5.8.0), there is a VS warning (see below). I'm using VS Pro 2017 v 15.9.42
As I could see the VisualStudio.SpellChecker.CodeAnalyzer.dll file was in the specified folder. I guess it wasn't the right version.
The warning disappear after reinstalling an older version of the Visual Studio Spell Checker.
Severity Code Description Project File Line Suppression State Warning AD1000 An instance of analyzer VisualStudio.SpellChecker.CodeAnalyzer.CSharpSpellCheckCodeAnalyzer cannot be created from C:\USERS\VIDO\APPDATA\LOCAL\MICROSOFT\VISUALSTUDIO\15.0_70D54E06\EXTENSIONS\0434OAVB.3B4\VisualStudio.SpellChecker.CodeAnalyzer.dll: Could not load file or assembly 'Microsoft.CodeAnalysis, Version=3.3.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.. 1 Active
The text was updated successfully, but these errors were encountered: