.NET 11 RC2: 9 Updates Beat Java 27 [2026]

Microsoft’s .NET Team published .NET 11 Release Candidate 2 on October 13, 2026, updating nine areas of the platform just as Oracle’s Java 27 and JetBrains’ new agentic IDE system settle into the market. The timing is not a coincidence so much as a reminder of how crowded the annual release calendar has become for backend developers choosing a platform for new work. Three major moves landed inside a five week window: Java 27 in September, JetBrains Air’s early access program in early October, and now .NET 11 RC2 on October 13.

None of these releases exist in a vacuum. Teams planning 2027 roadmaps are weighing runtime performance, tooling support, and security patch cadence against each other at the same moment three ecosystems are shipping their biggest updates of the year. This piece breaks down what changed in .NET 11 RC2, how it stacks up against the current Java release, and what the surrounding framework news, including a 16-CVE patch in Micronaut and a version floor bump in Grails 8, says about where backend development is headed.

Google · Preferred Sources

Don't miss new tech stories on Google

Add TrendinTech once in the Google app and our stories appear in your news suggestions.

Add Now

Microsoft Ships .NET 11 Release Candidate 2

The .NET Team’s October 13 announcement describes .NET 11 RC2 as the second release candidate in the cycle, arriving with a go-live support license that clears it for production use ahead of general availability. That license is the detail enterprise teams watch closest: it signals Microsoft’s confidence that the build is stable enough to run real workloads, even though it remains a prerelease.

“.NET 11 Release Candidate 2 is now available. This is our second release candidate, which comes with a go-live support license so you can confidently use this release for your production applications.”
.NET Team, Microsoft .NET engineering team, via devblogs.microsoft.com

.NET 11 is expected to reach general availability as part of Microsoft’s annual November release cycle, matching the cadence it has kept since .NET 5. The company has not published an exact RTM date in the RC2 post itself, so the usual assumption, a release tied to .NET Conf in November, stands until Microsoft confirms it directly.

Nine Components Touched in This Build

According to the .NET blog, RC2 includes changes across the runtime, class libraries, SDK, MSBuild, NuGet, F#, ASP.NET Core, .NET MAUI, and Windows Forms. That spread covers nearly every layer of the stack a typical enterprise .NET shop touches, from low level runtime behavior up through the desktop and mobile UI frameworks. Microsoft bundled the RC2 announcement with its routine October 2026 .NET and .NET Framework servicing updates, also dated October 13, which carry both security and non-security fixes for teams still running older supported versions alongside the new release candidate.

Pairing a release candidate with a servicing update in the same week is standard practice for Microsoft, but it does mean teams tracking .NET 11 need to separate two different patch streams: fixes rolling into the new major version, and fixes landing on .NET 8, 9, and 10 for shops not ready to move yet.

What the Go-Live License Actually Permits

A go-live license is not the same as general availability. It means Microsoft will support production deployments of RC2, but the build can still change before RTM, and teams are expected to validate their own dependencies, analyzers, source generators, CI images, and third-party NuGet packages before shipping it. For a platform update that touches ASP.NET Core and MSBuild at the same time, that validation step matters more than usual, since build pipeline behavior and web request handling are exactly the kinds of changes that surface late in a release cycle.

Teams that have already adopted the AI-assisted code editors now common in enterprise workflows will find that most mainstream tooling updates its language server support within days of an RC, since editor vendors track Microsoft’s prerelease NuGet feeds closely.

Visual Studio 2026 Insiders and the C# Dev Kit Workflow

Microsoft confirmed that .NET 11 RC2 is supported in the new Visual Studio 2026 Insiders build, as well as in Visual Studio Code paired with the C# Dev Kit extension. That dual-track support, a full desktop IDE on one side and a lighter extension-based setup on the other, mirrors how Microsoft has handled every .NET release since Visual Studio Code’s C# tooling matured.

“This release of .NET 11 is supported in the new Visual Studio 2026 Insiders release alongside Visual Studio Code with the C# Dev Kit.”
.NET Team, Microsoft .NET engineering team

A quick way to confirm a project is actually targeting the new release once GA lands is checking the target framework moniker in the project file:

<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <TargetFramework>net11.0</TargetFramework>
    <Nullable>enable</Nullable>
  </PropertyGroup>
</Project>

Java 27 Landed Weeks Earlier, and the Comparison Writes Itself

Oracle shipped Java 27 in September 2026, and JetBrains confirmed in its October Java Annotated Monthly post that IntelliJ IDEA supported the release from day one. That is the same week-one tooling confidence Microsoft is now extending to .NET 11 through Visual Studio 2026 Insiders, and it puts the two platforms on comparable footing for anyone deciding where to place a new service this quarter. The site’s own breakdown of Java 27’s post-quantum cryptography JEPs against the Java 25 long-term support baseline covers the language side of that story in more depth.

Java 25, released in September 2025, remains the current long-term support version many enterprises still run in production, which means Java 27 occupies roughly the same position .NET 11 will hold once it ships: a newer, feature-forward release sitting next to an LTS baseline that conservative shops are in no rush to leave.

