Hosted build agents on Visual Studio Team Services already meet the prerequisites listed here.

Cast Software Vs Sonarqube. Expand the capability of SonarQube and SonarLint with additional languages, by using our best in class code analyzers.

In my organisation, we are using Visual Studio Code Analysis with Microsoft ruleset for all projects. I tried out Sonar Qube and was impressed with the UI and everything that is analysed.

I want to make a case to the leadership on why we have to use Sonar Qube. * Could you help with some pointers to make the case? * Can we use both - Sonar Qube and VS Code analysis? * How better is it to compared to VS Code Analysis? * We also have HTML, Javascript code in our projects. I believe SonarQube has option to analyse html and javascript, but VS Code analysis does not analyse. Is there any major advantage that I can capture?

* In addition to ASP.NET MVC and Web API, We are also developing Android and iOS apps. I believe SonarQube analyses these both as well. Yes you can potentially use both.

Aktiv Grotesk Font Family List. I probably wouldn't. Sonarqube it's nice that you can centrally control your rules. Don't try and manage rules in 2 places.

Especially nice if you have a few solutions. And yes it does have rules for most file types. You can also add most of the Microsoft analysers to it. And plenty of others that might not come out of the box.

Or you can write your own. You would then use sonar lint extension in visual studio to drag down your analysers and rules into your projects and keeps them in sync. As the other post mentioned you can also use resharper for analysis and style control. With lots of other features. Recently put our solution into sonar cube. Huge legacy code base, no common style across the whole thing since it's the result of 15+ years of work. In 2010, we started using code analysis in VS, with a pared down set of code analysis rules for the absolute must-have stuff.

(The default set was giving so many messages it was impossible to find useful things) These found several 'bugs' when we did this, and have helped along the way since then. Yes rule set has grown a bit as we fixed things. So the company wanted all products in one place. I got our TFSBuild to send the data into SonarQube from the daily builds.

Using the default set of rules, Sonar again Reports so many 'Bugs' that its next to in-usable. I went and fixed its top critical reported bugs, but they're not real bugs. Nothing a customer would report. In fact, in one case fixing the issue caused the software to fail in other ways as there were things depending on this broken implementation. So take the 'time to fix' estimate with a grain of salt. I never yet figured out how to send the code coverage from unit tests. In the end, as a developer I don't see much added value of having both tools in play.

Except that I can control the rules applied in one, and not the other (big wigs want common rules applied across all products!) • • • •.