1 min readfrom InfoQ

Microsoft Releases .NET 11 RC1 with Go-Live Support, C# 15 and F# 11 as Default Language Versions

Our take

Microsoft has released .NET 11 Release Candidate 1, marking a significant step forward with go-live support for production environments. This release designates C# 15 and F# 11 as the default language versions, streamlining development workflows. Key improvements include expanded dotnet test capabilities for mobile and desktop, finalized SignalR authentication refresh APIs, and enhanced Android build times within .NET MAUI. Explore these advancements and discover how .NET 11 empowers developers to build more efficiently.
Microsoft Releases .NET 11 RC1 with Go-Live Support, C# 15 and F# 11 as Default Language Versions

The release of .NET 11 Release Candidate 1 by Microsoft signals a continued commitment to rapid iteration and a future-focused development cycle for the platform. The immediate availability of a go-live support license is particularly noteworthy, demonstrating a confidence in the maturity of the release and a desire to encourage immediate adoption. This aligns with the broader industry trend toward faster release cadences, allowing developers to leverage the latest features and improvements sooner. The shift to C# 15 and F# 11 as default language versions also underscores Microsoft’s dedication to providing modern language capabilities within the .NET ecosystem, empowering developers with tools to build increasingly sophisticated and performant applications. This move is particularly relevant given the ongoing discussions around responsible AI development, as highlighted in [Microsoft’s new AI ‘code of conduct’ tells models not to hack systems or trick humans], where robust and reliable development platforms are essential for building trustworthy AI solutions.

Beyond the headline changes, the expanded functionality of `dotnet test` to include mobile and desktop targets is a practical improvement that streamlines the development and testing workflow. This broadened support reflects a recognition of the diverse environments in which .NET applications are deployed. The finalization of SignalR authentication refresh APIs addresses a critical area for real-time communication applications, enhancing security and reliability. Improvements to Android build times within .NET MAUI are also welcome, particularly for developers targeting cross-platform mobile solutions. It’s interesting to see the evolution of tools like .NET alongside projects pushing hardware boundaries, such as the [ESP32 Bit Pirate: Bridging Modern Microcontrollers and Browser-Based Hardware Debugging] project, which demonstrates the expanding possibilities of embedded development and debugging. The advancements within the .NET ecosystem increasingly complement and support these broader trends in the developer landscape. Furthermore, the focus on modularity and performance, as seen in Jotai 3.0's shift to ESM-only packages [Jotai 3.0 Ships as a Modernized, ESM-Only Package That Drops Legacy Builds and Deprecated APIs], resonates with the .NET team’s own efforts to optimize for modern deployment environments.

The significance of .NET 11 RC1 extends beyond the specific features included in this release. It represents a maturation of the .NET platform as a whole, solidifying its position as a leading choice for building a wide range of applications, from web services to desktop applications to cloud-native solutions. Microsoft’s willingness to embrace a shorter release cycle, coupled with the ongoing enhancements to language capabilities and tooling, demonstrates a commitment to keeping .NET relevant and competitive in a rapidly evolving technological landscape. The inclusion of go-live support so early in the release cycle is a strategic decision that signals Microsoft’s confidence in the stability and reliability of the platform. This approach encourages developers to experiment with new features and integrate them into their projects with greater assurance.

Looking ahead, it will be fascinating to observe how the adoption of C# 15 and F# 11 impacts developer productivity and application performance. The continued refinement of .NET MAUI and its ability to deliver consistent cross-platform experiences will also be a key area to watch. Ultimately, the success of .NET 11 and subsequent releases will depend on Microsoft's ability to continue delivering on its promise of a modern, accessible, and empowering development platform. One crucial question remains: how will Microsoft balance the need for rapid innovation with the imperative of maintaining backward compatibility, ensuring a smooth transition for existing .NET applications?

Last week, Microsoft has released .NET 11 Release Candidate 1, the first release candidate of the cycle, shipping with a go-live support license for production use. The release makes C# 15 and F# 11 the default language versions, extends dotnet test to mobile and desktop targets, finalizes the SignalR authentication refresh APIs, and improves Android build times in .NET MAUI.

By Almir Vuk

Read on the original site

Open the publisher's page for the full experience

View original article