Could you please be a bit more precise on which kind of error do you encounter ?
Thanks.
Could you please be a bit more precise on which kind of error do you encounter ?
Thanks.
Hi,
(While looking at the log I realized that one of the links did not work: https://sonarcloud.io/documentation/analysis/scan/sonarscanner-for-azure-devops)
Here are the logs:
2020-02-20T08:31:49.0351301Z ##[section]Starting: prepare analysis on sonarcloud
2020-02-20T08:31:49.0355399Z ==============================================================================
2020-02-20T08:31:49.0355528Z Task : Prepare Analysis Configuration
2020-02-20T08:31:49.0355599Z Description : Prepare SonarCloud analysis configuration
2020-02-20T08:31:49.0355689Z Version : 1.10.0
2020-02-20T08:31:49.0355736Z Author : sonarsource
2020-02-20T08:31:49.0355788Z Help : Version: 1.10.0. More Information
2020-02-20T08:31:49.0355890Z ==============================================================================
2020-02-20T08:31:49.5481738Z SYSTEMVSSCONNECTION exists true
2020-02-20T08:31:49.9210690Z [command]/opt/hostedtoolcache/dncs/3.1.101/x64/dotnet /home/vsts/work/_tasks/SonarCloudPrepare_xxxxxxxxxxxxxxxxx/1.10.0/dotnet-sonar-scanner-msbuild/SonarScanner.MSBuild.dll begin /k:Workplace-Domain /o:xxxxxxxxxxx
2020-02-20T08:31:49.9405817Z ##[error]It was not possible to find any compatible framework version
The framework ‘Microsoft.NETCore.App’, version ‘2.0.0’ was not found.
(While looking at the log I realized that one of the links did not work: https://sonarcloud.io/documentation/analysis/scan/sonarscanner-for-azure-devops)
You should add a trailing forward slash in the url, this works.
For the rest, indeed, we haven’t yet shipped the full dotnet core 3 new assembly in the extension, this will be done soon, i created a ticket : https://jira.sonarsource.com/browse/VSTS-230
In the mean time and as a workaround, you can invoke the scanner for msbuild in command line, using the dotnet core 3 assembly.
Sorry for the inconvenience !
Mickaël
Hi,
Thanks for all the replies!
Regards
here is the workaround I used for the mean time! may help others.
verify in SonarQube project the analysis as part of build is posted.
Hi there,
currently we are using the workaround. But it’s ugly & the pipeline is longer. Is there any news regarding porting it to .net 3.x runtime?
Appreciated!
J.
anyone?
Hi, we are also experiencing this same issue now we’ve finished a company wide upgrade from our legacy codebase and now can’t use SonarQube since we are using NETCore 3.1.
Any further info on when this will be supported?
Thanks.
And I see it is still in “TODO” state
https://jira.sonarsource.com/browse/VSTS-230
Any hope it will be implemented soon?
Please fix this. .NET Core 2.1 (LTS) will be unsupported in 3 weeks! This will be a security issue.
EOL date: 21 Aug 2021. See .NET Core | endoflife.date
I guess this should fix it:
As there is a msbuild version for .NET Core 3
@mickaelcaro please make sure this will be fixed ASAP. In 2 weeks .NET Core 2.1 will be unsupported.
That means - .NET Core 2.x will be unsafe!
See .NET Core 2.1 will reach End of Support on August 21, 2021 | .NET Blog (microsoft.com)
That said, we won’t be issuing security updates for .NET Core 2.1 starting September 2021
and
.NET Core 2.1 will be reaching end of support on August 21, 2021 and after this date we will no longer provide updates including security fixes, or technical support for this version. We strongly recommend you migrate your applications to .NET Core 3.1 or later before this date.
To be clear, 2.0, 2.2 and 3.0 are already unsupported. The only supported version for 2.0+, is 3.1 - see .NET Core | endoflife.date
We also need time to update this extension!
See my PR of a fix
No update. No response. And .NET Core 2 is now officially not secure any more.
Very disappointed sonarsource doesn’t understand security.
Please update the ticket with updated version
Hi,
We are aware that the .NET Core 2 framework has been deprecated few days ago. This is on the way and will be released within the next 2 weeks.
Kind regards,
Christophe
This change couldn’t come soon enough.
Gee! for sure it was related. See the fix there.