JetBrains Air Adds an Agentic Wrinkle to the IDE Race

The same October update from JetBrains also confirmed the early access program for JetBrains Air, described as a system of products built around agentic software development. JetBrains has also been previewing Java and Kotlin language support for third-party editors through an LSP-based extension, a move that would let VS Code and its forks tap into JetBrains’ language intelligence without switching IDEs entirely. That is a notable shift for a company that has historically kept its best tooling inside its own editors, and it lines up with the broader agentic-coding push the site covered in its comparison of Zed, VS Code, and JetBrains Air market share.

For .NET developers, the relevant question is whether Microsoft answers with its own agentic layer inside Visual Studio 2026 before JetBrains Air exits early access. Right now, the C# Dev Kit gives Visual Studio Code a lightweight path into .NET 11, but it does not yet carry the same agentic framing JetBrains is building into Air.

Where C# and Java Actually Stand With Developers

Stack Overflow’s 2025 Developer Survey, which collected more than 49,000 responses across 177 countries, gives the clearest public read on how C# and Java compare to the rest of the language field. JavaScript led for the thirteenth straight year, while Python posted the largest single-year jump in the survey’s history, up roughly seven percentage points from 2024.

Language	Share of respondents (2025)
JavaScript	66.0%
HTML/CSS	61.9%
SQL	58.6%
Python	57.9%
Bash/Shell	48.7%
TypeScript	43.6%
Java	29.4%
C#	27.8%
C++	23.5%

Java’s own usage trend is worth a second look: a recruiting-industry analysis of the same Stack Overflow data put Java at 29.7% among professional developers specifically, down from 30.6% a year earlier, while ranking it fourth on the TIOBE Index and second on the PYPL index as of September 2026. C# sits just behind Java in the Stack Overflow figures, close enough that platform choice increasingly comes down to ecosystem and tooling rather than raw popularity.

.NET’s November Cadence: A Short Release History

.NET 11 is on track to continue a release rhythm Microsoft has held since it unified .NET Framework and .NET Core into a single yearly cadence. Every major version since .NET 5 has shipped in November, with every even-numbered release carrying long-term support.

Version	Release timing
.NET 5	November 2020
.NET 6 (LTS)	November 2021
.NET 7	November 2022
.NET 8 (LTS)	November 2023
.NET 9	November 2024
.NET 10 (LTS)	November 2025
.NET 11	RC2 on October 13, 2026; GA expected in the November 2026 cycle

Under that pattern, .NET 11 is a standard-support release, meaning the long-term support decision for cautious enterprises will likely wait for .NET 12 in November 2027. That makes .NET 10, shipped last November, the version most production-focused teams are still standardizing on while .NET 11 attracts early adopters.

Micronaut Patches 16 CVEs as Framework Security Gets Serious

While Microsoft and Oracle traded release headlines, the Micronaut Framework team pushed out version 5.2.2, built on Micronaut Core 5.2.15, which updates its bundled Netty dependency to version 4.2.19.Final. That update addresses 16 CVEs, including HTTP request and response smuggling issues and unbounded resource consumption bugs across HTTP, HTTP/2, and HTTP/3 codecs. For any team running Micronaut-based microservices in front of public traffic, that patch is a higher priority than either of the headline platform releases this month.

Request smuggling bugs are particularly dangerous in microservice architectures because they let an attacker craft a request that two different layers of a proxy chain interpret differently, potentially bypassing access controls placed in front of an internal service. A 16-CVE batch landing in one dependency bump is a reminder that the framework layer, not just the language runtime, carries its own patch cadence that teams have to track separately from Java or .NET version upgrades.

Grails 8 Raises Its Minimum Bar to JDK 21

Apache Grails also shipped version 8.0.0 this month, with bug fixes, documentation updates, dependency upgrades, and new features. The release sets JDK 21 and Gradle 9.7 as its new minimum versions, and it changes controller behavior so controllers now resolve as REST resources directly from the incoming request rather than relying solely on explicit mappings. Combined with the Micronaut patch, it is a reminder that the JVM ecosystem’s framework layer is moving on its own schedule, somewhat independent of whether a shop has adopted Java 27 yet.

Release Roundup: What Shipped in October 2026

Project	Release	Key detail
Oracle Java	Java 27	Shipped September 2026; day-one support in IntelliJ IDEA
JetBrains Air	Early access program	Agentic development system; LSP-based Java and Kotlin support previewed for VS Code and forks
Apache Grails	8.0.0	Requires JDK 21 and Gradle 9.7 minimum; controllers resolve as REST resources
Micronaut Framework	5.2.2 (Core 5.2.15)	Netty updated to 4.2.19.Final; patches 16 CVEs including request smuggling
Microsoft .NET	11 Release Candidate 2	Go-live license; updates runtime, SDK, ASP.NET Core, MAUI, and six other areas

GitHub Copilot’s Own October Shuffle

