Home Archive Issue #470
Issue #470

Memory Safety, Async Pitfalls, and CI

Coverage includes C# unsafe redesign, ASP.NET Core Task.Run guidance, WinForms scheduling, Clean Architecture, NuGet CI, and ValueTask tradeoffs.

Jasen's top three picks

  1. 1
    Building a Scheduling App in C# WinForms From Scratch: What the Tutorials Skip

    medium.com

    A useful reality check for anyone building desktop line-of-business software; the gaps between tutorial code and shipping code are where most pain lives.

  2. 2
    Improving C# memory safety

    csharpdigest.net

    The most interesting item in the batch for me; language safety work matters because it shapes how we write dangerous code on purpose.

  3. 3
    XAML.io v0.7exports C# projects as native to Windows, macOS and Linux

    news.google.com

    Cross-platform native output from C# projects is notable, especially for teams watching alternatives around XAML-based app delivery.

Editor's note

I pulled together another deliberately mixed issue today, from low-level C# memory safety to practical ASP.NET Core async advice. The memory safety piece is worth your time because it frames the C# 16 unsafe changes as an explicit contract, and the Task.Run article is a good reminder of where server-side concurrency advice still gets misapplied. I also liked the Clean Architecture write-up for grounding the pattern in a concrete failure rather than abstract diagram talk.

Today's articles

Related issues

📬 Get daily .NET content delivered to your inbox