TodoApi VS FastEndpoints

Shameless plug https://github.com/davidfowl/TodoApi

This is a fairly common scenario (externalizing the authentication piece but still wanting app-local storage of some user information) that isn't well documented (we're working on that). You might try taking a look at this app by u/davidfowl that supports what you're asking about: https://github.com/davidfowl/todoapi

Good news: David Fowler has a full showcase repository TodoApi

ASP.NET Core Identity.However, most examples use Identity with the MVC/Blazor. I need to support both a SPA and a mobile app and I am not sure if that is the recommended approach here.(Perhaps I should use the backend for frontend approach like David Fowler showcases in https://github.com/davidfowl/TodoApi ?)

Throwing mine in the ring https://github.com/davidfowl/TodoApi/

Example at https://github.com/davidfowl/CommunityStandUpMinimalAPI/blob/main/TodoApi/Program.cs

A basic example looks like: https://github.com/davidfowl/CommunityStandUpMinimalAPI/blob...

Some more documentation on integration tests: https://learn.microsoft.com/en-us/aspnet/core/test/integrati...

Pre .NET 6, there's a Startup.cs file that is used to set these up. .NET 6+ just puts them in Program.cs by default, but you can still use a Startup.cs if you'd prefer. Example of the newer template in Program.cs is here

Bonus Time! In addition to the Microsoft-supported methods above, many community frameworks exist for building APIs with .NET. FastEndpoints is an option I found recently that seems very promising. With performance benchmarks that put them on par with Minimal API, they are firmly ahead of Controller-based APIs.

Have you had a look at FastEndpoints yet? Any thoughts?

And yet, all Microsoft's demos for the upcoming changes for Blazor in .NET 8 (like SSR) has been a public facing recipe site (e.g. https://www.youtube.com/watch?v=QD2-DwuOfKM). I'd say this is a very similar use case as the Microsoft Store.

I love .NET and ASP.NET Core, but I use it purely for backend. And even there, I use 3rd party libraries like Fast Endpoints (https://fast-endpoints.com/). Microsoft keeps bringing in new technologies and effectively abandoning the ones that fall out of favour (look at the progression from MVC -> Razor Pages -> Blazor). I do not blame the Microsoft Store team for not trusting the .NET team to not simply abandon Blazor as well somewhere down the line and instead opt for other technologies for the front-end.

I also find a very similar framework in .NET "Fast Endpoints"

I gave it a go and I was impressed how easy and fast it was to set it all up. Since I'm not a big fan of REPR pattern almost all my projects are using CQRS pattern with a help of MediatR ](https://github.com/jbogard/MediatR) I immediately started going over something similar that Fast Endpoints offer which is a command bus.

Ive personally been using FastEndpoints which is a community built thing on top of minimal apis - https://fast-endpoints.com/

I've just started to use a similar thing, and it's so much better than controllers - https://fast-endpoints.com/

Sort of minimal but check out FastEndpoint. https://fast-endpoints.com/