Five dated news digests and five engineering Q&A entries. Each item cites primary documentation or release artifacts (not generic placeholders).
Microsoft’s .NET 9 announcement highlights thousands of performance changes, adaptive Server GC, and new vectorization support for modern CPUs.
Align ASP.NET Core, EF Core, and MAUI package versions with the 9.0 train.
GitHub release notes enumerate assembly version bumps useful when diffing internal forks or trimming self-contained deployments.
Scan for breaking changes in reflection-heavy serializers.
Official download pages list SDK installers and container tags; infrastructure teams should pin digests in Kubernetes manifests.
Validate glibc compatibility on older Linux hosts.
On-demand videos explain how teams adopt .NET 9 features gradually; use them for lunch-and-learn curricula.
Pair videos with hands-on labs from learn.microsoft.com.
The consolidated README in dotnet/core links to workload-specific documents for ASP.NET Core, Windows Desktop, and MAUI.
Track this file across monthly servicing updates.
The .NET 9 blog explains adaptive Server GC tuning based on application memory needs; capture GC metrics before/after upgrading web APIs.
Use dotnet-counters during soak tests.
Bump the shared framework and SDK, restore, fix analyzer warnings, then incrementally update Microsoft.* package versions according to release notes.
Watch for source-generator breaking changes.
ASP.NET Core’s migration docs list behavior changes for routing, authentication, and minimal APIs—read them before deploying to production.
Run smoke tests on OAuth/OIDC flows.
Use dotnet publish -p:PublishTrimmed=true only on supported workloads; diff publish folders and run ILLinker warnings as errors in CI.
Validate reflection-heavy plugins manually.
NativeAOT remains scenario-specific; read dotnet/runtime notes and sample repos before committing serverless cold-start optimizations.
Profile compatibility with serializers and DI containers.