Staying Current with .NET
A practical series about making .NET upgrades routine by first understanding, controlling, and reproducing the build environment, then continuously evaluating new releases before they become urgent.
.NET 11 RC1 Is Here. Is Your Upgrade Process Ready?
With .NET 8 and .NET 9 nearing end of support, .NET 11 RC1 is a good time to rethink framework upgrades as a continuous evaluation process instead of an EOS-driven project.
Before You Upgrade .NET, Do You Know What Is Building It?
Before .NET upgrades can become routine, you need to know which SDK is actually building your application, whether that choice is intentional, and whether the environment can be reproduced.
Can You Build Your .NET Application on a Clean Machine?
A clean-machine test can expose the tools, package sources, services, configuration, and developer knowledge your .NET repository depends on but does not declare.
How to Test a New .NET SDK Without Installing It System-Wide
Install a newer .NET SDK in isolation so you can use newer development tooling to evaluate an existing application before changing the SDK installation your normal development environment depends on.
Managing .NET SDKs: Installation Was Just the Beginning
How Isolated .NET SDK evolved from a simple installer wrapper into a tool for managing, verifying, and auditing SDK installations.
Modernizing .NET: Establishing and Verifying Code Style with EditorConfig
Configure EditorConfig for .NET Framework 4.8 and verify naming rules with Visual Studio, IDE1006, and dotnet format—without migrating projects.
Modernizing .NET: Take Control of NuGet Package Sources
Learn to control NuGet package sources in .NET Framework projects. Verify inherited feeds, disabled sources, and restore behavior using real CI tests.
.NET 11 Is Here. .NET 8 and .NET 9 Are Out of Support.
.NET 11 launches as .NET 8 and 9 reach end of support. Review final servicing updates for .NET 8, 9, and 10, security fixes, and upgrade choices.