-
Notifications
You must be signed in to change notification settings - Fork 33
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
Instance of analyzer can not be created - missing dependency for Microsoft.CodeAnalysis? #771
Comments
Hi @StarWars999123 |
VS 16.10.3. So shouldn't be the reason why. |
@StarWars999123 Unlike with other NuGet packages, the From a command line, can you type: When you build your project on the command line with: If you already have VS2022, there is no reason to use VS2019. Alternatively, the latest VS2019 is version 16.11.38. Maybe updating to that version fixes things. |
So, I am not able to update those systems. For certain reasons, those systems are still stuck with primarily VS2019. Right now, we were only able to reference the NUnitAnalyzer with a condition to be ignored on CI builds. |
According to the NET 5.0 download page .NET 5.0.4xx came with VS2019 16.11.14. The version 5.0.3xx isn't even available for download. If you can't update VS2019 to the latest version, I see you have .NET 6.0.201 installed. {
"sdk": {
"version": "6.0.200",
"rollForward" : "latestPatch",
"allowPrerelease": false
}
} Otherwise, you need NUnit package 3.3.0 as the last version that depended on Microsoft.CodeAnalysis version 3.8.0 |
Hi,
while I was able to install the package, compile and refactor my projects with Visual Studio 2022, I faced the following warning on CI upon compile with VS2019:
I referenced the project in my SDK style .csproj targeting net472/net48 as follows:
Is my package reference (created automatically) faulty or are you missing a dependency reference to Microsoft.CodeAnalysis?
The text was updated successfully, but these errors were encountered: