5 hours ago · 14 min read2700 words · Tech · hide · 0 comments

This is the fifth post in the series: Exploring the .NET 11 preview. Part 1 - Running background tasks in Blazor with Web WorkersPart 2 - .NET (OK, C#) finally gets union types🎉Part 3 - Avoiding ToString() allocations with StringBuilder.MoveChunksPart 4 - Closed class hierarchiesPart 5 - Improvements to reading Process outputs (this post) In this post I talk about some of the important updates to the Process APIs in .NET 11. Adam Sitnik has been working on a whole load of improvements, improving both the "simple" scenarios (such as running a process and reading the output), as well as adding new features (such as fire-and-forget or kill on parent exit). This work all builds on top of fundamental features introduced in early .NET 11 previews. In this post, I talk about the improvements made to reading child-process output, as these improvements are a great way to avoid some critical failures like deadlocks. I look at how you need to handle it in .NET 100, how it works in .NET 11, and…

No comments yet. Log in to reply on the Fediverse. Comments will appear here.