Blog

December 5, 2017
in Data Analysis
5 min read

How LOC is computed in SonarQube, NDepend and Visual Studio

Lines of Code (short LOC) are an often used metric to compare projects by their size. All you need to do is to count the lines of source code to figure out if project A is bigger than project B. However, that is only true when they use the same programming language. Only then can you do the same work in a line of code. If you compare Ruby with C or Assembler your LOC metric may differ by many orders of magnitude to get the same things done.

November 30, 2017
in Data Analysis
3 min read

Fine-tune the Collection of your SonarQube Projects

The SonarQube scanner is a simple way to start gathering data on your project. However, the scanner doesn’t know much about project structures and conventions for programming languages. Those things are all included in the build integration, which will be the topic of a later post.

November 28, 2017
in Data Analysis
4 min read

Start Analysing Code with SonarQube

With SonarQube in place and the first project run through the scanner, we are now ready for the interesting part: Analysing our project.

November 23, 2017
in Data Analysis
3 min read

Collecting Data on your Projects with SonarQube Scanner

As soon as your SonarQube installation is working, you are ready for the next step. To analyse code with SonarQube is simple, but again you need to know where you have to start.

November 21, 2017
in Data Analysis
5 min read

SonarQube: Installation Walkthrough for Windows and SQL Server Express

The installation of SonarQube is well documented and easy to follow. However, SQL Server Express brings its own challenges. There are some configuration changes you must make or SonarQube will not work. This installation walkthrough will address those issues and help you to overcome them.

November 14, 2017
in Testing
4 min read

SpecFlow+ Installation Walkthrough

The "Given, When, Then" syntax of behaviour-driven development (short BDD) is a great way to get the business involved in the software development process. SpecFlow allows you to use this kind of example based specification with your .Net projects. Unfortunately, there are two obstacles that make the installation of SpecFlow and its commercial extension SpecFlow+ a challenge. This post will guide you through the installation process and help you to overcome those obstacles.

November 7, 2017
in Data Storage
2 min read

Paged Results in SQL Server

A common requirement for applications is to display a list – that can range from products to search results. While showing all entries works for small lists, it is not that useful for lists with hundreds of entries. In this case you should use paging and only show 10 or 20 entries at a time. The user sees the first part of entries and then can switch to the next page of the list to get more entries. This approach is faster, reduces the workload on your systems and the user isn’t drowning in data. Let’s look how you can implement paging in applications that use SQL Server.

October 31, 2017
in Coding Practice, Data Storage
2 min read

Reading Configuration Files in C

A common task for developers is to store application specific configuration. There are many ways you can take to get that functionality. If you use .Net / C# you can use the simple, built-in way to work with configuration files. Let’s look how this works.

October 24, 2017
in Coding Practice, Testing
3 min read

Upgrade NUnit from Version 2.x to 3.8

We started the migration to NUnit 3.0 as soon as the final version was released. Unfortunately, some bugs on Visual Studio Team Services ended this endeavour rather suddenly. We concentrated on shipping our product and postponed the upgrade. Now, with all our projects migrated, it is time to look back on the breaking changes that took the most time to upgrade.

October 17, 2017
in Coding Practice
2 min read

Little Git Tricks: How many Commits are in a Branch?

Certain questions about a project can only be found in the source repository. The commit messages contain details on how your code was developed that you probably nowhere else have documented. The same is true if you want to know how many commits where made in a branch.