Hi @mickaelcaro thank you for the response. Please see the attached yaml file, we do the following: initialize SonarCloud, build the solution, run the analysis, and publish the results. Let me know if there is an error in that yaml.
Thanks again for your responses and time! I see one of the code smells but one that shows up in SonarLint and not on the scan is the block of commented out code. I was curious why some rules appear and others do not.
I noticed it with a block of code commented out not being found in the PR scan. Unfortunately our trial is over so I cannot test out other scenarios, but we did notice the inconsistencies.
I am closing this topic as it doesnāt have enough details to derive some actions from it. If you are willing to try again and see the same problem, please open a new topic.
Regarding why not all expected code smells appeared on the PR, there could have been multiple issues, possibly:
detection of test projects - there have been some inconsistencies regarding test project detection, read here about some of them; also, in the past releases of the Scanner for .NET (5.1 and 5.2) we fixed them; this month we will deploy a new analyzer version to :sonarcloud: which will close this topic
detection of generated code - we fixed some problems there ( #2228), the fix will be shipped in the next release of our .NET analyzers