Few months back, Microsoft acquired GitHub and we expected to see some interesting collaboration following the acquisition. It was not a long wait and we saw a number of announcements made by Microsoft recently which includes its collaboration with GitHub…. Read More ›
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.
Visual Studio 2017 now includes Redgate Tools to increase productivity while doing database development work. I use the VS Enterprise edition at work, so am pretty excited to leverage the productivity benefits of these tools, within Visual Studio IDE itself.
The Find All References feature has been upgraded in Visual Studio 2017 and looks much better now – both visually and from a functionality perspective.
Database Unit Test project seems to not build in Visual Studio 2017. In this article, I will show how to handle this error, and get your database unit tests back to a running green state.
Are you tired of the sluggish performance, frequent IDE crashes, high memory consumption and slow solution load time of Visual Studio IDE? Read this article to find out how to overcome these pain points with Visual Studio 2017.
When you have a large solution comprising of multiple projects, you must have experienced a delay while loading the solution for the first 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. In this article, we will understand all the details around this new feature.
A year back on this very day, I decided to start my own blog and that’s how dotnetvibes.com came into existence. Today on 1st January, 2017 – exactly a year later – I must admit that it has been an eventful journey with lot of excitement, learning, challenges and acquaintances.
With the initial release of Visual Studio 2017 RC, there were multiple issues reported related to Windows Workflow Foundation in the VS Developer Community site . The latest update to VS 2017 RC however has a great news for Workflow Foundation users.
In the recently concluded Microsoft Connect 2016 Conference, Microsoft made a number of big announcements. One of them was the availability of the next version of Visual Studio -Visual Studio 2017 Release Candidate. In this article, I will be explaining the new installation experience with Visual Studio 2017.
Static Code Analysis has been present in Visual Studio IDE since the earlier versions, and has been evolving with each release. In this article, we will look at few usability issues of the Code Analysis in Visual Studio 2013 and how it… Read More ›
The importance of Code Quality has grown multi fold times over the past few years. Gone are the days, when meeting deadlines used to be the sole measure of success. In today’s world, just delivering code is not enough –… Read More ›
In this blog, we will look at a very cool Visual Studio 2015 extension called ‘CodeLens Code Health Indicator’ and its features. This extension shows the current value of the Maintainability Index for our code and provides us insight into… Read More ›
In this blog, we will try to understand the importance of code reviews, classify types of design flaws and identify the code smells using Visual Studio Code Metrics. Why is Code Review important? In a development life cycle, Code Reviews… Read More ›