# .NET 11 .NET 11 is a software development platform release with SDKs and runtimes for building and running .NET applications. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Performance Improvements in .NET 11 DevFeed: [Performance Improvements in .NET 11]() Original publisher: [Read original article]() Author: Stephen Toub - MSFT Published: 2026-09-15T12:00:00Z Content type: article Language: en Sources: [.NET Blog]() Topics: [.NET](), [.NET 11]() Tags: [blog](), [improvements](), [net](), [net-11](), [performance](), [post]() ### AI overview This post surveys hundreds of performance improvements in .NET 11, including runtime and library changes that reduce bounds checks, allocations, locks, loop cycles, redundant checks, instructions, system calls, and array-copy costs. ### Source excerpt Take a tour through hundreds of performance improvements in .NET 11. The post Performance Improvements in .NET 11 appeared first on .NET Blog. ## Microsoft Releases .NET 11 RC1 with Go-Live Support, C# 15 and F# 11 as Default Language Versions DevFeed: [Microsoft Releases .NET 11 RC1 with Go-Live Support, C# 15 and F# 11 as Default Language Versions]() Original publisher: [Read original article]() Author: Almir Vuk Published: 2026-09-15T07:11:00Z Content type: news Language: en Sources: [InfoQ]() Topics: [.NET 11](), [C# 15](), [Microsoft](), [releases](), [ASP.NET Core](), [F#](), [SignalR](), [SDKs](), [.NET MAUI](), [native aot]() Tags: [android](), [api](), [asp-net-core](), [c-sharp-15](), [development](), [dotnet-11-rc-1-release](), [f-sharp](), [ios](), [macos](), [microsoft](), [native-aot](), [net](), [net-10](), [net-11](), [net-9](), [net-core](), [net-maui](), [news](), [releases](), [sdk](), [signalr]() ### AI overview Microsoft released .NET 11 Release Candidate 1 with go-live support for production use. It makes C# 15 and F# 11 the default language versions and stabilizes features from the preview cycle. The release also extends testing across mobile and desktop targets, updates SignalR authentication refresh APIs, and adds SDK, ASP.NET Core, Blazor, and Native AOT-related improvements. ### Source excerpt 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 ## Quiz: Python 3.15 Preview: Lazy Imports DevFeed: [Quiz: Python 3.15 Preview: Lazy Imports]() Original publisher: [Read original article]() Author: Real Python Published: 2026-09-09T12:00:00Z Content type: article Language: en Sources: [Real Python]() Topics: [Python](), [.NET 11]() Tags: [module](), [python](), [time]() ### AI overview An interactive 12-question quiz tests understanding of Python 3.15 Preview lazy imports, including the lazy keyword, __lazy_modules__, deferred module loading, startup-time savings, restrictions, older-Python alternatives, and imports that must remain eager. ### Source excerpt Test your understanding of Python 3.15 lazy imports, from the lazy keyword and __lazy_modules__ to the imports that have to stay eager. ## Python in Visual Studio Code - October 2025 Release DevFeed: [Python in Visual Studio Code - October 2025 Release]() Original publisher: [Read original article]() Author: Luciana Abud Published: 2025-10-10T17:55:26Z Content type: release Language: en Sources: [Microsoft Python Engineering]() Topics: [Python](), [Visual Studio Code](), [releases](), [Testing](), [Pytest](), [.NET 11](), [Windows Subsystem for Linux](), [GitHub Copilot](), [jupyter]() Tags: [2025](), [github-copilot](), [powershell](), [pytest](), [python](), [release](), [releases](), [testing](), [visual-studio-code](), [wsl]() ### AI overview Microsoft announces the October 2025 release of the Python extensions for Visual Studio Code. The update improves Python environment handling, adds a Copy Test ID option for pytest functions, and makes Python virtual-environment activation more reliable across shell creation methods, PowerShell, and WSL. ### Source excerpt The October 2025 release of the Python and Jupyter extensions for Visual Studio Code are now available. This release includes improvements to the Python Environments extension, Copy Test ID functionality, and enhanced environment activation when using Copilot Chat. Keep on reading to learn more! The post Python in Visual Studio Code - October 2025 Release appeared first on Microsoft for Python Developers Blog. ## Oracle JDK licensing changes in Java 11 and OpenJDK alternatives DevFeed: [Oracle JDK licensing changes in Java 11 and OpenJDK alternatives]() Original publisher: [Read original article]() Author: Stephen Colebourne (noreply@blogger.com) Published: 2018-09-26T10:57:00Z Content type: opinion Language: en Sources: [Stephen Colebourne]() Topics: [Java](), [openjdk](), [.NET 11](), [Adoptium](), [GNU General Public License]() Tags: [adoptium](), [java](), [jdk](), [lts](), [openjdk](), [oracle]() ### AI overview The author argues that Oracle JDK for Java 11 has commercial-use restrictions and recommends choosing a free OpenJDK build for commercial use. The article cites Adoptium as a GPL-licensed option intended to provide more than four years of security patches. ### Source excerpt TL:DR; Java is still available at zero-cost, you just need to stop using Oracle JDK and start using an OpenJDK build, such as this one or this one. The trap Java 11 has been released. It is a major release because it has long-term support (LTS). But Oracle have also set it up to be a trap (either deliberately or accidentally). For 23 years, developers have downloaded the JDK from Oracle and used it for $free. Type "JDK" into your favourite search engine, and the top link will be to an Oracle Java SE download page (I'm deliberately not providing a link). But that search and that link is now a trap. Oracle JDK, the one all web searches take you to, is now commercial not $free. The key part of the terms is as follows: You may not: use the Programs for any data processing or any commercial, production, or internal business purposes other than developing, testing, prototyping, and demonstrating your Application; The trap is as follows: Download Oracle JDK (because that is what you've always done, and it is what the web-search tells you) Use it in production (because you didn't realise the license changed) Get a nasty phone call from Oracle's license enforcement teams demanding lots of money In other words, Oracle can rely on inertia from Java developers to cause them to download the wrong (commercial) release of Java. Unless you read the text/warnings/legalese very carefully you might not even realise Oracle JDK is now commercial, and that you are therefore liable to pay Oracle for using this particular JDK in production. (Update, 2018-10-03: Searches for Java 11 and JDK 11 now seem to be resolving to OpenJDK builds, not commercial ones!) Is this trap malicious behaviour on the part of Oracle? Readers will have their own opinions. I do suggest bearing in mind that Oracle invests huge amounts in developing Java, so it is reasonable to have a commercial plan available for those that want it. And they do provide a $free alternative completely valid for commercial use... The ## The TODO list, collaborative edition DevFeed: [The TODO list, collaborative edition]() Original publisher: [Read original article]() Published: 2014-06-28T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [.NET 11](), [opensource](), [Windows]() Tags: [free](), [open-source](), [opensource](), [os](), [react](), [reactos](), [reports](), [weekly](), [win32](), [winapi]() ### AI overview A weekly status report about ReactOS discusses the project's older known issues and notes that the report may be shorter or different than usual. ### Source excerpt Hello! Welcome back to my weekly status report. I want to finally start writing the reports on Fridays, so it hasn't been that many days since the last report, and there was a holiday in the middle of this week and some craziness you may already be aware of, so this report may end up either shorter than usual, or at least different. Sorry about that! I started the week by looking back at older "known issues".