C# on .NET wat we zoeken

Strangling SOAP: migrate to modern .NET without breaking clients

Thu, 20 Nov 2025 11:26:00 +0100

The Strangler Fig pattern is one of those transitional architecture patterns to get to a better system. But strangling SOAP is a bit difficult. If you just put a proxy in front of a SOAP service, you’ll quickly bump into a painful detail: SOAP typically exposes a single HTTP endpoint. All operations share one path, and the actual method is picked using headers like SOAPAction or action and the body contents. That makes the usual reverse‑proxy trick an “all or nothing” mechanism. Not at all a Strangler Fig approach. But there is a way!

Playwright in a single file dotnet app

Fri, 14 Nov 2025 18:43:04 +0100

One of the recent additions in .NET is that you can now have single file projects. In this article we’ll explore how to use Playwright in such file.

TL;DR: Full example at the end of this page.

Why?

More and more I use Playwright not only for testing but also for small automation scripts and to quickly make demos using it’s handy built-in recorder. Before .NET 10 that would required a C# project, a directory with a csproj file a cs file and the Playwright package installed.

Stryker in a CI/CD pipeline

Sat, 10 Feb 2024 12:25:38 +0200

In my last blog I wrote about why mutation testing is a better way of measuring test completeness. I also mentioned the drawback regarding performance.

In this blog I’d like to discuss what Stryker does to increase performance and the things you can do in your pipeline to get the most out of mutations testing every check-in.

What stryker already does

Concurrency

By default Stryker takes half of the available cores to do the work. Use the concurrency to use more or less cores of you system. I tested this on a 8 core machine. When using 4 core the whole process takes 02:42. Whit 8 cores that same process took almost 30 seconds less, 02:18.

Use mutation testing to replace code coverage

Fri, 02 Feb 2024 10:25:45 +0200

It is pretty common to use some sort of code coverage measurement tool along with unit tests to gather feedback on completeness of your test suite. Measuring code coverage is great start to find out if your code needs more testing. But by it’s nature it also comes with some caveats. In this article I’ll explain these caveats and how mutation testing fills these caps and turns out more valuable as a source of feedback.

Simplifying .NET solution upgrades with Directory.Build.props and Directory.Packages.props

Mon, 23 Oct 2023 22:46:34 +0200

With .NET 8 almost released it is time to make upgrading easier. In this blog I’ll explain about Directory.Build.props and Directory.Packages.props and how these can make upgrading easier.

Most solutions consist of multiple projects. Even if all of your production code is in a single project chances are that your tests are in a different project. The separation that projects bring can be great, but sometimes managing dependencies can be a hassle.

Source generation in System.Text.Json, should I care?

Mon, 21 Feb 2022 12:45:04 +0200

With the release of .NET 6 also came the option to use source generation in System.Text.Json. In short this means that instead of runtime reflection some of the work is now done compile time. This makes it more efficient. But how much? And should I care? Just measure it. I made a small project that you can use and adjust to measure the difference for your specific case. Let the results help you decide what’s best for your application.