<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>.NET MAUI | The .NET Blog</title><link>https://thedotnetblog.com/tags/.net-maui/</link><description>Articles, tutorials and insights from the .NET community.</description><generator>Hugo</generator><language>en</language><managingEditor>@thedotnetblog (The .NET Blog)</managingEditor><webMaster>@thedotnetblog</webMaster><lastBuildDate>Mon, 25 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://thedotnetblog.com/tags/.net-maui/index.xml" rel="self" type="application/rss+xml"/><item><title>.NET 11 Preview 4: MCP Server Template, Runtime-Async Libraries, Process API</title><link>https://thedotnetblog.com/news/emiliano-montesdeoca/dotnet-11-preview-4-mcp-template-runtime-async-process-api/</link><pubDate>Mon, 25 May 2026 00:00:00 +0000</pubDate><author>Emiliano Montesdeoca</author><guid>https://thedotnetblog.com/news/emiliano-montesdeoca/dotnet-11-preview-4-mcp-template-runtime-async-process-api/</guid><description>.NET 11 Preview 4 is out. Here are the highlights that caught my eye: the MCP Server template shipping in the SDK, runtime libraries compiled with runtime-async, dotnet watch for mobile, and a major Process API expansion.</description><content:encoded>&lt;p&gt;.NET 11 Preview 4 is available. Every release of a major .NET preview adds a long list of items across the runtime, SDK, libraries, ASP.NET Core, MAUI, C#, and Entity Framework. Rather than repeat the full list, here are the things that stand out to me.&lt;/p&gt;
&lt;h2 id="mcp-server-template-ships-in-the-net-sdk"&gt;MCP Server Template Ships in the .NET SDK&lt;/h2&gt;
&lt;p&gt;The single most interesting item: an MCP Server project template is now included in the SDK. That means &lt;code&gt;dotnet new mcp-server&lt;/code&gt; (or whatever the command ends up being) works out of the box. For anyone building MCP tooling in .NET, this removes the bootstrapping friction considerably. MCP integration in the platform toolchain signals the direction the ecosystem is heading.&lt;/p&gt;
&lt;h2 id="runtime-libraries-compiled-with-runtime-async"&gt;Runtime Libraries Compiled with Runtime-Async&lt;/h2&gt;
&lt;p&gt;The runtime itself now compiles its standard libraries using the runtime-async feature. This is an internal change that affects performance — async state machines in the runtime become more efficient. The significance here isn&amp;rsquo;t user-visible API changes; it&amp;rsquo;s that runtime-async is mature enough to be used for the BCL itself, which is a meaningful signal about the feature&amp;rsquo;s readiness.&lt;/p&gt;
&lt;h2 id="jit-optimizations-and-hardware-intrinsics"&gt;JIT Optimizations and Hardware Intrinsics&lt;/h2&gt;
&lt;p&gt;Preview 4 continues the JIT work. Hardware intrinsics and code generation improvements ship here — details are in the runtime release notes. These are typically the kind of changes that improve throughput on tight computation loops without any code changes on your part.&lt;/p&gt;
&lt;h2 id="process-api-expansion"&gt;Process API Expansion&lt;/h2&gt;
&lt;p&gt;A major update to &lt;code&gt;System.Diagnostics.Process&lt;/code&gt; ships in Preview 4:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;Process.RunAndCaptureTextAsync&lt;/code&gt; — start a process, capture stdout/stderr, wait for exit, all in one call without deadlock risk&lt;/li&gt;
&lt;li&gt;&lt;code&gt;KillOnParentExit&lt;/code&gt; — lightweight lifetime coupling between parent and child processes&lt;/li&gt;
&lt;li&gt;&lt;code&gt;SafeProcessHandle&lt;/code&gt;-based APIs that are more trimmer-friendly&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If you&amp;rsquo;ve ever written boilerplate to capture process output without hitting deadlocks (async read from stdout &lt;em&gt;and&lt;/em&gt; stderr simultaneously), &lt;code&gt;RunAndCaptureTextAsync&lt;/code&gt; is the API you were missing.&lt;/p&gt;
&lt;h2 id="dotnet-watch-for-android-and-ios"&gt;dotnet watch for Android and iOS&lt;/h2&gt;
&lt;p&gt;&lt;code&gt;dotnet watch&lt;/code&gt; now supports device selection for .NET MAUI Android and iOS projects. Faster iteration on mobile without manually managing device connections in the build loop.&lt;/p&gt;
&lt;h2 id="span-based-compression-apis"&gt;Span-based Compression APIs&lt;/h2&gt;
&lt;p&gt;New span-based Deflate, ZLib, and GZip encoder/decoder APIs ship in the libraries. Less allocation when dealing with compressed data — relevant if you&amp;rsquo;re doing high-throughput data processing.&lt;/p&gt;
&lt;h2 id="try-it"&gt;Try It&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://dotnet.microsoft.com/download/dotnet/11.0"&gt;Download .NET 11 Preview 4&lt;/a&gt; — it&amp;rsquo;s a preview, not production-ready, but worth running against your projects to catch any issues early before the RC cycle.&lt;/p&gt;
&lt;p&gt;Original post: &lt;a href="https://devblogs.microsoft.com/dotnet/dotnet-11-preview-4/"&gt;.NET 11 Preview 4 is now available!&lt;/a&gt;&lt;/p&gt;</content:encoded></item></channel></rss>