You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The MS build tasks for Sonar has a dropdown where the scanner is selected. The dropdown includes all MSbuild capabilities in addition to the MSBuild Sonar scanner capability. his is confusing for developers that configures Sonar scans. This might be because the sonarscanner is using the same capability type as MSBuild. Is there a way to prevent al MSbuild capabilities from showing up in the dropdown.
Looking back, it might have been better to use an own capability type for the MSBuild SonarScanner to avoid confusion with the other MSBuild capabilities.
At this point, we think a change to an own capability type is not ideal and will lead to more confusion than clarity. Our suggestion is to name the MSBuild SonarScanner explicitly to distinguish them from the other MSBuild capabilities.
Thanks for understanding,
Christian - Mibex Software