The same month also brought changes to GitHub’s own tooling. GitHub’s changelog lists new controls and chat improvements for Copilot inside JetBrains IDEs, weekly Copilot release notes through early October, the arrival of Claude Haiku 5.5 inside GitHub Copilot, and an update to CodeQL 2.27.2 that improves static analysis coverage for C++, Go, Rust, and JavaScript. Those changes land separately from the GitHub Copilot model lineup changes set to take effect by mid-November, but together they show Microsoft tuning its AI-assisted coding stack on nearly the same timeline as its core .NET release.

Market Impact: Why Platform Choice Still Matters in 2026

None of these releases exist purely as technical news. Every platform decision a team makes this quarter carries hiring, tooling licensing, and cloud cost consequences that outlast the release cycle that triggered it. A shop standardizing on .NET 11 is also betting on Microsoft’s Azure-aligned tooling roadmap, while a shop staying on Java 27 or moving to Micronaut is betting on the broader, more fragmented JVM ecosystem with its own mix of vendors.

The AI coding layer complicates that calculus further. A recent METR-style study the site covered found that some AI coding agents actually slowed experienced developers down by roughly 19% on real tasks, a result worth weighing against any plan to lean on agentic tooling like JetBrains Air or GitHub Copilot to offset a platform migration’s labor cost. Teams evaluating .NET 11 against Java 27 should treat tooling maturity, not just raw language popularity, as the deciding factor, since both ecosystems now have comparable day-one IDE support.

Historical Context: How the Platforms Got Here

The current rivalry traces back to Microsoft’s decision to unify .NET Framework and the open source .NET Core into a single annual release train starting with .NET 5 in 2020, abandoning the old Framework-versus-Core split that confused adoption for years. Java, by contrast, moved to a six-month release cadence back in 2017, alternating short-lived feature releases with long-term support versions every two to three years, a rhythm Java 25’s LTS status and Java 27’s feature release both reflect.

Both ecosystems have spent the years since chasing the same goals: faster startup times, lower memory footprints for containerized deployments, and tighter integration with cloud-native tooling. The database and API testing layer, covered in tools like DataKitchen’s TestGen, which added DuckDB, CSV, JSON, and Parquet profiling support this month, shows that the pressure to modernize is not limited to languages and frameworks. It extends into the testing and data-quality tooling that sits alongside them in any production pipeline, a space also reshaped this year by delays tied to AI-assisted code review in PostgreSQL 19.

Predictions for the Rest of 2026

.NET 11 will reach general availability in November 2026 alongside Microsoft’s annual developer conference cycle, continuing the unbroken pattern set since .NET 5.
JetBrains Air will exit early access with broader IDE integration before .NET 11’s first point release, pressuring Microsoft to clarify its own agentic coding roadmap for Visual Studio.
More JVM framework maintainers will follow Micronaut’s lead and ship consolidated security patches bundling multiple CVEs, as Netty-level smuggling bugs get more scrutiny across the ecosystem.
Enterprise adoption of .NET 11 will lag .NET 10’s LTS install base through at least mid-2027, mirroring how Java 27 trails Java 25’s LTS footprint today.
GitHub Copilot’s model lineup and CodeQL coverage will keep expanding in lockstep with whichever platform, .NET or Java, sees the faster day-one tooling response to its newest release.

Frequently Asked Questions

What is .NET 11 Release Candidate 2?
It is the second release candidate for Microsoft’s next major .NET version, published by the .NET Team on October 13, 2026, with a go-live support license that permits production use ahead of general availability.

When will .NET 11 officially release?
Microsoft has not published an exact general availability date in the RC2 announcement, but the company’s release history points to the annual November cycle it has followed since .NET 5 shipped in November 2020.

Is .NET 11 a long-term support release?
Based on Microsoft’s established even-year LTS pattern, .NET 11 is expected to be a standard-support release, following .NET 10’s long-term support status from November 2025.

How does .NET 11 compare to Java 27?
Both arrived within weeks of each other this fall, and both now have day-one support in their respective flagship IDEs, Visual Studio 2026 Insiders for .NET 11 and IntelliJ IDEA for Java 27. Direct performance benchmarks between the two have not been published yet.

What is JetBrains Air?
JetBrains Air is a new system of products focused on agentic software development, now in early access, with JetBrains also previewing LSP-based Java and Kotlin support for third-party editors including VS Code and its forks.

Why does the Micronaut CVE patch matter if I am not using .NET or Java 27 directly?
Micronaut Framework 5.2.2 fixes 16 CVEs tied to its bundled Netty dependency, including HTTP request and response smuggling issues, which affect any production service built on the framework regardless of which language platform release a team is tracking.

Can I use .NET 11 RC2 in production today?
Microsoft’s go-live support license permits it, but the build is still a prerelease, so teams should validate their dependencies, analyzers, and CI pipelines before deploying it to live workloads.

What should I check before upgrading a project to .NET 11?
Review the official .NET 11 release notes and the ASP.NET Core, .NET MAUI, and Windows Forms migration guidance once published, and test third-party NuGet packages, source generators, and build tooling such as MSBuild and NuGet against the new version before moving production workloads.

.NET 11 RC2 Ships 9 Updates, Java 27 Closes Gap [2026]