This site (and blog) has recently been moved from WordPress to a Hugo-based site hosted on GitHub. The new setup is powered by Markdown, allowing for a simpler and more flexible content management process.

Please note that the site is still a work in progress. I’m actively working to refine the design, migrate content, and add new features. Some pages may be incomplete or missing temporarily, so thank you for your patience during this transition.

Feel free to explore and check back often for updates. Your feedback is always welcome!

Recent Archives

Moving to SDK-Style projects and package references in Visual Studio, part 2

Introduction

The SDK style projects are the new format that first appeared for .net core, but actually can be used also for nearly any type of projects in the .net world. The old style, or what we could call legacy style, is a very complex style, and it is not uncommon to be the cause of merging issues, and also can cause all sorts of weird behavior. Both styles for a C# project has the extension csproj, even if their content is so different.

read more

New version of the NUnit 2 adapter supporting Visual Studio 2019

The NUnit 2.X framework have been superseded by the NUnit 3 framework several years ago. Each framework "family" needs a separate adapter, one for the V2 and one for the V3. The V3 have been maintained continuously, and have 3-4 releases per year. The V2 adapter however, has not been updated since mid 2017.

The thinking have been that developers should move to the V3 version of the framework. Over time that has happened, but there are still some that need the V2 version for various reasons. Although the V3 framework is an enhancement of V2, there are some breaking changes between them. And for some systems those prevents upgrading.

read more

Moving to SDK-Style projects and package references in Visual Studio, part 1

Background

With the introduction of .NET core some time back, Visual Studio got two different project systems. Along with this, we also got two different formats for a 'csproj' file. The new format have a better way of including packages, called PackageReference. This also made its way into the old style format, and greatly simplifies the csproj file with respect to including nuget packages.

Naming

These formats have not really had any proper naming, but over time the following names have appeared:

The new format: SDK-Style format seems to be in favor, although Lightweight format is also used.

read more

More

How to find the best gitignore for Visual Studio and Azure DevOps

A story on working with NUnit backward compatibility, and dependencies

How to convert NUnit Assert.AreEqual to fluent Assert.That syntax easily

How to extend the NUnit constraints

All Archives