Nuget tags specifying required .NET version are incorrect

[KraftyKanuck]

The dotnet-sonarscanner lists .NET50 and .NET Core 2.0 as it's supported versions, while the Dependencies tab lists the correct dependencies: NetCoreApp2.1/3.1 or 5.0.

You cannot install the 5.X dotnet-sonarscanner with 2.0 (or 2.2) installed, you MUST have 2.1 installed.

[andrei-epure-sonarsource]

Thanks @KraftyKanuck . You are right, we need to improve these tags.

I would suggest changing your pipelines from having only netcore 2.1 installed because that's out of support (Microsoft stopped supporting it in August 2021).

[andrei-epure-sonarsource]

@duncanp-sonar do you know where these tags get computed from? because the nuspec tags don't refer to this.

I guess they come from the TFM encoded in the tools/... path

, however we cannot change that without breaking compatibility. We'll only be able to fix this when we'll change the packaging.

This is what nuget.org shows: https://www.nuget.org/packages/dotnet-sonarscanner/#supportedframeworks-body-tab

[duncanp-lseg]

@andrei-epure-sonarsource no, I don't know, but that seems like a reasonable guess. It would be easy enough to test.

[csaba-sagi-sonarsource]

@andrei-epure-sonarsource do you think that we will work on this? We plan to change the packaging of the global tool anyway.

[csaba-sagi-sonarsource]

I am closing this issue as we are planning to have only one scanner for dotnet which is built for .NET and one for .Net framework. The progress on that can be tracked here.