Hello @marcilioneto,
Is there any issue regarding new versions?
This was quite a big internal change and it seems you found an issue. Using sonar.scanner.useSonarScannerCLI=true is the fallback to unblock you.
Please help us finding the root cause of the problem. Can you please provide more details about the environment you are using?
Share your pipeline
If you are using the scanner in a Continuous Integration pipeline, please share the pipeline definition and which CI environment you are using (GitHub Action, AzureDevops, etc.). Make sure to redact any secrets from you pipeline definition before posting it here.
Share the Scanner for .NET verbose logs
Please provide verbose logs with sonar.scanner.useSonarScannerCLI=false:
Add /d:"sonar.verbose=true" to the Scanner BEGIN step. Examples:
dotnet sonarscanner begin /k:"MyProject" /d:"sonar.verbose=true"
SonarScanner.MSBuild.exe begin /k:"MyProject" /d:"sonar.verbose=true"
- task: SonarCloudPrepare@3 # or SonarQubePrepare@3
inputs:
SonarCloud: 'sonarcloud'
organization: 'foo'
scannerMode: 'dotnet'
projectKey: 'foo_sonar-scanning-someconsoleapp'
projectName: 'sonar-scanning-someconsoleapp'
extraProperties: |
sonar.verbose=true
Please note that most of the relevant logging will happen during the END step, i.e. in SonarCloudAnalyze, SonarQubeAnalyze or Run Code Analysis.