Top 8 .NET Trends in 2026: What CTOs Should Plan For

What is .NET in 2026?

.NET is Microsoft's free, open-source developer platform for building web applications, APIs, cloud services, desktop and mobile apps, games and IoT software. You write .NET code mostly in C#, with F# and Visual Basic also supported, and run it on Windows, Linux and macOS.

The name covers two related products, and the difference matters for planning:

• .NET Framework is the original, Windows-only platform that appeared in the early 2000s. Its last major version is 4.8, with 4.8.1 as the latest release. It still receives security and reliability fixes as a component of Windows, but no new features.
• .NET (previously .NET Core) is the cross-platform successor. In May 2019 Microsoft stated in ".NET Core is the Future of .NET" that new applications should be built on it and that .NET Framework 4.8 would be the last major version of the old platform. Since then, one product simply called .NET ships every November.

The .NET Framework lifecycle page shows how long the old line lingers: 4.8 and 4.8.1 have no end date because they follow the Windows component policy, while .NET Framework 4.6.2 retires on January 12, 2027. So the practical picture in most companies is two worlds side by side: modern .NET services on Linux containers and older .NET Framework applications (Web Forms, WCF services, classic ASP.NET MVC) that nobody wants to touch.

Our .NET developers work in both worlds every week, and most of the trends below are really about moving safely from the second world to the first.

Is .NET still relevant in 2026?

Yes, and the data says so without any marketing help. In the 2025 Stack Overflow Developer Survey, 27.8% of all respondents had used C# in the past year. Among web frameworks, ASP.NET Core was used by 19.7% and classic ASP.NET by 14.2%, with Blazor at 7%. For comparison, Node.js stood at 48.7% and React at 44.7%. .NET is not the most common web stack, but it is one of the largest and most stable, and it is heavily used for business back ends where long life and predictable upgrades matter more than fashion.

The cloud numbers point the same way. Market research firm SRG reported on July 30, 2026 that cloud infrastructure services reached about $143.4 billion in the second quarter of 2026, with Amazon at 28%, Microsoft at 20% and Google at 15% of the worldwide market. Azure is the natural home for many .NET workloads, although modern .NET runs just as well in Linux containers on any cloud.

The release rhythm is also predictable, which is underrated. A new major version ships every November, and releases alternate between Long Term Support (three years) and Standard Term Support (two years), as described in Microsoft's releases and support guide. You can plan upgrade budgets years ahead, which is harder with ecosystems that move on a less regular schedule.

We see this in our own work. More than a dozen of our published case studies run on .NET, from construction platforms in Germany and Switzerland to an accounting product in Ireland and a fintech desktop framework in the United States. If you are weighing .NET against JavaScript on the server, our comparison of Node.js and .NET Core covers the trade-offs.

Where is .NET used?

The range of products built on .NET is wide. These are the areas where we see it most often in 2026.

Web applications and APIs

ASP.NET Core is the main reason companies choose .NET today. It covers REST and gRPC APIs, minimal APIs for small services, Razor Pages and MVC for server-rendered sites, and Blazor for interactive web UI in C#. Large multi-tenant SaaS platforms, internal portals and public e-commerce back ends all fit here.

Desktop applications

Windows desktop software is still a big .NET niche, especially in finance, engineering and manufacturing. WPF and Windows Forms both run on modern .NET and both received updates in .NET 10, so a desktop application no longer needs to stay on .NET Framework to keep its UI technology.

Mobile and cross-platform apps

.NET MAUI builds Android, iOS, macOS and Windows apps from one C# codebase. It replaced Xamarin, which is covered in trend 8 below.

Cloud services and microservices

Background workers, message consumers, serverless functions and containerized microservices are a natural fit for .NET on Linux. Native AOT compilation produces small, fast-starting executables, which matters when you pay per second of compute.

Games

Unity uses C# for game scripting, so a large share of game developers write C# every day, even if they rarely think of themselves as .NET developers.

IoT and edge

Devices connected to the internet collect sensor data and act on it, from smart buildings to factory monitoring. Modern .NET runs on Linux and Arm64 hardware, so the same language can cover the device, the gateway and the cloud service that analyzes the data.

Enterprise systems

