Quick answer: .NET 11 is scheduled to launch at .NET Conf, which runs from 10 to 12 November 2026. It brings C# 15 (including union types), a move to the CoreCLR runtime for .NET MAUI mobile apps, async validation for ASP.NET Core minimal APIs and updated tools for building AI and agent-based apps. For most Australian businesses, the practical advice is simple: if your apps are on .NET 8 or 9, which lose support on 10 November, move them to .NET 10 (the current Long Term Support release) now, and treat .NET 11 as an option for new projects and teams that want the latest features and are comfortable upgrading more often. Do not run preview builds in production, and wait for the stable release and first servicing updates before committing.
What is happening, and when
Microsoft releases a new version of .NET every November, following the same pattern each year: several preview builds through the year, release candidates in autumn, and a stable release at .NET Conf. This year, .NET Conf is a free, online event from 10 to 12 November 2026, and it includes the launch of .NET 11.
The timing matters for a second reason. 10 November is also the date .NET 8 and .NET 9 reach end of support. If you run applications on either version, your priority this month is the upgrade, not the new release. Our last-minute upgrade checklist and our .NET 10 migration guide explain how to do that.
LTS or STS: understanding the two release types
Before comparing versions, it helps to understand how Microsoft supports them:
- Long Term Support (LTS) releases are the ones aimed at stability. They are supported for longer, and they are the usual choice for business-critical systems. .NET 10 is the current LTS release.
- Standard Term Support (STS) releases bring newer features sooner, with a shorter support period. By Microsoft’s current pattern, odd-numbered releases such as .NET 11 are STS.
Support lengths and dates are set out in Microsoft’s official .NET support policy, and they have changed in the past, so always check that page before you plan. The practical point is that the cadence differs: LTS suits teams that upgrade every few years, while STS suits teams that upgrade every year.
What is new in .NET 11?
Here are the main changes that have been announced and previewed, explained in plain language. Features can change before the final release, so check the official release notes once .NET 11 is stable.
C# 15
C# 15 ships with .NET 11. The headline additions are:
- Union types. These let you say that a value can be one of several defined types, such as a successful result or one of a few specific errors. That makes code that handles different outcomes clearer and safer, because the compiler can check that you have dealt with every case.
- Closed hierarchies. These let you declare a fixed set of related types, which also helps the compiler check that code covers every possibility.
- A preview of an updated unsafe model. This is mostly relevant to low-level and performance-sensitive code.
- A few smaller changes that reduce everyday boilerplate.
For most business teams, the benefit is cleaner, easier-to-maintain code and fewer bugs from unhandled cases, not a dramatic change in what you can build.
.NET MAUI and CoreCLR on mobile
One of the larger changes this year is that .NET MAUI apps on Android, iOS and Mac Catalyst move to the CoreCLR runtime. If you build or plan cross-platform mobile apps, this is worth watching. It is aimed at aligning the mobile runtime with the one used elsewhere in .NET, which can improve consistency and performance. It also means mobile projects should be tested carefully before upgrading. Read our guides to .NET MAUI app development and Xamarin to .NET MAUI migration for background.
ASP.NET Core: async validation for minimal APIs
Minimal APIs gain support for asynchronous validation. In practice, this makes it easier to validate input that needs a database lookup or an external check, for example confirming that an email address or an ABN is not already registered, without awkward workarounds. If you build APIs, see our custom ASP.NET development guide.
AI and agents
AI development is a major theme across the .NET ecosystem this year:
- Microsoft.Extensions.AI provides common building blocks for working with AI models. Experimental additions include routing requests between models and providers, and failing over automatically if one is unavailable.
- Microsoft Agent Framework is Microsoft’s framework for building AI agents in C#, with a simple path for deploying them to hosted environments.
- The MCP C# SDK has reached its 2.0 release, with a stateless-by-default design. MCP, the Model Context Protocol, is a standard way for AI tools to connect to your systems and data.
If you are considering adding AI features to a .NET application, these libraries reduce the amount of plumbing you have to build yourself. Note that some of these features are marked experimental, so plan accordingly.
Other updates
Preview releases have also included changes across the libraries, runtime, SDK, Entity Framework Core, F# and Windows Forms. The full list will appear in Microsoft’s official release notes at launch.
Should you upgrade to .NET 11 or stay on .NET 10?
There is no single answer, so use this guide as a starting point:
| Your situation | Suggested approach |
|---|---|
| Apps on .NET 8 or 9 | Upgrade to .NET 10 now. This is your deadline-driven priority. |
| Business-critical systems, regulated industries, small IT teams | Stay on .NET 10 LTS, and plan the next move deliberately. |
| Government or enterprise customers that favour long-supported platforms | Prefer LTS releases. |
| New projects starting soon, with a team comfortable upgrading regularly | Consider .NET 11, once stable and your libraries support it. |
| New cross-platform mobile apps | Evaluate .NET 11 carefully, especially for the CoreCLR change, and test on real devices. |
| AI-heavy or agent-based features | Evaluate the new libraries on .NET 10 or 11, and be aware that some features are experimental. |
| Legacy .NET Framework applications | Do not jump straight to the newest release, and follow our migration roadmap. |
In short, a rule of thumb that works for most businesses is: move to .NET 10 now, evaluate .NET 11 in the first half of next year, and make that decision based on your own needs rather than on novelty.
Practical issues to check before adopting .NET 11
A new release is never just about your own code. Before you commit, check:
- Third-party libraries. Confirm that the packages you depend on support the new version, including UI component libraries, reporting tools, payment and identity libraries.
- Hosting and tooling. Check that your hosting platform, container images, CI/CD pipelines and IDE versions support the new runtime. Platforms sometimes add support after the release date, not on it.
- Entity Framework Core and databases. Review any breaking changes and test data access carefully.
- Mobile and desktop apps. UI frameworks often have the most visible changes, so test on real devices and operating systems.
- Experimental features. Be cautious about building production systems on anything marked experimental or preview.
- Your team’s skills. Plan time for training, particularly for new language features.
How to evaluate .NET 11 safely
- Wait for the stable release. Don’t run preview or release candidate builds in production.
- Create a branch. Retarget one non-critical application to .NET 11 on a separate branch.
- Run your tests. Use your existing automated tests to find compatibility problems early.
- Check performance and memory. Compare behaviour under realistic load.
- Read the breaking changes. Microsoft publishes documentation for each release.
- Wait for the first servicing updates before upgrading important production systems.
- Decide using evidence. Move only the applications that benefit.
If your applications have good test coverage, a move between modern .NET versions is usually far less work than moving from .NET Framework, but the effort rises quickly with older code, many dependencies and heavy customisation.
Australian considerations
- Security patching. The Australian Cyber Security Centre’s Essential Eight stresses patching applications and avoiding unsupported software. Whichever version you choose, make sure you have a plan to keep it supported, and a calendar reminder for its end-of-support date.
- Privacy and compliance. The Privacy Act 1988 requires covered organisations to take reasonable steps to protect personal information. Running a supported .NET version is part of showing you do that.
- Procurement and contracts. Government and enterprise customers often prefer or require software on supported, long-term platforms, which favours LTS releases.
- Insurance and audits. Insurers and auditors increasingly ask about software lifecycles. Documenting your version policy helps.
- Budgeting. If you choose a faster upgrade cadence, include annual upgrade work in your budget. Our .NET development cost guide provides pricing context.
This is general information, not legal advice, so check your obligations with your compliance advisers.
Create a simple .NET version policy
Most organisations benefit from writing down a short policy, so version decisions don’t have to be reinvented every year. A simple example:
- Production systems run on a supported LTS release.
- No production system runs on a version within six months of its end-of-support date without an approved upgrade plan.
- New projects may use the newest stable release if the team has capacity to upgrade annually.
- Each system has an owner who tracks its support dates.
- A short review is held each November after the new release.
This turns the annual release into a routine review instead of a scramble.
Common mistakes to avoid
- Ignoring the 10 November deadline while chasing the new release. Upgrade .NET 8 and 9 apps first.
- Upgrading production on launch day. Let the ecosystem catch up.
- Assuming newer is always better. Choose the version that fits your support and upgrade capacity.
- Relying on experimental features. They can change or be removed.
- Forgetting dependencies. One unsupported library can block an upgrade.
- No test coverage. Without tests, every upgrade is a gamble.
- No owner for upgrades. Without a named person, deadlines slip.
DIY or get a .NET specialist?
If you have a capable in-house team, good tests and a few well-maintained applications, you can follow the steps above yourself. Specialist help makes sense when you have many applications to upgrade, older code, limited capacity, or compliance needs. A good partner will assess your applications, recommend the right target version for each, handle the upgrade and testing, and set up a sustainable upgrade plan. Learn more about our custom software development and dedicated .NET developer services.
Frequently asked questions
When is .NET 11 released?
Microsoft has announced that .NET Conf 2026 runs from 10 to 12 November, and that it includes the launch of .NET 11. Check Microsoft’s .NET blog for the final release date and notes.
Should I upgrade to .NET 11 or .NET 10?
If your apps are on .NET 8 or 9, upgrade to .NET 10 first, because those versions lose support on 10 November. Consider .NET 11 for new projects or when you want its features and are comfortable upgrading more often.
Is .NET 11 a Long Term Support release?
By Microsoft’s current pattern, odd-numbered releases are Standard Term Support and even-numbered releases are Long Term Support, so .NET 10 is LTS and .NET 11 is STS. Confirm the exact support dates on Microsoft’s official support policy page.
What are the biggest new features in .NET 11?
The main announced changes include C# 15 with union types, .NET MAUI moving to CoreCLR on Android, iOS and Mac Catalyst, async validation for minimal APIs, and expanded tools for AI, including the MCP C# SDK 2.0 and the Microsoft Agent Framework.
What are union types in C# 15?
Union types let you declare that a value can be one of several defined types. The compiler can then check that your code handles every case, which reduces bugs.
Is it safe to use .NET 11 in production on launch day?
It is better to wait. Let third-party libraries and hosting platforms catch up, and consider waiting for the first servicing updates before moving important systems.
Will upgrading from .NET 10 to .NET 11 be difficult?
Moving between modern .NET versions is usually much easier than migrating from .NET Framework, but the effort depends on your dependencies, test coverage and how much your code uses features that have changed. Test on a branch first.
What should I do if my app is still on .NET Framework?
Do not wait for .NET 11. Plan a migration to a supported modern .NET version, usually .NET 10, following a staged roadmap. See our legacy migration guide.
What happens if I stay on .NET 8 or 9 after 10 November?
Your apps will keep running, but Microsoft will stop issuing security patches and fixes for those versions, so new vulnerabilities remain unpatched.
Need help choosing the right .NET version?
Dotnet Professional is a Microsoft-partnered .NET development company with teams in Sydney and Melbourne. We can review your applications, tell you which version each should run on, and manage the upgrade so it is safe, tested and on time.
Contact us to book a .NET upgrade assessment.
