.NET 11 Release Candidate 1 is now available, and it includes something important: a go-live support license.
This means Microsoft supports .NET 11 RC1 for production applications. It also makes this one of the best times to begin learning what the next version of .NET means for your applications under real-world conditions.
However, “supported for production” should not be interpreted as “appropriate for every production application.”
Release candidates are a valuable opportunity, but selecting the right project matters.
Why Start Before the Final Release?
Testing a new .NET release against a sample application can identify obvious compilation errors and breaking changes. It cannot fully reproduce everything that happens inside a real application.
Production applications include third-party dependencies, authentication workflows, database integrations, background processing, build pipelines, hosting configuration, monitoring, and actual user behavior.
Those are the areas where meaningful upgrade lessons tend to appear.
Using .NET 11 RC1 with a real application gives your team time to discover those issues before the final release. It also gives you a chance to evaluate new runtime, SDK, ASP.NET Core, Blazor, .NET MAUI, Entity Framework Core, and C# capabilities in the context where you may actually use them.
That experience helps transform a future upgrade from an abstract backlog item into a path your team has already started to understand. Just as I've said before, just because it compiles doesn't mean you are fully upgraded! What new features become 'critical' during the upgrade to improve your applications, as that will set the true scope for all others.
Choose the Right Production Application
A go-live license does not eliminate the possibility of instability or changes between RC1, RC2, and the final production release.
The application selected for early adoption should be able to tolerate that risk. Good candidates might include:
- An internal application with a controlled group of users.
- A new application that has not yet accumulated many dependencies.
- A lower-risk service that can be rolled back or redeployed quickly.
- An application with strong automated tests and useful production telemetry.
- A project whose schedule can accommodate additional framework or dependency updates.
A mission-critical application with limited test coverage, difficult deployment processes, or strict dependency requirements is probably not the best first candidate.
The question is not simply whether the application can run on RC1. The question is whether the organization can respond effectively if something changes.
The Go-Live License Is Support, Not a Stability Guarantee
Microsoft’s go-live designation means that RC1 is supported for production use. That is a meaningful distinction from earlier preview releases, which are intended for public testing but are not supported in production.
It does not guarantee that every third-party package, hosting platform, development tool, or application framework has completed its own .NET 11 validation.
Before deploying, review the complete application stack:
- Confirm that important NuGet packages support .NET 11.
- Validate the required Visual Studio and build-agent versions.
- Review documented breaking changes.
- Test deployment and rollback procedures.
- Verify that logs, metrics, and alerts can expose unexpected behavior.
- Plan time for the move from RC1 to RC2 and then to the final release.
Early adoption should be intentional, observable, and reversible.
Real-World Usage Builds the Upgrade Path
The strongest reason to consider .NET 11 RC1 is not simply to say that an application is running the newest version.
It is to start building practical knowledge.
A carefully selected production application can show which dependencies are ready, which tests need improvement, how the deployment pipeline must change, and where the upgrade documentation is incomplete. Those lessons can then guide the migration of larger and more critical applications after .NET 11 reaches general availability.
There is risk in adopting a release candidate, but there is also risk in waiting until the final release before beginning any meaningful evaluation.
.NET 11 RC1 provides a supported opportunity to move beyond experimental projects and start testing the platform under real conditions. Choose an application that can tolerate some instability, prepare for changes between releases, and use what you learn to chart the path for the rest of your application portfolio.
Go-live support makes production adoption possible. Good project selection and disciplined engineering make it practical.
What is your stance with regards to Go-Live usage of a Release Candidate? Is it a risk you will take? Why or why not?