The SonarQube Extension is not finding any issues in our code anymore. The SonarQube server scanning is still properly identifying the issues. The extension used to work properly early last year. This issue also effects our other developers. .NET code is being properly scanned by the extension. Unfortunately, I am unsure exactly when the extension stopped working. I have attached a log of the scan. There’s are errors in the log from SonarQube incorrectly replacing “%20” to spaces in or project name. I have tested removing any space and %20 from the project name but it still doesn’t find any issues.
is a verbose log from a fresh startup from when visual studio starts up. There is only 1 file open for it to scan. In the file I have added the code “const int &weekdayCount = 7;” to force an issue to show up and it’s not. I uploaded it again just incase I made a mistake in the original upload.
After a conversation with @Devon.Reynolds and attempts at fixing it, we decided that we can’t fix it at the moment and the workaround is to not use % signs in project/file names. Closing this thread