SonarQube has a collection of rules to analyze your source code at compile time to identify potential vulnerabilities, bugs, anti-patterns, refactoring and poor coding practices. The earlier we identify issues, the easier and cheaper it is to address them. By leveraging the power of Static Code Analysis, developers can get an early feedback for their code changes.
If you are trying to install SonarQube in your project or planning to upgrade it to a newer version, you might have bumped into multiple issues during the setup process. In this article, I will show you how you can display the Code Coverage Results in SonarQube and troubleshoot any issues related with the same.
The SonarQube Scanner for MSBuild – Begin Analysis task contacts the SonarQube server to retrieve the quality profile, and dynamically produces rulesets to be applied during the static analysis. If there are issues in the process, I would recommend to go the Administration section in your SonarQube server, and navigate to the background Tasks tab to find the error log.
I have my SonarQube server up and running. I added a SonarQube Service endpoint and associated it while configuring the SonarQube Begin analysis task.
However when I trigger the build, it failed throwing the below error – ‘Unhandled Exception: System.IO.InvalidDataException: End of Central Directory record could not be found.’
I started seeing a weird issue while working in Visual Studio 2017 few days back. I was not able to attach to running processes with the Visual Studio debugger. The IDE used to freeze/hung each time I tried to do so. The ‘Attach to Process’ window used to come up but it was blank and all I saw was the spinner – eventually the screen became unresponsive after some time.
One of the coolest feature in Visual Studio 2017 is the ‘Lightweight Solution Load’ which greatly reduces the Visual Studio startup time and the overall memory consumption.
However I have bumped into multiple issues working with Lightweight Solution Load feature turned ON in VS2017. In this article, I will list down few of my observations, so that you are aware of these limitations.
Visual Studio 2017 comes with a lot of new capabilities and productivity enhancements. This was good enough reason to start moving from VS 2015 to VS 2017, and leveraging all the new features. In this blog post, I will mention about couple of issues which I bumped into during the migration process and the action items I took to resolve those.