Build your own or use an out-of-the-box event sourcing library. That's the question I tackle in part seven of my event sourcing series:
https://www.planetgeek.ch/2026/05/26/event-sourcing-why-we-built-our-own-library/

I'll look back at our architectural decisions when we started over 10 years ago and how we likely would decide in today's landscape.

#EventSourcing #fsharp #dotnet

Event Sourcing: Why we built our own “library”

During my series on event sourcing, I got a question a couple of times: "Why don't you use an event sourcing library? Why have you built your own kind of library?" So part seven is about the trade-offs of using out-of-the-box libraries versus building your own - even today. When we started When we started...

planetgeek.ch

reposting for any who missed it previously:

Proposal: Open Source Maintenance Fee for Verify

https://github.com/orgs/VerifyTests/discussions/1731

#dotnet

Proposal: Open Source Maintenance Fee for Verify · VerifyTests · Discussion #1731

The Verify project is considering adopting the Open Source Maintenance Fee (OSMF), and we'd like to open it up for discussion before committing to anything. Verify has been freely available since 2...

GitHub
@Migueldeicaza are you still involved with https://gui-cs.github.io/Terminal.Gui/ because the instructions on that page don't help.
It installs some v1 version and the tui-simple template is not available. Manually specifying the v2 also does not help. #dotnet #tui
Terminal.Gui - Cross Platform Terminal UI Toolkit for .NET | Terminal.Gui v2

Content Pipeline в MonoGame: почему я его не использую

Введение Content Pipeline — это официальный способ работы с ассетами в MonoGame. Однако в сообществе уже давно существует немалая группа разработчиков, которые его не любят и предпочитают загружать ассеты в «сыром» виде. Особенно это заметно в сообществе FNA(ещё одной реализации XNA4) — там такой подход используют практически все. Я тоже давно в этой «партии» и в этой статье объясню, почему…

https://habr.com/ru/articles/1039344/

#gamedev #csharp #dotnet #monogame

Content Pipeline в MonoGame: почему я его не использую

Введение Content Pipeline — это официальный способ работы с ассетами в MonoGame. Однако в сообществе уже давно существует немалая группа разработчиков, которые его не любят и предпочитают загружать...

Хабр

i built a thing https://github.com/SimonCropp/GeoConvert

Convert maps between geospatial formats, with no third-party dependencies #dotnet

GitHub - SimonCropp/GeoConvert: Convert maps between geospatial formats, with no third-party dependencies

Convert maps between geospatial formats, with no third-party dependencies - SimonCropp/GeoConvert

GitHub
Two releases of #ILSpy today: v10.1 with #dotnet 11.0 runtime-async support https://github.com/icsharpcode/ILSpy/releases/tag/v10.1 and version 1.0 of our #vscode extension https://github.com/icsharpcode/ilspy-vscode/releases/tag/v1.0.0
Release ILSpy 10.1 · icsharpcode/ILSpy

WarningWe DO NOT own the domain ilspy[.]org See #3709 Download ILSpy only from GitHub Releases! This release is based on .NET 10.0. Please make sure that you have it installed on your machine befo...

GitHub
🚨 Microsoft just open-sourced something every .NET developer using AI tools should pay attention to. The dotnet/skills repo went public on GitHub. It's a curated set of reusable engineering skills… | Mukesh Murugan | 18 comments

🚨 Microsoft just open-sourced something every .NET developer using AI tools should pay attention to. The dotnet/skills repo went public on GitHub. It's a curated set of reusable engineering skills that AI coding agents (Copilot, Claude, Gemini, Codex) can load on demand to write better, more consistent .NET code. I've been running my own skills setup for months. Custom CLAUDEmd files, project-specific commands, repeatable workflows for writing, reviewing, and refactoring code. It works really well. But it's mine. Nobody else on the team gets to use it. That's what changes now. 𝗪𝗵𝗮𝘁'𝘀 𝗮𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝗶𝗻 𝗶𝘁: • Skills for aspnetcore, Aspire, Orleans • AI + Agents patterns • Testing, Architecture, Migrations • Works with any agentic AI tool, not just Copilot 𝗪𝗵𝘆 𝘁𝗵𝗶𝘀 𝗺𝗮𝘁𝘁𝗲𝗿𝘀: Most AI prompts in .NET projects get written from scratch every single time. Same context, same examples, same patterns. Typed into the chat over and over. Skills flip that. The knowledge lives in the repo, the agent loads what it needs, and your code stays consistent across the team. No more "perfect prompt" trials. This is the same approach that has been quietly winning in the Claude Code and Cursor communities. Microsoft is now making it native to the .NET ecosystem. If you ship .NET code with AI in the loop, this becomes the foundation you build on top of. Repo linked in the comments. | 18 comments on LinkedIn

LinkedIn
Introducing Syncfusion Toolkit for Blazor: Free Open-Source Blazor Components | Syncfusion Blogs

We’re thrilled to launch the Syncfusion Toolkit for Blazor, a free, open-source, MIT-licensed collection of reusable Blazor UI components.

Syncfusion

Automatically getting API difference diagrams in your .NET PRs | by Morten Nielsen

https://xaml.dev/post/automatically-getting-api-difference-diagrams-in-your-net-prs

#dotnet #csharp #apis #github #pullrequests

dotMorten | Automatically getting API difference diagrams in your .NET PRs

dotMorten - .NET Ramblings, XAML hacking and some GIS endeavors - A while back I built a tool that could analyze .NET Source Files as well as assemblies, and generate

Dew Drop – May 25, 2026 (#4675) – Morning Dew by Alvin Ashcraft