Msbuild on Strathweb. A free flowing tech monologue.

Enforcing C# EditorConfig formatting conventions at build time

Sun, 26 Jan 2020 07:40:29 +0000

EditorConfig is an excellent way to enforce stylistic rules on your C# projects. However, the rules and their corresponding IDExxxx diagnostics are only enforced in the editor, such as Visual Studio or VS Code with OmniSharp, but not at build time.

While there are various categories of EditorConfig conventions that you can use, in this post, I will show you how to enforce the formatting conventions (IDE0055) at build time.

Solution-wide Nuget package version handling with MsBuild 15+

Fri, 20 Jul 2018 13:04:06 +0000

Last year I blogged about a way to handle NuGet package versions at the solution level for .NET SDK-based csproj project files (so those using entries to define their NuGet dependencies).

That approach worked reasonably well, but was entirely custom - as it simply relied on defining reusable MsBuild properties to handled the versions, which created a bit of overhead.

With MsBuild 15 and newer, you can actually do it in a much more elegant way. Let’s have a look.

Solution-wide Nuget package handling in .NET SDK-based projects

Fri, 29 Sep 2017 08:25:21 +0000

In this blog post I’d like to show you a very simple technique for ensuring all your Nuget packages across all the projects in a solution have the same version. Such package management improvement introduced recently into the OmniSharp code by one and only Dustin Campbell, and I’ve also been using it in some of my projects.

If your solution is built around .NET SDK csproj projects, which were introduced in Visual Studio 2017, hopefully this blog post will be useful to you.