Last week I discovered an annoying Microsoft "feature" on my laptop. After a long holiday and a few Windows updates, Microsoft Word was gone. I could not find the application anywhere and my computer was unwilling to open any *.docx files. A quick Google search showed that I am not alone. But how do I get Word back?
If you persist a DateTime property to SQL Server you lose a tiny bit of precision. For most use cases this will go unnoticed. However, if you try to compare two objects as part of an integration test, your test will fail. Let us look how we can work around the different timer precisions between .Net and SQL Server in Fluent Assertions.
Azure DevOps allows you to add multiple Git repositories to the same project. That allows you to set the permissions only once and organise your code as you like. Sooner than later, you try to add a second backlog and that is where things get complicated. This feature is well hidden and easy to overlook.
If your code works on the Continuous Integration (CI) server but not on your local machine, you may have a problem in the files not tracked by Git. And since Git does not track them, there is no easy way to get rid of them - at least in most Git clients. In such cases, we can go to the command line and use the full feature set of Git to fix the problem.
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 spring cleaning of my computers, I noticed that one device I had nearly no disk space left. After removing old files and the usual suspects (like Windows updates) I found that Docker uses the most space.
While Docker Desktop for Windows showed me a disk usage of around 50 GB, TreeSize found 124 GB - far too much for the few containers that run on this machine. To clean-up the storage, I first tried the prune command to remove unused data:
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.