Browse .NET Roundups (12)

This week in .NET, Microsoft kept pushing the platform in two directions at once: modernizing long-running enterprise workloads (including mainframe connectivity) while tightening the inner loop for web and client apps with better testing, faster WebAssembly, and more pragmatic API design patterns. That maps cleanly to last week's split between "ship-ready platform updates" and "what's taking shape next." .NET 10 keeps showing up as the standardization point (from Ubuntu 26.04 baselines and container tags to real products migrating runtimes), while .NET 11 previews continue to fill in practical workflow gaps (Blazor UX and testing) before they harden into defaults.

This week in .NET was a mix of platform plumbing and practical building blocks: Microsoft pushed forward on modernizing the toolchain (especially inside Visual Studio), while several posts showed how .NET 10+ apps are increasingly composed from focused libraries for AI, caching, and API surface management. Coming right after last week's split between "install the preview" (.NET 11 Preview 3) and "patch production now" (April 2026 servicing), the throughline is familiar: the platform keeps tightening defaults (dependencies, provenance, project systems), and teams need to validate those shifts early to avoid surprises later. At the same time, a couple of changes signaled where the ecosystem is heading next, including a notable test platform dependency shift that could surface as a breaking change in CI.

This week in .NET was split between "ship-ready platform updates" and "what's taking shape next." Ubuntu 26.04 landed with first-class .NET 10 support out of the box, while the .NET 11 wave continued to fill in long-requested language and tooling gaps (from discriminated unions to more practical scripting). On the app side, the teams kept pushing on real developer pain points: smoother Blazor list virtualization, clearer API docs when versioning is involved, and faster inner loops across containers and MAUI. That split mirrors last week's pattern: alongside "you can try this now" items (like the Fabric ADO.NET preview driver and early .NET 11 Blazor validation direction), we are seeing more places where the platform is either ready to standardize (Linux baselines, container tags) or clearly signaling where core workflows are headed next (Blazor UX primitives, Aspire wiring, language features).

This week's .NET updates split between moving forward and staying current. .NET 11 Preview 3 shipped runtime/SDK/library/framework updates aimed at everyday development, while April 2026 servicing releases delivered security fixes across supported .NET and .NET Framework versions. Building on last week's .NET 11 direction-setting items (like Blazor validation previews), this is another preview step you can install and test, alongside reminders to keep production stacks patched. Microsoft also set a deadline for an "ASP.NET Core on .NET Framework" escape hatch, pushing teams toward modern .NET for web workloads.

This week's .NET updates focused on practical changes: a new way to run Spark SQL from ADO.NET code, early direction on Blazor validation in .NET 11, and a Windows packaging change for PowerShell that will affect machines and build agents. Compared to last week's "what's next" previews, this week is more "here is what you can trial now," plus a policy shift that can impact pipelines.

This week’s .NET items leaned toward "what’s next," with early looks at language features and framework experiments that could change how you model APIs and configure apps. MAUI also clarified how to try new UI ideas without waiting for full releases. This split between stable baselines and previews/experiments continues from last week: alongside GA paths like Aspire on App Service, the .NET 11 Preview 2 thread keeps producing deeper language/runtime experiments, and MAUI is formalizing an "expect churn" lane through an experiments hub.

This week's .NET updates focused on meeting developers where they are: keeping code-first workflows while widening where apps can run. It continues last week's two-track theme: maintain a stable production baseline (PowerShell 7.6 LTS on .NET 10, smoother VS Code Insiders tooling) while trying newer .NET 11 Preview 2 features (like MAUI Maps pin clustering). This week, that split shows up as Aspire getting a supported Azure deployment path and MAUI exploring broader targets via Avalonia's rendering stack.

This week's .NET updates landed where teams feel everyday friction: shells and editors that drive automation and debugging, and UI controls that need to stay responsive under real data. Building on last week's "apply updates" focus (.NET servicing guidance and the macOS VS Code debugger hotfix) plus "try new features" (.NET 11 Preview 2 wave), this week continues the same two-track story: a clearer production baseline for tooling and a Preview 2 feature that is easy to validate in apps.

This week’s .NET updates split into new features to try and updates to apply. .NET 11 Preview 2 added runtime, observability, and web/data updates, while .NET 10/9/8 servicing focused on secure, stable builds plus an out-of-band macOS debugger hotfix for VS Code users.

In Coding this week, major platforms received new updates and improvements. TypeScript 6.0 RC debuted, VS Code expanded support for agent development, and .NET streamlined data and workflow integration. Tutorials and Q&A sessions cover current best practices in productivity and migration.

The Coding section offers guides for in-depth debugging and instrumentation, helping teams diagnose container builds and monitor .NET workloads with minimal overhead.

Coding updates this week highlight new .NET runtime features, expanded agent workflows in VS Code, and community stories in language development and open source. These changes provide more options for reliable code, stronger automation, and better integration in developer tools.