CRM, ERP, document management and compliance systems are often a mix of web, desktop and mobile front ends on top of a .NET back end. Getting started here needs C#, .NET and JavaScript knowledge, plus deep understanding of the business domain.

AI-enabled applications

This category did not exist in our original article. Today many .NET products add assistants, document search, summarization or agent workflows on top of large language models. Trend 3 explains the libraries that make this practical.

The 8 .NET trends to plan for in 2026

Whatever your industry, whether e-commerce, healthcare, construction, energy or finance, these are the eight .NET trends we expect to shape budgets and roadmaps over the next 12 months. The table shows how each one relates to what we wrote in 2022.

Trend 1: .NET 10 LTS is the new baseline

.NET 10 was released on November 11, 2025 as a Long Term Support release and is supported until November 14, 2028, according to the official support policy. That makes it the default target for any system you expect to run for more than a year.

The deadline that matters most this year is the one for its predecessors. .NET 8 (LTS) and .NET 9 (STS) both reach end of support on November 10, 2026. They end on the same day because Standard Term Support releases are supported for two years, so .NET 9, released a year after .NET 8, runs out at the same time. After that date there are no more security patches, so any internet-facing service still on .NET 8 or 9 becomes a growing risk with every monthly Patch Tuesday that passes it by.

What you get by moving to .NET 10, based on Microsoft's What's new in .NET 10:

• A faster runtime. Better JIT inlining, method devirtualization and stack allocation, plus Native AOT enhancements. These gains arrive without code changes, though how much they matter depends on the workload.
• C# 14. The field keyword for field-backed properties, extension blocks that add extension properties and static extension members, null-conditional assignment and user-defined compound assignment operators. These are small features that remove a lot of boilerplate.
• Post-quantum cryptography. Expanded ML-DSA support, including Composite ML-DSA, so you can start testing quantum-resistant signatures.
• A better SDK. File-based apps that can be published (including with Native AOT), container images built directly from console apps, one-shot tool execution with dotnet tool exec, and Microsoft.Testing.Platform support in dotnet test.
• ASP.NET Core and EF Core 10. Passkey support in Identity, OpenAPI 3.1 by default, built-in validation for minimal APIs, and named query filters in EF Core.

For a well-tested service, moving from .NET 8 to .NET 10 is a modest project compared with leaving .NET Framework. The risk sits in dependencies and breaking changes rather than in your own code. One concrete example from the ASP.NET Core 10 release notes: Microsoft.OpenApi 2.0 drops OpenApiAny in favor of JsonNode, so custom OpenAPI transformers need rewriting. Small items like this are why an upgrade needs a test suite and a short plan rather than a version bump on a Friday afternoon.

A cheap safety net: Microsoft's guide suggests setting the CheckSdkVulnerabilities MSBuild property to true, so builds emit warning NETSDK1239 when they resolve an SDK that is end of life. It takes one line and stops an unsupported SDK from quietly building your releases.

Trend 2: .NET 11, C# 15 and runtime async

.NET 11 was in its release candidate phase at the time of this update (October 2026). Release Candidate 2 was announced on October 13, 2026 with a go-live license, which means Microsoft supports it in production. The What's new in .NET 11 page expects general availability in November 2026, and Microsoft says it will launch the release at .NET Conf. Because releases alternate between LTS and STS and .NET 10 is LTS, .NET 11 is a Standard Term Support release with two years of support.

The features that matter most for product teams, as documented for RC2:

• Runtime async. Async and await move into the runtime itself, with cleaner stack traces and lower overhead. Projects that target .NET 11 get it without preview flags, and the runtime libraries are compiled with it. For I/O-heavy APIs this is the most interesting performance change in years.
• C# 15. Union types and closed hierarchies bring a long-requested way to model "one of these cases" safely, which suits domain models in finance, logistics and construction workflows. Collection expression arguments, extension indexers and labeled break and continue round out the release.
• Libraries for real business problems. IEEE 754 decimal types (Decimal32, Decimal64 and Decimal128), Zstandard compression, System.Text.Json support for unions and JSON Lines, and asynchronous validation in DataAnnotations.
• Supply chain controls. A new option to require a minimum publication age for NuGet packages, which helps defend against freshly published malicious packages.
• Testing on devices. dotnet test now supports Android, iOS, macOS and Mac Catalyst test projects.

