You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the SDK is built against Roslyn 1.0. This means that it if it is run against analyzer packages that use a newer version of Roslyn, it will not find any analysis rules (the SDK will be looking for classes that inherit from DiagnosticAnalyzer v1.0, but the analysis rules will be inheriting from e.g. v2.0).
This will not affect the version of Roslyn that is required to execute the rules during analysis, only the version of Roslyn that must be available when running the SDK.
Options to consider
binding redirect, relying on backwards compatibility (if it works, this would maximise the versions of MSBuild/Roslyn the SDK can work with)
change the version of the NuGet package used by the SDK
The text was updated successfully, but these errors were encountered:
Currently the SDK is built against Roslyn 1.0. This means that it if it is run against analyzer packages that use a newer version of Roslyn, it will not find any analysis rules (the SDK will be looking for classes that inherit from DiagnosticAnalyzer v1.0, but the analysis rules will be inheriting from e.g. v2.0).
This will not affect the version of Roslyn that is required to execute the rules during analysis, only the version of Roslyn that must be available when running the SDK.
Options to consider
The text was updated successfully, but these errors were encountered: