Your AI-generated monthly roundup of .NET platform updates and community highlights.
Welcome to the April 2026 edition of Pulse on .NET, where we recap the latest updates from Microsoft’s official .NET releases and the broader .NET community over the past month. April was a month of stability and forward momentum: Microsoft patched critical security issues in the current LTS (.NET 10) while pushing ahead with .NET 11 previews, giving developers an early taste of upcoming features. We also saw developer tooling enhancements (with Visual Studio’s big April update and JetBrains’ spring releases) and open-source ecosystem milestones (Avalonia’s next major version and the F# community’s projects). Meanwhile, the community engaged in lively discussions about new C# features and .NET’s evolving focus on AI integration. In this edition, we’ll cover core releases & previews (from servicing patches to .NET 11 Preview 3), the tooling updates across IDEs and CLIs, noteworthy ecosystem developments (open-source frameworks and libraries catching up with .NET 10 and beyond), plus community highlights like blog posts, events, and trends that shaped April. Let’s dive in.
To set the stage, here’s a quick summary of April’s most significant .NET-related updates, grouped by category:
| Category | Update | Release Date | Highlights |
|---|---|---|---|
| Releases | .NET 11 Preview 3 | April 14, 2026 | Third preview of .NET 11 (the next STS release due Nov 2026) [infoq.com]. Brings runtime-level async (no preview flag needed) [infoq.com], JIT optimizations (faster switch, fewer bounds checks) [infoq.com], ASP.NET Core’s new Zstandard compression enabled by default [infoq.com], .NET MAUI improvements (Map control clustering, Android 17 support) [infoq.com], and C# 15 features (e.g. union types) in progress [infoq.com]. |
| Releases | .NET 10.0.6 (Servicing) & 10.0.7 (OOB) | April 14 & 21, 2026 | April Patch Tuesday for .NET 10 LTS fixed 6 CVEs [devblogs.m…rosoft.com] (including RCE and DoS issues) and other non-security fixes. However, a DataProtection regression in 10.0.6 prompted Microsoft to issue an out-of-band 10.0.7 patch a week later [cybersecur…tynews.com], addressing a critical DataProtection vulnerability (CVE-2026-40372) that could corrupt integrity checks and elevate privileges [cybersecur…tynews.com], [cybersecur…tynews.com]. All .NET 10 users were urged to update immediately. (.NET 8/9 also received the April security patches) |
| Tooling | Visual Studio 2026 v18.5 (April Update) | April 14, 2026 | Major update to VS2026 focusing on AI integration and quality. Introduced Copilot “agent skills” (the IDE auto-discovers custom AI skill sets from repos for Copilot agents) and cloud-based agent sessions from within VS [learn.microsoft.com], [learn.microsoft.com]. Also updated JSON editor with latest schema support [learn.microsoft.com] and various performance fixes. Follow-up patches (v18.5.1/.2) fixed minor bugs and included the ASP.NET DataProtection security fix in VS’s components [learn.microsoft.com]. All existing VS 2022 extensions remained compatible. |
| Tooling | JetBrains Rider 2026.1 & ReSharper 2026.1 | Released late Mar 2026 | JetBrains’ Q1 update delivered big changes. ReSharper (the VS extension) is now available as a Visual Studio Code extension [the-runtime.dev], [the-runtime.dev], bringing its deep C# analysis/refactoring to VS Code. Rider 2026.1 added a built-in assembly (ASM) viewer and can run single-file C# scripts without a full project [the-runtime.dev]. Both tools fully support .NET 10 & C# 14 features (like extension members) and improved performance using .NET 10 for ReSharper’s process [the-runtime.dev], [the-runtime.dev]. |
| Ecosystem | Open Source Frameworks & Libraries | April 2026 | The .NET ecosystem saw notable updates. Avalonia UI reached v12.0 (April 28), a major cross-platform UI framework update now aligned with .NET 10 and featuring developer experience improvements (e.g. a new detachable XAML previewer in its VS extension) [en.wikipedia.org], [avaloniaui.net]. The F# community’s Fable compiler (F# to JavaScript transpiler) hit v5.0 [FSWeekly BLOG], enabling modern web development with F#. Many other libraries (e.g. SkiaSharp, Serilog, etc.) published updates to maintain .NET 10 compatibility or adapt to .NET 11 previews. Cloud platforms continued to support .NET 10 fully – Azure Functions .NET 10 support was GA by Q1, and AWS, Docker, and others updated images – so modernization efforts face fewer roadblocks. |
| Community | Content & Blogs | April 2026 | .NET 11 previews sparked analysis and debate. InfoQ summarized Preview 3’s key changes across runtime, ASP.NET, EF, and MAUI [infoq.com], while community bloggers dove into Runtime Async (a new async engine improving performance and debugging) [visualstud…gazine.com]. A new C# 15 feature – collection expression arguments – ignited discussions about language complexity [visualstud…gazine.com], [visualstud…gazine.com], with some devs criticizing it as unnecessary and others defending its convenience. The official .NET Blog demonstrated .NET’s new Agentic AI capabilities via a real app (a “ConferencePulse” assistant built with the AI SDK, Semantic Kernel & Agent Framework) [devblogs.m…rosoft.com], [devblogs.m…rosoft.com], showing how AI can enhance typical .NET applications. |
| Community | Events & Conferences | April 2026 | .NET developers had plenty of gatherings. NDC Sydney 2026 took place April 22–24 [ndcconferences.com], featuring talks on cloud-native .NET, Blazor, and responsibly integrating AI into .NET apps. Local user groups worldwide continued with meetups (many hybrid/online), often sharing experiences with .NET 10 and preview features. Looking ahead, excitement is building for Microsoft Build 2026 in early June – expected to unveil more on .NET 11 – as the community stays actively engaged and prepared for what’s next. |
Table: April 2026’s key .NET updates and highlights, by category (official releases, tooling, ecosystem, community). [devblogs.m…rosoft.com], [cybersecur…tynews.com]
.NET 10 (LTS) remained in focus as Microsoft ensured its stability and security. On April 14 (Patch Tuesday), they released .NET 10.0.6 across the runtime, ASP.NET Core, EF Core, and SDK – a servicing update that packed six security fixes addressing CVEs ranging from denial-of-service to remote code execution. Notably, one fix corrected a potential security feature bypass affecting .NET 8–10 (CVE-2026-26171) and another closed a serious RCE vulnerability (CVE-2026-32178) impacting all modern .NET versions. The patch also included general reliability tweaks, keeping the LTS release robust for production use. However, soon after 10.0.6 rolled out, developers reported issues decrypting ASP.NET Core DataProtection payloads. Upon investigation, the .NET team discovered that a change in 10.0.6 had inadvertently introduced a cryptographic flaw in the DataProtection subsystem. This vulnerability (CVE-2026-40372) could allow malicious tampering with protected data to go undetected – a critical risk given DataProtection secures things like authentication cookies and CSRF tokens. Microsoft responded swiftly: on April 21 they rushed out .NET 10.0.7 as an out-of-band patch, advising all .NET 10 users to update immediately. This quick turnaround (just a week after Patch Tuesday) underscores Microsoft’s commitment to security and stability – even in the era of monthly releases, critical regressions are addressed without delay. Thanks to the emergency fix, .NET 10’s early adopters could continue using LTS with confidence by month’s end. [devblogs.m…rosoft.com] [cybersecur…tynews.com], [cybersecur…tynews.com] [cybersecur…tynews.com]
While .NET 10 was being patched, the next .NET release moved forward. April saw .NET 11 Preview 3 arrive on schedule, marking the third early look at the STS (Standard Term Support) version due in November 2026. With Preview 3, some big features became more mature: the new “Runtime Async” infrastructure no longer requires opt-in with a preview flag, meaning projects targeting .NET 11 can now fully experiment with this new async engine by simply enabling a feature switch. “Runtime Async” shifts part of async/await’s machinery into the runtime itself, promising to boost performance in heavily asynchronous code and yield better debugging (with meaningful stack traces across awaits). Preview 3 also extended support to NativeAOT and ReadyToRun scenarios for runtime-level async, broadening its usage. The .NET JIT (RyuJIT) got further optimizations – InfoQ highlighted things like branchless multi-target switch handling, fewer index bounds checks (especially on C#’s ^ index-from-end syntax), and faster numeric conversions on older x86 CPUs. WebAssembly support advanced too: CoreCLR-on-WASM efforts progressed with support for WebCIL and better debugging symbols, hinting at a faster Blazor WebAssembly in the future. The .NET SDK gained conveniences such as dotnet sln being able to create/edit solution filter files, and a new #include directive for file-scoped C# scripts to improve code sharing. Meanwhile, ASP.NET Core in Preview 3 introduced Zstandard compression (modern high-performance compression) enabled by default for responses, and allowed request decompression of Zstd as well. Web developers also saw improvements in Blazor’s virtualization component (now handling variable item heights smoothly) and a subtle but impactful Kestrel change: starting HTTP/3 request processing sooner to reduce first-request latency. On the data side, Entity Framework Core Preview 3 added a handy GetEntriesForState API to fetch tracked entities by state without forcing a re-scan of changes, and new helpers to more easily swap database providers in tests. For cross-platform UI, .NET MAUI Preview 3 improved its Maps control (with clustering and custom pins), introduced LongPressGestureRecognizer, and began prepping for next-gen mobile OS versions (Android API Level 37, iOS notifications permissions). Rounding things out, this preview also came with an early implementation of C# 15’s “union types” – so intrepid developers can experiment with the new UnionAttribute and IUnion interface for discriminated union-like classes in C#. All told, .NET 11’s development seems on pace, with broad changes across the stack to refine performance, polish new features, and set the stage for more AI integration (the ASP.NET team’s roadmap emphasizes enabling “agentic” web apps by GA). .NET 11 is shaping up as an iterative but significant release, balancing innovative runtime changes with developer feedback along the way. [infoq.com]
Additionally, .NET Framework 4.8.1 – the trusty Windows-only framework – received its own April updates aligning with those CVEs fixed in .NET Core. No new features were added, but the update ensures that desktop and older applications maintain a secure baseline. With April’s patches applied, enterprises can trust that both modern .NET and .NET Framework are fortified against the latest threats. [devblogs.m…rosoft.com]
April’s tooling news showed how the .NET developer experience is rapidly evolving – especially with AI-driven assistance and cross-IDE support.
Visual Studio 2026 received its first major feature update since launch. VS 2026 version 18.5 (“April Update”) arrived mid-month and it carried forward the IDE’s integration with AI coding assistants. This release unveiled deeper integration of GitHub Copilot’s “agentic” features inside Visual Studio: now, Copilot agents can automatically detect and use custom “skills” found in your repository or profile (essentially scriptable recipes guiding the AI on specialized tasks). For example, if your repo contains a .github/skills/ folder with a SKILL.md defining how to run your build pipeline, the Copilot agent will now notice and apply it, making AI suggestions more context-aware. VS 2026 also added a new option to spawn cloud-hosted AI agents directly from the IDE. This leverages cloud resources to run heavy AI tasks – such as having Copilot draft a PR for you – asynchronously in the background while you continue coding. Essentially, Visual Studio is doubling down on AI augmentation as a first-class part of the developer workflow, aiming to boost productivity by letting Copilot handle repetitive or complex tasks via these “agents.” Beyond AI, VS 18.5 included some traditional improvements: an updated JSON editor supporting modern JSON Schema versions (2019-09 and 2020-12) for better IntelliSense and validation, and a variety of bug fixes and performance tune-ups. Impressively, Microsoft managed to maintain backwards compatibility – the update did not break VS2022 extensions or older project types. In the days following the release, two minor patches (18.5.1 and 18.5.2) were issued to address specific bugs (like a strange keyboard input freeze) and also to incorporate the ASP.NET DataProtection fix at the IDE level. By the end of April, Visual Studio 2026 users enjoyed a more intelligent, refined IDE – aligning with Microsoft’s vision of an AI-powered developer environment that still feels stable and familiar. [learn.microsoft.com], [learn.microsoft.com] [learn.microsoft.com]
JetBrains also shook things up with its 2026.1 release across the .NET tool suite (officially shipped March 30, but effectively new for April). This was a substantive update bridging the gap between different development workflows. The headline was that ReSharper 2026.1 – JetBrains’ famed refactoring and analysis tool – now runs in VS Code. After months in preview, JetBrains published ReSharper as a Visual Studio Code extension, marking a historic broadening of their reach. .NET developers who favor VS Code can now leverage ReSharper’s deep static analysis, context-aware suggestions, and powerful refactorings directly in that lightweight editor. The VS Code extension isn’t watered down either: it provides solution-wide analysis, navigation (with decompilation), and integrated test runner support for NUnit/xUnit, among other features. Essentially, JetBrains decoupled ReSharper from full Visual Studio and gave .NET coders on any platform (Windows, Mac, Linux) something beyond what the free C# Dev Kit offers – albeit licensing applies for commercial use. Meanwhile, the standalone Rider 2026.1 IDE also got noteworthy enhancements: it can now open and run a single .cs file without requiring a full project or solution (great for quick scripts or experiments) and introduced a built-in assembly (IL) viewer so developers can inspect JIT-compiled output or decompiled code more easily. Both Rider and ReSharper improved their support for the latest C# features – for example, they handle C# 14’s extension members gracefully now (navigation and auto-import suggestions work with extension properties/methods defined via extension syntax). JetBrains also continued performance work: ReSharper’s out-of-process mode (which isolates it from VS to reduce slowdowns) saw over 70 bug fixes and now runs on .NET 10 runtime for speed gains. The presence of .NET 10’s JIT in ReSharper’s process improved indexing and code completion times, particularly in large solutions. Together, these changes from JetBrains demonstrate a convergence in .NET tooling: VS Code is now a viable environment for advanced .NET development with enterprise-grade analysis (thanks to ReSharper), and traditional VS + ReSharper users see performance catching up to Rider’s levels. With Microsoft and JetBrains both pushing AI integration and cross-platform flexibility, .NET developers have a richer set of tools than ever going into the rest of 2026. [the-runtime.dev], [the-runtime.dev] [the-runtime.dev]
On other tooling fronts, Lightweight editors and CLI tools remain strong. The Visual Studio Code C# extension (powered by the open-source Roslyn-based language server) was already in good shape for .NET 10, and incremental updates in April focused on stability. The .NET CLI itself got some love in .NET 11 previews (like environment variable passing in dotnet run and better dotnet watch resilience), which developers using command-line workflows can test out. In build and DevOps tooling: Azure DevOps quietly kept up, adding recognition for VS2026’s solution filter files and making sure hosted build agents had .NET 10.0.6 by mid-month. And PowerShell 7.6, built on .NET 10, hit General Availability in March, meaning April was the first full month with the new LTS of PowerShell available – it brings enhancements like parallel pipelining and usage of .NET 10’s GC improvements, which may benefit automation scripts (a niche but relevant part of the .NET family). [infoq.com]
Beyond Microsoft’s core products, the open-source .NET ecosystem continued to innovate and align with the latest platform updates. In April, we saw a mix of major releases and community-driven advancements.
One significant milestone: the Avalonia UI framework released Avalonia v12.0 (finalizing its next-gen release) towards the end of April. Avalonia is a popular open-source, cross-platform XAML UI framework (a modern alternative to WPF) that’s widely used for building desktop applications on .NET. Version 12.0 cements Avalonia’s full .NET 10 compatibility and brings improvements both under the hood and for developer productivity. On the tooling side, Avalonia’s April update was accompanied by a new Visual Studio extension (Avalonia for VS 12.0) that offers a detachable XAML preview window for designing UI, configurable color schemes, and an experimental improved XAML previewer for faster feedback. This signals Avalonia’s maturity in providing a polished dev experience comparable to WinForms/WPF designers of old. For developers, Avalonia 12 also refined many controls and performance aspects, continuing to make cross-platform .NET GUI development smoother. It’s encouraging to see such community-driven frameworks keep pace with .NET’s evolution – developers targeting Avalonia can now confidently use .NET 10, and even try .NET 11 previews, knowing the framework is up to date. [en.wikipedia.org] [avaloniaui.net], [avaloniaui.net]
In the web and cloud space, ASP.NET Core features delivered in .NET 10 are being actively adopted. April’s blogosphere saw tutorials on things like the new Server-Sent Events support in ASP.NET Core 10 (using TypedResults.ServerSentEvents), and on enabling passkey authentication with minimal code changes in .NET 10’s Identity libraries – reflecting ongoing excitement about these features. Also, while not an April release per se, it’s worth noting that Azure Functions support for .NET 10 reached general availability in late February 2026. By April, many cloud developers were starting to migrate serverless functions to .NET 10 LTS, gaining performance and language enhancements. With AWS having enabled .NET 10 in services like Lambda (as of early January) and even releasing its Transform modernization tool in late 2025, all major clouds are on board. This means the ecosystem – from on-premises frameworks to cloud services – is broadly aligned on .NET 10, which in turn accelerates broader adoption.
In cross-platform and mobile news, the Uno Platform (a framework for building native apps with C# and XAML) was already on Uno 6.4 with .NET 10 support since last November. In April, the Uno community was quietly preparing for Uno 6.5 (which had service releases by February) and a likely Uno 7 preview later this year, focusing on even tighter integration with AI features (Uno’s earlier release teased an “Agentic Development” model for generating UI via AI). The Xamarin successor, .NET MAUI, didn’t have a standalone release in April (its next update likely coinciding with .NET 11 previews in coming months), but the community did continue to fill gaps – e.g., plugin libraries adding features, or developers using MAUI Community Toolkit contributions to enhance .NET’s official cross-platform UI.
The F# ecosystem had a highlight this month as well: Fable 5.0 was released. Fable is an F# to JavaScript transpiler that allows F# developers to write web front-end code. The F# Weekly newsletter celebrated Fable 5.0 in late April, noting improvements like better integration with npm toolchains and support for the latest F# language features. The new version makes it easier to share code between server (in .NET) and client (via Fable) – an approach valued by those building end-to-end F# solutions. This release underscores that while C# often dominates .NET news, the F# community is active and pushing boundaries in its niche (functional programming, web front-ends, data science). On a related note, other F# tooling saw updates too: e.g., SwaggerProvider 4.0 (for type-safe OpenAPI client generation in F#) entered beta, and the Akkling library (F# API for the Akka.NET actor model) got a mention in early April for new contributions, showing that F# is keeping pace with .NET improvements. [FSWeekly BLOG]
Finally, microservices and distributed systems remain a buzzing area in .NET. Projects like Dapr were gearing up for new releases (Dapr v1.18 was in release-candidate stage by early May), likely bringing enhancements for running .NET services with ease. Orleans, Microsoft’s distributed actor framework, had reached v10.0 in late 2025 – by April, developers continued to explore Orleans for building cloud-scale .NET apps, often discussing how .NET 10’s performance gains benefit such scenarios. No new Orleans version shipped this month, but interest remains high thanks to the cloud-native trend. Meanwhile, security and devops considerations in open-source .NET got some attention: a few .NET libraries adopted supply-chain security measures (like signing with Sigstore), and blog posts reminded maintainers how to handle security patches – quiet yet important progress for the ecosystem’s resilience.
In summary, April’s ecosystem news shows broad engagement with .NET 10 and anticipation for .NET 11. Established frameworks are up-to-date, niche tools like Fable demonstrate diversity in .NET usage, and the community is busy integrating the new capabilities (AI, performance enhancements, etc.) into their own projects. The .NET ecosystem’s momentum continues strong into 2026.
The .NET developer community was active and vocal in April, producing rich content and engaging in thoughtful debates. With new tech like .NET 11 previews and AI integration on the horizon, community members took to blogs, forums, and conferences to share knowledge and opinions.
📝 Top Blog Posts & Tutorials – A wave of content came out to clarify .NET 11’s emerging features and help developers get the most out of .NET 10:
🎙️ Events, Meetups & Community Buzz – April kept community energy high:
Closing Thoughts: April 2026 was a microcosm of the .NET ecosystem in motion – secure and stable in the present, ambitious about the future. The community is digesting .NET 10’s benefits while also influencing .NET 11’s direction through feedback. There’s a clear excitement about performance gains, new language features, and the prospect of AI-enhanced development – albeit paired with healthy debates on complexity and focus. With major gatherings like Build 2026 on the horizon and .NET 11’s previews accelerating, the coming months promise even more news and innovation. We’ll be here to continue capturing the pulse of the .NET world. Until next time, happy coding! [infoq.com], [visualstud…gazine.com]