News

.NET 11 Previews Focus on Nuts-and-Bolts Coding -- AI Not So Much

• By David Ramel
• 04/20/2026

Remember when you had to really dig in and concentrate and understand exactly how C# and other code worked at the most basic levels?

With the software development space still obsessing over "vibe coding" and other manifestations of AI, Microsoft is focusing more on the nuts-and-bots coding in its early previews of .NET 11.

.NET 11 is expected in November 2026, and public statements from Mads Kristensen at VSLive! indicate Visual Studio 2027 is expected then as well, likely as an in-place update to Visual Studio 2026 rather than a separate side-by-side release (see "At VSLive!, Mads Kristensen Lets 'the Cat out of the Bag' on Visual Studio 2027").

.NET 11's first three preview releases suggest a different emphasis from the one Microsoft used to open the .NET 9 cycle, where it said its "most important focus areas are cloud-native and intelligent app development." The early .NET 11 announcements are centered instead on core runtime, SDK, web framework and language work. For developers following Microsoft's monthly preview cadence, that makes .NET 11 look less like an AI-forward release story and more like a return to the platform's traditional bedrock engineering priorities.

That does not mean AI has disappeared from the broader .NET ecosystem. Microsoft continues to publish separate AI-focused material for .NET developers, and the company has tied AI-adjacent capabilities such as Copilot and related tooling to other parts of its developer stack. But in the official preview announcements for .NET 11 Preview 1, Preview 2 and Preview 3, AI is not the organizing theme. The recurring structure is familiar: runtime changes, SDK and CLI work, libraries, ASP.NET Core, Blazor, .NET MAUI and C# improvements.

For Visual Studio Magazine readers, that change in emphasis is arguably the point. As earlier coverage of .NET 11 Preview 1 noted, the new release cycle opened with a mix of technical groundwork and muted enthusiasm in some corners of the developer community (see Devs Souring on .NET 11?). Preview 2 (March) and Preview 3 (April) continue that practical pattern. They add useful functionality, but they do so mostly through the kind of coding, debugging, build and framework improvements that working .NET developers feel in daily use rather than through a marquee AI headline.

Likewise, reader reaction to the first three .NET 11 previews has been practical rather than AI-focused. In the Preview 1 comment thread, the sharpest discussion centered on language complexity, with several developers questioning whether new C# syntax such as collection expression arguments adds enough value to justify more cognitive overhead, while others defended the feature as useful in narrower scenarios. Other commenters asked basic adoption questions about how to try specific Preview 1 features, suggesting curiosity was present but not necessarily broad excitement.

By Preview 2 and Preview 3, the tone shifted even more toward operational friction. Commenters flagged documentation lag, said some linked material was not ready when the posts went live, and raised recurring complaints that Azure Pipelines, hosted build agents and Visual Studio infrastructure still trail the pace of Microsoft's yearly .NET releases. One especially telling Preview 3 comment captured that mood bluntly: "How about MS slow down and get the entire infrastructure updated before worrying about NET vNext?" Taken together, coder concern seems focused on language churn, tooling readiness and the real-world cost of keeping up.

Arguably, the most important single new concept to emerge from Preview 2 and Preview 3 is C# 15 union types. Microsoft documents union types as a way to represent values that can be one of several case types, with support for implicit conversions and exhaustive switch checking. For developers who routinely model alternative results, domain events, command outcomes, API responses or state transitions, that can make code more expressive and safer at compile time, without having to fall back as often on inheritance hierarchies, loosely typed containers or custom discriminated-union patterns built by hand.

Union types matter because they are bigger than a point improvement to one framework or one CLI command. They affect how developers model data and reason about correctness across desktop, web, cloud and service applications. Microsoft says the feature first appeared in the .NET 11 preview line and that later previews include the runtime support needed for the related types, making Preview 3 a more visible point in the rollout.