Should you adopt .NET 11? Microsoft's own advice in the releases and support guide is that if you build a service you update regularly, you should use the latest release, LTS or STS. If you build a client application that customers install and upgrade on their own schedule, an LTS release can be the better option. Our default for client systems: production on .NET 10, plus a CI pipeline that also builds and tests against .NET 11, so breaking changes surface months before you need to act. Features described from release candidate documentation can still change before the final release.

Trend 3: AI features with Microsoft.Extensions.AI and Agent Framework

In 2022 our AI trend was ML.NET 1.4, Microsoft's library for training custom machine learning models in C#. ML.NET is still maintained, and the 5.x line is current on its GitHub releases page. It remains the right tool for classic machine learning on your own data: classification, regression, anomaly detection and forecasting that runs in-process without a call to an external model.

Most of the new AI work we see in .NET products, however, is generative: assistants inside the product, search over documents, drafting, summarization and agents that take actions. Two pieces of the Microsoft stack now carry that work.

Microsoft.Extensions.AI

The Microsoft.Extensions.AI libraries define common abstractions such as IChatClient for chat models and IEmbeddingGenerator for embeddings. Your code talks to the abstraction, and a provider package supplies the implementation. Function calling, OpenTelemetry telemetry and caching plug in through the same dependency injection and middleware patterns ASP.NET Core developers already use. The practical benefit: you can switch model providers, or run a local model for sensitive data, without rewriting the feature.

Microsoft Agent Framework

Microsoft shipped Agent Framework 1.0 for .NET and Python on April 3, 2026, describing it as production-ready with stable APIs. It brings together the enterprise foundations of Semantic Kernel and the orchestration patterns of AutoGen, with migration guides for both. First-party connectors cover Microsoft Foundry, Azure OpenAI, OpenAI, Anthropic Claude, Amazon Bedrock, Google Gemini and Ollama, and agents can call tools exposed by MCP servers.

What this means for planning:

• If you built on Semantic Kernel in 2024 or 2025, plan a move to Agent Framework. Microsoft even added a "Semantic Kernel to Agents" scenario to its upgrade agent (see trend 4).
• Pick the abstraction first and the model second. Model prices and quality change every few months; your product should not care which one answers.
• The hard part is not the SDK. It is clean data, access rights, evaluation of answer quality and cost control per request. That is where most AI features stall.

Our knowledge systems and copilots work starts there: proving the data before the build. One example from our case studies is ING+, a German construction platform that uses automation and AI to simplify infrastructure management. A dedicated Intelvision team has worked on it since August 2022 on .NET Blazor, Angular, .NET Core Web API and Azure, with a published 40% reduction in development cost.

Trend 4: AI-assisted modernization of .NET Framework applications

Many companies still run important systems on .NET Framework 4.x: Web Forms back offices, WCF services, older ASP.NET MVC sites and desktop tools. They work, so they rarely get budget. But they cannot use modern .NET performance, Linux containers or the newest libraries, and the developers who know them are getting harder to find.

What changed in 2026 is the cost of the mechanical part of migration. Microsoft's GitHub Copilot upgrade agent supports upgrades from any .NET Framework version, and from .NET Core 1.x to 3.x, to .NET 8 or later. Its scenarios include converting projects to SDK-style, replacing Newtonsoft.Json with System.Text.Json, moving from System.Data.SqlClient to Microsoft.Data.SqlClient, moving Azure Functions to the isolated worker model, migrating Web Forms to Blazor and moving Semantic Kernel agents to Agent Framework.

The agent works in three stages, assessment, planning and execution, and writes each stage to Markdown files in the repository so a human can review the strategy before any code changes. It commits each portion of the work to Git, so every step can be reviewed or rolled back.

That is a real productivity gain. It is not a replacement for engineering judgment. The 2025 DORA report found that 90% of respondents use AI at work and more than 80% believe it increased their productivity, yet 30% report little or no trust in AI-generated code, and its central finding is blunt: AI amplifies what is already there. In the 2025 Stack Overflow survey, 66% of developers named "AI solutions that are almost right, but not quite" as their top frustration. An almost-right migration of a billing module is worse than no migration.

