IEndpointFilter en Minimal APIs
El "envoltorio" del handler โ
Ejecuta lรณgica ANTER y DESPUES (logging, auth, mรฉtricas, headers) sin ensuciar tu endpoint.
Before โ Handler โ After
๐ฅ #dotnet#aspnetcore#minimalapi
Probably because devs using Server are happily employed and aren't ranting on X about SPA frameworks. WASM makes for good discussions. I could see SSR Htmx/DataStar eventually being adopted more than WASM. Devs yearn for Razor what MinimalAPI did to Controllers. MinimalBlazor?
๐ Your daily dose of .NET is here! Issue #318 covers easier Span<T> conversions in C# 14 โก, an EF Core Performance Challenge to go 233ร faster ๐, Migrating from MVC to Minimal APIs ๐, and 10 Mind-Blowing C# Record Features ๐ง . Pause, reflect, and sharpen your skills with the wisdom only an experienced dev can appreciate! ๐
dotnetnews.co/archive/the-neโฆ#dotnet#csharp#efcore#minimalapi#performance#records
๐ต ๐๐ก๐ ๐๐๐ฌ๐ฎ๐ฅ๐ญ ๐๐๐ญ๐ญ๐๐ซ๐ง: ๐ ๐๐ฆ๐๐ซ๐ญ๐๐ซ ๐๐๐ฒ ๐ญ๐จ ๐๐๐ง๐๐ฅ๐ ๐ ๐๐ข๐ฅ๐ฎ๐ซ๐๐ฌ
Nested try-catch blocks, unreadable logs, no status code return and unclear return paths make debugging a painful experience. But what if there was a simpler, cleaner, and more predictable way to deal with failures?
The Result Pattern offers just that. Instead of relying on exceptions for flow control, it embraces explicit success and failure outcomes, making your code easier to read, test, and maintain.
๐ฌ ๐๐ฒ ๐ญ๐๐ค๐? Since I adopted the Result Pattern in APIs and services, Iโve seen better maintainability, clearer contracts, and more confidence in error handling.
Itโs not just functional programming hype: it works.
What about you? Have you implemented the Result Pattern in your codebase?
โค๏ธ Like if this was helpful
๐ฌ Drop your thoughts below
๐ Share with someone tired of chaos
#dotnet#csharp#webapi#cleancode#resultpattern#errorhandling#programming#developerlife#softwarearchitecture#backend#restapi#minimalapi#aspnetcore#cleanarchitecture
Whatโs .NET?
In our latest demo, We break down how to build modern APIs in .NET both Minimal and Controller-based.
Fast. Scalable. Cloud-ready.
Learn how the two approaches compare and when to use each.
#CSharp#APIs#Developers#MinimalAPI#ControllerAPIyoutu.be/1E5JgftUIwM
๐ต ๐ ๐๐ฅ๐จ๐ ๐ฌ ๐ญ๐ก๐๐ญ ๐ข๐ฆ๐ฉ๐ซ๐จ๐ฏ๐๐ ๐ฆ๐ฒ .๐๐๐ ๐๐จ๐๐ โ ๐๐จ๐ซ ๐ซ๐๐๐ฅ
If you're a backend or full-stack dev working with .NET, these articles were written with you in mind.
Over the past few months, Iโve shared 8 blog posts packed with lessons from real-world projects, each one packed with clean code tips, architectural insights, and code samples that you can use right away.
1 - How to Generate Fake Data for Automated Tests Using Bogus
(pedrocons.com/how-to-generatโฆ)
2 - Central Package Management in .NET: A Must-Have for Scalable Projects
(pedrocons.com/central-packagโฆ)
3 - What Is Vertical Slice Architecture and Why Should You Care?
(pedrocons.com/what-is-verticโฆ)
4 - Global Exception Handling in .NET โ Why You Canโt Ignore It
(pedrocons.com/global-exceptiโฆ)
5 - Why Most Developers Get Minimal API Structure Wrong (And How to Fix It)
(pedrocons.com/why-most-develโฆ)
6 - Why .NET Developers Are Saying Goodbye to Controllers and Embracing Minimal APIs โ And You Should Too
(pedrocons.com/why-net-develoโฆ)
7 - What Is the Options Pattern in .NET and Why Should You Use It?
(pedrocons.com/what-is-the-opโฆ)
8 - How to Boost Your .NET Apps with Fluent Validation (Step-by-Step Tutorial)
(pedrocons.com/how-to-boost-yโฆ)
No fluff. Just sharp solutions to common problems.
๐ฌ Which topic should I dive deeper into with code walkthroughs?
โค๏ธ Like if one of these saved you some time
๐ Repost to help others write better .NET apps
#DotNet#CSharp#CleanCode#MinimalApi#AspNetCore#Testing#Architecture#VerticalSlice#FluentValidation#OptionsPattern#SoftwareEngineering