This website uses cookies

Read our Privacy policy and Terms of use for more information.

In partnership with

Frontier models perform better in Attio’s agent harness.

We gave GPT-6 Astra the same job twice: analyze 100 sales calls and draft the follow-ups, once in Ask Attio and once in ChatGPT.

Ask Attio finished in 4 minutes 49 seconds. ChatGPT took 26 minutes 11 seconds, about 5.4 times as long.

The most ambitious GTM work requires more than frontier intelligence. It requires architecture that can put that intelligence to work at scale.

Hi everyone,

.NET 11 arrived this week, bringing C# 15 and changes across the runtime, web stack, and developer tools. There’s plenty to explore, but I’d start with how those changes fit the applications we already maintain.

Alongside the release coverage, this edition focuses on practical reads on controllers, Excel imports, and finding outdated runtimes in containers. It also covers substantial Rider and Uno updates, plus Visual Studio changes in servicing channels and AI models.

Here’s this week’s reading list.

  1. .NET 11 is here: the release overview
    .NET Team · Microsoft
    C# 15 unions and closed hierarchies, faster CLI startup, asynchronous validation and OpenAPI 3.2 are among the changes in this release. The announcement connects those features with updates to EF Core, Blazor and .NET MAUI, making it a useful starting point before choosing an area to explore. .NET 11 is an STS release with two years of support. Some features discussed alongside the launch still carry preview labels, including opting application code into Runtime Async. Keep that distinction in mind when planning what to adopt.

  2. Explore .NET 11 and C# 15 with Anton
    Anton Martyniuk
    Anton’s walkthrough covers the language, runtime, libraries, ASP.NET Core and EF Core, with a section on breaking changes before upgrading. It gives you a more practical route through a release that can otherwise feel like a long list of announcements.
    I’d start with unions and closed hierarchies, then move to the changes relevant to your application. Read the breaking-change section alongside the examples; that is where an upgrade plan starts to become specific.

  3. What .NET 11 changes for controllers and Minimal APIs
    David Grace · Round The Code
    David demonstrates controller short-circuiting and union response types, then uses an email lookup to explore asynchronous validation in Minimal APIs. The examples make it easier to see where the new features belong in an existing API.
    There’s a useful boundary here: the asynchronous validation example works in Minimal APIs, while his controller example still invokes synchronous validation. Check the behavior for the endpoint style you actually use.

  4. Choose an approach for reading Excel files in C#
    Khalid Abuhakmeh
    Spreadsheet imports tend to start small and grow into something the business depends on. Khalid compares ExcelDataReader, ExcelMapper, ClosedXML, and lower-level options, using the same data model across the examples.
    The choice comes down to what you need: stream rows, map them into objects, or read and edit a workbook. He also shows what parsing an .xlsx file without a library involves. A useful reference before adding the next import endpoint or background job.

  5. Rider 2026.3 brings .NET 11 support and JetBrains Air
    Michael Hawker and Alexander Kurakin · JetBrains
    Rider supports .NET 11 and C# 15 from launch, including help with new language features and debugging support for Runtime Async. JetBrains Air adds a workspace for directing agents and reviewing their work inside the IDE.
    For teams already using coding agents, the workflow changes deserve a look: agents can run tests through Rider’s MCP integration, and local project configuration can be copied into Git worktrees.

  6. Uno Platform 7.0 expands cross-platform UI options
    Uno Platform Team
    Uno 7.0 brings a unified rendering pipeline based on SkiaSharp 4, an experimental WebGPU option, .NET 11 support, and Apple TV as a target. It also extends the use of third-party .NET MAUI controls across Uno targets, including web and Linux.
    The team reports substantial speed and size improvements over 6.7 in its benchmarks. Treat those figures as a reason to test your own screens and workloads. The rendering changes and broader control support are the parts I’d investigate first.

  7. November servicing: check packages as well as runtimes
    Rahul Bhandari and Tara Overfield · Microsoft
    November’s servicing post collects security advisories, release notes, and downloads for .NET, with links to .NET Framework updates. It deserves attention even if a major-version upgrade is already underway.
    Two details are easy to miss: one advisory requires a separate update to the System.Formats.Cbor package, and another concerns Identity scaffolding and templates, including previously generated application code. Follow the relevant remediation instructions; updating an installed runtime alone does not cover every fix.

  8. Use your own AI models in Visual Studio
    Praveen Sethuraman · Microsoft
    Bring Your Own Model is generally available in Visual Studio 18.12. You can configure multiple connections to the same provider, connect custom or local endpoints, and select an API format that matches the model service.
    This is particularly relevant when your team has an approved internal endpoint, or you want separate work and personal configurations. GitHub sign-in is not required for BYOM, although endpoint authentication, network access, and organizational policies still apply.

  9. A modern C# reference to keep nearby
    Khalid Abuhakmeh
    Khalid’s cheat sheet collects examples for collections, records, pattern matching, LINQ, asynchronous code, and null handling. It is organized for jumping to the syntax you need rather than reading everything in one sitting.
    The examples target .NET 10 and C# 14, so this is a useful companion for everyday work and onboarding alongside this week’s C# 15 coverage.

  10. Visual Studio LTSC 18.11: a servicing choice for teams
    Jamshed Damkewala · Microsoft
    Visual Studio 2026 LTSC 18.11 receives support through November 14, 2028, and includes .NET 10 LTS toolsets. It is intended for organizations that need a fixed feature baseline while continuing to receive security and critical fixes.
    Stable continues with monthly feature and quality updates. For teams managing shared development environments, this is a deployment decision worth making deliberately. The Visual Studio 18.12 AI announcements in this issue belong to a different release from LTSC 18.11.

  11. What changed in Visual Studio’s Copilot experience
    Dalia Abo Sheasha · Microsoft
    Visual Studio 18.12 moves Copilot Chat onto an SDK-based execution engine. You can steer it while a task is running, inspect tool results, follow subagent activity, and see request costs.
    Microsoft reports improved results on its C# task benchmark using the same models. That is an encouraging result from its evaluation; try the updated workflow on representative tasks from your own codebase and review the resulting changes and tests.

  12. Rider’s game development update: Godot, debugging and new plugins
    Anna Ruban · JetBrains
    The game development release gets its own detailed walkthrough, including a closer connection with the Godot Editor, improvements to C++ debugging, and support for Unity CoreCLR Players. Shared command-line argument presets should also help when switching between common launch scenarios.
    Lua and Verse plugins are available in beta. If you work with Godot and C#, start with the ability to debug the current scene through the editor with Rider attached from the first frame.

  13. Find .NET 8 and 9 in your container inventory
    Silpa Nallagopula
    Last issue’s support deadline has now passed: .NET 8 and 9 reached end of support on November 10. Silpa looks at the next operational question: how do you identify the runtime inside images whose tags only describe your application version?
    The article uses inherited image configuration as an initial check and discusses SBOM scanning for self-contained applications. It is a useful starting point for an inventory, with coverage gaps to account for. Microsoft’s support policy confirms the lifecycle dates.

Which part of .NET 11 are you planning to try first—and what needs to be in place before you upgrade an existing application?

Thanks for reading,

Get future editions at dotnet.news.
Have an article to suggest? Send it to [email protected].