The sequence we use for .NET Framework migrations:

1. Inventory. List every project, target framework, NuGet package and Windows-only dependency (System.Web, WCF server, COM, registry access).
2. Protect behavior. Add characterization tests around the flows that make money or carry legal risk before anything moves.
3. Convert and multi-target. Move to SDK-style projects and make shared libraries build for both old and new targets.
4. Move bottom-up. Upgrade leaf libraries first, then services, then the UI. The upgrade agent recommends the same bottom-up strategy for large solutions with deep dependency graphs.
5. Replace what does not port. Web Forms pages, WCF server endpoints and System.Web code need a target technology decision, not just a recompile.
6. Run old and new side by side. Route traffic gradually, feature by feature, so you never bet the business on one cutover weekend.

Our migration and modernization teams run this sequence on live systems. When the problem is not one application but years of accumulated shortcuts across the codebase, our Strike Team approaches it as technical debt remediation, sequenced so each phase pays for itself.

Trend 5: Cloud-native .NET with Azure and Aspire

Azure was one of our 2022 trends, and it remains the most common cloud for .NET workloads. With 20% of the worldwide market in the second quarter of 2026 according to the market research firm SRG, it is the second-largest cloud provider. The reasons we listed then still apply:

• A wide network of regions, which helps with data residency rules for European customers.
• Hybrid options that connect on-premises systems with public cloud services.
• A long list of compliance certifications, which shortens security questionnaires from enterprise customers.
• Close integration with Visual Studio, GitHub, Azure DevOps and Microsoft Entra ID (formerly Azure Active Directory).

The newer trend is how .NET teams build for the cloud. Aspire, previously called .NET Aspire, reached version 13 on November 11, 2025. According to What's new in Aspire 13, it dropped the .NET prefix and now describes itself as a multi-language application platform, with Python and JavaScript apps first-class alongside .NET. An Aspire AppHost describes your services, databases and containers in code and runs them together locally, and the new aspire do command (an experimental preview) turns build, publish and deploy steps into a pipeline with dependency tracking. Aspire 13 requires the .NET 10 SDK.

For engineering leads this solves a familiar problem: the new developer who needs two days and a wiki page to run the system locally. Because the AppHost is code, the setup is reviewed and versioned like everything else instead of living in one engineer's head.

Cost is the other side of cloud-native .NET. Three habits that consistently lower the bill:

• Run ASP.NET Core on Linux containers rather than Windows hosting where nothing requires Windows.
• Use Native AOT for small, short-lived services and functions, where startup time and memory drive cost.
• Measure before you scale up. A profiler session often finds the N+1 query that a bigger database tier would only hide.

Our Fortuna case is a good illustration: a localized advertising platform built on ASP.NET Core, Angular and SQL with Azure DevOps CI/CD, where the published result was a 35% infrastructure cost reduction and a 60% improvement in platform stability and usability.

None of this ties .NET to Azure. .NET services run well in Linux containers on AWS and Google Cloud too. Choose the cloud for your customers, contracts and team skills, not for the language.

Trend 6: Blazor grows up

In 2022 we described Blazor as a framework for interactive client-side web apps in C#. It has become a full-stack web UI framework. A Blazor Web App can combine static server-side rendering for fast first loads with interactive components that run on the server or in the browser through WebAssembly, chosen per page or per component.

.NET 10 removed several pain points that kept teams away, according to the ASP.NET Core 10 release notes:

• State that survives. A declarative [PersistentState] attribute replaces most manual state persistence code, and server-side circuit state can now survive lost connections and browser tab throttling.
• Faster WebAssembly start. Framework assets are preloaded, and hot reload now works for WebAssembly.
• Better forms. Validation supports nested objects and collections and uses a source generator instead of reflection, which also helps Native AOT.
• Production basics. Consistent "not found" handling, a reconnection UI that works with stricter content security policies, and built-in metrics and tracing.

In .NET 11, the QuickGrid virtualization APIs are no longer experimental, according to the RC2 announcement, which helps data-heavy admin screens.

