richlander

.NET Release Verification Report

• Date: 2026-04-14
• Tool: release-notes 1.0.1
• Command: dotnet run --project src/Dotnet.Release.Tools -- verify releases /Users/rich/git/core/release-notes --skip-hash
• Exit code: 2

Summary

| Version | Latest release | URLs checked | CDN mismatches | aka.ms mismatches | Result |

richlander

.NET Release Verification Report

• Date: 2026-04-14
• Tool: local Dotnet.Release.Tools build from ~/git/dotnet-release
• Command: dotnet run --project src/Dotnet.Release.Tools -- verify releases /Users/rich/git/core/release-notes --skip-hash
• Exit code: 2

Outcome

The updated verifier no longer reports false SDK feature-band failures for .NET 9.0 and .NET 8.0. The remaining issues are limited to unresolved .NET 11.0 preview aka.ms redirects and .NET 10.0 CDN/aka.ms drift.

richlander

.NET Container images: whoami

We have had two relevant practices for the container images we publish:

• Don't change the user.
• Don't add users.

You can see that with our .NET 7 container images.

richlander

Updating .NET Linux Build

.NET Core started out life as a cross-platform project. We naturally wanted to encourage usage on Linux. Across the first couple versions, we figured out how to build a single set of binaries that worked everywhere (e.g. for Linux x64). A key design point of that project was building on an old Linux so that our choice of build OS didn’t unnecessarily limit where .NET apps could be run. That has worked well, using CentOS 7, but it will soon go out of support. There isn't an obvious replacement for CentOS 7, requiring us to adopt a new approach.

We intend to use a combination of Mariner and a streamlined copy of Ubuntu going forward.

Breadth Targeting

The primary aspect of breadth targeting on Linux is linking with the C standard library (libc). Native code (like the .NET runtime) is compiled with a given libc and then is only able to run on distros with a libc version at le

richlander

Playing with .NET 8 Containers

We just shipped a cool new scenario for .NET, which is making it really easy to run .NET 8 container images as a non-root user.

Friends don't let friends run as root

We should all get T-Shirts that say that.

Let's take a quick look using our favourite aspnetapp sample. I'm going to use WSL. I'll show you everthing I do. I use the patterns that are easiest for me, which might not be the same for you.

richlander

FROM alpine

ARG TARGETPLATFORM
ARG TARGETOS
ARG TARGETARCH
ARG TARGETVARIANT
ARG BUILDPLATFORM
ARG BUILDOS
ARG BUILDARCH
ARG BUILDVARIANT

richlander

const string Bar = "Bar";
const string DoubleBar = $"{Bar}_{Bar}";

WriteLine(DoubleBar);

richlander

.NET 6 Examples

• Record structs
• Readonly record structs
• Extended property patterns
• const interpolated string

Note: See .NET 5 examples

richlander

<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>net6.0</TargetFramework>
    <ImplicitUsings>enable</ImplicitUsings>
    <Nullable>enable</Nullable>
  </PropertyGroup>

</Project>

richlander

Battery battery = new("CR2032", 0.235, 100);

WriteLine(battery);

while (battery.RemainingCapacityPercentage > 0)
{
    Battery updatedBattery = battery with {RemainingCapacityPercentage = battery.RemainingCapacityPercentage - 1};
    battery = updatedBattery;
}