Every 6 months, Ubuntu releases a new version of its Linux distribution. Since I always forget the command to update my installation, I wrote it down this time. And I added two additional steps you should not miss.
The more complex an application becomes, the greater is the benefit of Docker. If everything runs in containers, we can use a tool like docker-compose and start all the parts with one single command. No need to install all the tools, services, and frameworks - just run docker-compose and the magic happens automatically. We can go from nothing to the full running application in a few minutes.
Since I saw the talk "Dev and Test Agility for your Database with Docker" by Julie Lerman at NDC Oslo 2019 I wanted to port her solution for .Net Core to the .Net Full Framework. How hard could it be? As it turns out, it is an awful lot of work and a few weeks ago Microsoft made it even harder.
As we saw last week, parametrised tests help us to reduce the number of test methods we have to write and still keep the coverage high. However, writing the test parameters multiple times is error prone, especially when it is important that we test all values. Let us look on how NUnit can help us with this problem.
Parametrised tests help you to create many test cases without writing a lot of test methods. This approach saves you a lot of time and increases the quality of your tests. Let us look how we can parametrise our tests in NUnit.
At the user group site, we use GitVersion to turn our git history into a Semantic Version number. After we switched to main as the default branch, our build failed with this error message:
ERROR [****] An unexpected error occurred: System.InvalidOperationException: Could not find a 'develop' or 'master' branch, neither locally nor remotely.
For some posts code is not enough. An animated image that shows the effect of a code snipped helps much more than hundreds words of additional explanation. But how can we create animations like this one I made for the progress bar example?
If you commit a file to a Git repository, it stays there forever. Even when you remove it, Git keeps it around in the .git folder – otherwise you could not go back to a version where this file was part of your project.
In a Linux console we can use the clear command to get rid of all text output in that windows. This is a great help to quickly get an empty terminal without opening another console.
If we try to run the same command in the CMD on Windows, we get an error about a missing command. For a long time, I accepted this behaviour as a lack of functionality in the Windows terminal. However, recently I wondered if I just missed a command and started looking for a solution.
One problem that annoyed me for months was the missing code coverage in our build jobs in Azure DevOps. The metric vanished from one day to another for the .Net 4.x projects. Whatever I tried with the options in the Visual Studio Test task, all I could produce was this link to the Microsoft documentation:
After updating some NuGet packages, one of our .net 4.7.2 projects throw this error when we try to build it:
Error: Your project does not reference ".NETFramework,Version=v4.7.2" framework. Add a reference to ".NETFramework,Version=v4.7.2" in the "TargetFrameworks" property of your project file and then re-run NuGet restore.