Adoption is still modest: 7% of Stack Overflow respondents used Blazor in 2025, against 44.7% for React. That is the right way to read it. Blazor is not trying to replace React for consumer web apps with large front-end teams. It wins where the team is C#-heavy and the product is a business application: internal tools, portals, back-office systems and B2B platforms where sharing validation rules and models between server and UI saves real time.

When we recommend Blazor:

• Your team is mostly C# developers and you want one language from database to UI.
• The product is a line-of-business application with many forms, grids and workflows.
• You want to share domain models and validation between back end and front end.

When we recommend React or Angular instead: a large dedicated front-end team, a consumer product where the JavaScript ecosystem of UI components matters most, or a design system already built in JavaScript.

Two of our long-running clients use Blazor in production. AVIDENO, a Swiss cloud platform for digitizing company-specific business processes, has worked with two senior Intelvision full-stack developers on C#, .NET and Blazor since June 2022, with a published 40% reduction in development cost and 35% faster time to market. ING+ in Germany runs .NET Blazor alongside Angular.

Trend 7: Security moves into the platform

Our 2022 security section was about .NET Framework features such as code access security. Those Framework-era mechanisms were not carried into modern .NET. Security in 2026 is about what the platform gives you by default, and about not running software that no longer gets patches.

• Passwordless sign-in. ASP.NET Core Identity in .NET 10 supports passkeys (WebAuthn and FIDO2) for phishing-resistant login, and the Blazor Web App template includes passkey management.
• Safer API defaults. Known API endpoints now return 401 and 403 instead of redirecting to a login page when cookie authentication fails, which removes a class of confusing client bugs.
• Post-quantum readiness. .NET 10 expands ML-DSA signatures, and .NET 11 adds experimental composite ML-KEM and HPKE APIs plus X25519 key exchange. You do not need to switch algorithms today, but systems that sign long-lived documents or store encrypted data for years should start testing.
• Supply chain. The .NET 11 SDK can require a minimum publication age for NuGet packages. Combine it with dependency scanning and a software bill of materials in your pipeline.
• Observability for security. New authentication, authorization and Identity metrics in ASP.NET Core 10 make sign-in anomalies visible without custom logging.

The biggest security trend, though, is boring: version hygiene. After November 10, 2026, every service on .NET 8 or 9 stops receiving fixes. In our experience, enterprise customers' security questionnaires ask which runtime versions you run, and "out of support" is a hard answer to defend.

A short checklist we use in reviews:

• Every production service on a supported runtime, patched to the latest servicing update.
• CheckSdkVulnerabilities enabled in builds.
• Dependency scanning in CI that fails the build on known critical vulnerabilities.
• Secrets in a vault, not in configuration files or pipelines.
• Passkeys or single sign-on for admin users, with multi-factor authentication enforced.

Trend 8: .NET MAUI after Xamarin

Xamarin was our sixth trend in 2022. It is now history. Microsoft's Xamarin support policy states that support ended on May 1, 2024 for all Xamarin SDKs, including Xamarin.Forms, and that existing Xamarin.Forms projects should be migrated to .NET MAUI.

.NET MAUI keeps the core promise of Xamarin.Forms: one C# codebase for Android, iOS, macOS and Windows. .NET 10 added multi-file selection and image compression in MediaPicker, WebView request interception and support for Android API levels 35 and 36, as listed in What's new in .NET 10. .NET 11 adds building UI in C#, XAML hot reload improvements and dotnet test support for mobile projects.

The detail many teams miss is the support window. The .NET MAUI support policy guarantees each major version for at least six months after its successor ships. .NET MAUI 9 went out of support on May 12, 2026, and .NET MAUI 10 is supported until May 11, 2027. So even if your back end sits on .NET 10 LTS until 2028, a MAUI app must move to the next version every year. Mobile apps also face yearly platform requirements from the app stores, so budget a small upgrade project annually instead of treating mobile as "done".

Our own case studies include Xamarin-era apps, such as Posude, a mobile-first B2B order-taking app with offline mode and CRM sync, built with Xamarin and delivered as an MVP in 3 months. If you run an app of that generation, the path is clear: Microsoft's upgrade agent lists .NET MAUI and Xamarin among supported project types, but plan for manual work on custom renderers, third-party controls and platform-specific code.