Beyond union types, the rest of the .NET 11 Preview 1 through Preview 3 story reads like a steadily growing inventory of foundational improvements:

• Runtime Async: Microsoft has continued building out Runtime Async across the early .NET 11 cycle, and its runtime documentation says that starting with Preview 3, a net11.0 project no longer needs EnablePreviewFeatures to use it. That lowers friction for developers evaluating the feature and signals a step toward more normal experimentation in real codebases.

• Updated Hardware Baselines: The .NET 11 runtime documentation says Microsoft has updated minimum hardware requirements to require more modern instruction sets on x86/x64 and Arm64. This is not a flashy feature, but it is the kind of platform-level decision that can matter to enterprise deployment planning, compatibility testing and performance assumptions.

• JIT and Performance Work: Preview 2 and Preview 3 continue JIT and runtime optimization work, including more bounds-check elimination and other low-level improvements. These changes are typical of .NET preview cycles, but they remain important because they affect application performance without requiring developers to rewrite code.

• Smaller SDK Installers: Preview 2 introduced smaller installers on Linux and macOS through assembly deduplication. For teams that regularly provision dev environments, build agents or containers, reduced SDK footprint is a practical quality-of-life gain.

• Solution Filter CLI Support: Microsoft added support for creating and editing solution filters from the dotnet sln command line. That is especially relevant for large repositories and enterprise teams that need to work on subsets of projects without loading or building an entire solution.

• dotnet run -e: Preview 3 adds a new dotnet run -e option for passing environment variables directly from the command line. It is a small feature on paper, but it simplifies common testing and launch scenarios and reduces reliance on shell state or profile edits.

• dotnet watch Improvements: Microsoft's SDK documentation for Preview 3 highlights better support for Aspire app hosts, automatic crash recovery and improved Ctrl+C handling for Windows desktop applications. These are workflow-oriented changes that could matter more in practice than they do in a feature summary.

• System.Text.Json and Compression Updates: The .NET 11 overview highlights additional JSON controls, Zstandard support in System.IO.Compression and CRC32 validation for ZIP reads. These are plumbing features, but they touch common application concerns around serialization, packaging and I/O.

• Native OpenTelemetry Tracing in ASP.NET Core: Preview 2 adds built-in OpenTelemetry semantic convention attributes to ASP.NET Core HTTP server activity, according to Microsoft. That is significant for teams standardizing observability because it reduces the need for extra instrumentation to get useful tracing data.

• Blazor Static SSR TempData Support: Microsoft says Preview 2 adds TempData support for Blazor static server-side rendering. For developers building hybrid or server-rendered experiences, that gives them another familiar state-passing mechanism in the Blazor stack.

• OpenAPI 3.2.0 and Blazor Web Worker Template: Preview 2 also brings OpenAPI 3.2.0 support and a Blazor Web Worker project template. Those additions are not likely to outshine union types, but they expand the practical surface area for API and client-side experimentation.

• ASP.NET Core Zstandard Support: Preview 3 adds Zstandard response compression and request decompression in ASP.NET Core, with zstd enabled by default in the related middleware. That is one of the more concrete web-stack additions for developers focused on throughput and payload efficiency.

• Virtualize Improvements: Microsoft updated the Blazor Virtualize component so it can adapt to variable-height items at runtime. That should help developers avoid spacing and scrolling issues in real-world UI lists that do not fit a uniform-height assumption.

• Earlier HTTP/3 Request Processing in Kestrel: Preview 3 lets Kestrel begin HTTP/3 request processing without first waiting for the control stream and SETTINGS frame. This is a deeply technical change, but it targets first-request latency on new connections and reflects the kind of transport-level tuning that often accumulates quietly in preview releases.

• Windows Desktop Notes Remain Light: The official materials say Windows Forms has no notable updates in these previews, while WPF changes are mostly quality improvements and fixes. For desktop-focused VSM readers, that means the most meaningful action in early .NET 11 is happening elsewhere in the stack.