MAUI is not the only option. Blazor Hybrid lets you reuse Blazor components in a native shell, and if your team is stronger in JavaScript or Dart, React Native or Flutter can be the better choice. Pick based on the team you have and the one you can hire.

How to act on these trends: a 90-day plan

Trends are only useful if they change what the team does next. This is the plan we suggest to CTOs and engineering leads who own a .NET estate.

Weeks 1 to 2: get the facts

• List every application and service with its target framework, hosting, owner and business criticality.
• Flag everything on .NET 8, .NET 9, .NET Framework 4.6.2 or older, Xamarin, or an out-of-support MAUI version.
• Record which systems have automated tests you would trust during an upgrade.

Weeks 3 to 6: remove the deadline risk

• Upgrade internet-facing .NET 8 and .NET 9 services to .NET 10 first, then internal ones.
• Enable CheckSdkVulnerabilities and dependency scanning in every pipeline.
• Add a CI job that builds and tests against .NET 11 so you see breaking changes early.

Weeks 7 to 10: start the modernization that pays back

• Run an upgrade assessment on the most valuable .NET Framework application and estimate it module by module.
• Add characterization tests to its critical flows before migration starts.
• Set up Aspire for one system to shorten local setup for new engineers.

Weeks 11 to 13: one AI feature, done properly

• Choose one use case with clear value, such as document search or support ticket triage.
• Build it on Microsoft.Extensions.AI or Agent Framework so the model can be swapped.
• Define how you will measure answer quality and cost per request before launch.

Common mistakes in .NET upgrades and modernization

We see the same mistakes across companies of every size. Most of them are about planning, not code.

• Waiting for the deadline. Teams that start a .NET 8 upgrade in November discover a blocked third-party package in December, when nobody is available.
• Upgrading without tests. A compile is not a migration. Without tests you learn about behavior changes from customers.
• Treating AI-generated changes as finished work. Upgrade agents produce plausible code at speed. Review it like code from a new team member, because that is what it is.
• Big-bang rewrites. Rewriting a .NET Framework system from scratch pauses value delivery and bets everything on one cutover. Incremental migration is slower on paper and faster in reality.
• Ignoring mobile support windows. MAUI and app store requirements move every year, whatever your back-end LTS says.
• Locking AI features to one vendor. Calling a model SDK directly from business logic makes every pricing or model change a refactoring project.

How Intelvision works with .NET

We build and support .NET products for companies across Europe, often in construction tech, proptech, fintech and energy, where systems live for many years and upgrades need to happen without stopping the business.

In our original article we shared Visoplan, a German web platform for collaboration and digitization in construction projects. It is still one of our longest partnerships: we have worked on it since July 2021, scaled the dedicated team from one to five people, and released more than five product-scale features. The published results are a 50% cut in development costs and 40% faster time to market, on a stack of React, .NET Core, C#, ASP.NET Razor Pages, .NET 5.0 and Azure Web Apps with Azure DevOps CI/CD.

Other .NET work from our case studies:

• ING+ (Germany): a dedicated team on .NET Blazor, Angular, .NET Core Web API and Azure since August 2022, with a 40% reduction in development cost.
• AVIDENO (Switzerland): two senior full-stack developers on C#, .NET and Blazor since June 2022.
• Thrive (Ireland): one full-stack developer on React, .NET, EF Core and SQL Server, onboarded in 12 days and supporting the platform for more than 30 months.
• Fortuna: ASP.NET Core and Angular on Azure DevOps, with a 35% infrastructure cost reduction.

If you are comparing partners for this kind of work, our guide to choosing a .NET nearshore development company in Europe lists the questions worth asking.

What to do next

The .NET platform has never been in a better technical state: faster runtimes, a mature web UI framework, a clear AI story and agents that take the drudgery out of upgrades. The risk in 2026 is not the technology. It is the gap between what the platform offers and what your systems actually run.

Start with the date that cannot move: November 10, 2026. Get every .NET 8 and .NET 9 service onto .NET 10, put a .NET 11 build in CI, and then pick one modernization and one AI feature to do properly rather than five to do halfway.

Choosing and upgrading a technology stack is a business decision as much as a technical one. Intelvision can review your .NET estate, plan the upgrade path and provide experienced .NET engineers to carry it out inside your team.