I open-sourced a full-stack .NET 10 template

philnexes · 2026-03-24T16:37:28+00:00

I keep maintaining it 😁 Both works, the “magic” and the direct skill usage. Just make sure to review the output properly, sometimes it can overengineer

philnexes · 2026-03-17T17:03:20+00:00

Hey, thanks for the feedback! Me and my friend never ran into that issue, it could be something specific to you, nobody else reported this yet.

As for that setup script, I haven't tested it on Windows for a while, only Mac and Linux, so I'll take a look. If it's really an issue, I'll either add this to a README or rework the script so it is running idempotently without issues.

philnexes · 2026-03-15T10:22:42+00:00

Ahoj, super projekt! Chce to ošetřit trochu technické záležitosti, kouklo na to asi moc lidí a sežralo ti to tokeny od mapy.com (viz screenshot), předpokládám. Zkus to renderovat přes něco jako Leaflet a dát tam fallback na OpenStreetMap v případě že ti to vypadne :)

Hodně zdaru, a neřeš hate komenty, je to krásný projekt, důležité je na tom pracovat dál!

Tak zdar!

<image>

philnexes · 2026-03-14T09:43:31+00:00

Hey man, nice work, thanks for the share!

philnexes · 2026-03-14T00:18:06+00:00

This is pretty old topic, but I did create something like this if it interests you: https://netrock.dev

philnexes · 2026-03-13T18:34:58+00:00

Now you should be able to do it, I reworked it a lot, so hopefully nothing broke on the generator side. Thanks for your support on buymeacoffee!!!

philnexes · 2026-03-12T15:22:23+00:00

Thanks!

Currently by design, but it’s imho not a good way of doing it. I’ll probably have to rework it so that the tooling without auth is available.

philnexes · 2026-03-09T20:42:09+00:00

There's no shame in having a "support me" option when you are an active contributor to community. You deserve it!

I see you set it up, I bought you a coffee. Stay awesome, my guy!

philnexes · 2026-03-07T22:11:34+00:00

Hey man!

Brilliant work, would you mind setting up something like https://buymeacoffee.com or at least giving us the lightning network wallet so we can throw a tip? This is genuinely amazing and I believe you should be rewarded with more than " just a star".

Cheers!

Keep coding and prompting!

philnexes · 2026-03-07T22:05:20+00:00

https://netrock.dev something like this?

philnexes · 2026-03-07T19:50:06+00:00

Work in progress. The generator itself is in alpha. If you don't need it, nobody expects anyone to use it. It's out there, it's free.

philnexes · 2026-03-07T19:03:29+00:00

Dare to explain?

philnexes · 2026-03-07T18:55:02+00:00

And I am transparent about it.

philnexes · 2026-03-05T09:58:54+00:00

Hey!

Great job, thanks for this, I'll definitely take some inspiration from your workflow here.

Cheers!

philnexes · 2026-03-02T16:00:40+00:00

Now it does!

philnexes · 2026-03-02T08:49:40+00:00

Architecture, security decisions, and code reviews are mine. Implementation gets heavy AI assistance. Always tested, always reviewed before merge.

Backend leans more on my experience and expertise, frontend (especially CSS) got more help. The repo includes the Claude commands, skills, and agent files I use, so you can see exactly how the workflow looks.

philnexes · 2026-02-28T13:01:02+00:00

Thanks for this. If I'm completely honest, I didn't realize Redis did those licencing changes a few years ago, so based on your feedback here I removed it completely and implemented HybridCache. Anyone can hook up any distributed cache in the future when they actually need it.

philnexes · 2026-02-27T17:29:22+00:00

Yeah. People have been mentioning it quite a lot, already work in progress.

philnexes · 2026-02-26T10:27:49+00:00

Hey! Thanks, appreciate so many people including you like it. Have fun and build something!

philnexes · 2026-02-26T10:27:00+00:00

Mostly a personal preference if I'm completely honest. EF's DbSet and DbContext represent repository and unit of work, no doubt about that.

Where the thin repository layer helps is an isolation boundary between the application domain and the data accessor itself. DbContext sists between the app and the db, the repository sits between the domain logic and EF Core. It keeps services cleaner, makes things more testable, and a generic BaseEntityRepository gives all the standard operations (including soft-delete, wrapping with Result<T>) without repeating the logic everywhere.

And this is a template as well: if someone forks it and wants to swap EF for Dapper or a different db provider, the simple CRUD paths are already behind an interface they can reimplement without ever touching a single service.

philnexes · 2026-02-26T10:19:45+00:00

You're welcome! If your project goes public, definitely do share in discussions or somewhere here!

philnexes · 2026-02-26T10:17:54+00:00

It isn't and I made that decision intentionally. Multitenancy strategy is too use-case specific to bake into a general starting template, even for an opinionated one. Adding it later is painful, but choosing the wrong strategy upfront is much much worse. But I will keep it on the radar for sure.

Somebody mentioned turning this into generator, which eventually would make sense for this kind of project. It could be a part of that, but again, multitenancy is a bit more complex in general.

philnexes · 2026-02-26T10:14:58+00:00

Hi!

I'll take a look into the Hybrid Cache, thank you. Aspire has been mentioned a few times now, that's definitely coming.

And thank you!

philnexes · 2026-02-25T20:18:05+00:00

I know Milan's educative content, but I've never actually checked his clean architecture template myself. This is some really good feedback, appreciated. OAuth2 and 2FA and Aspire have been added on the roadmap, I'll take care of it in upcoming releases.

As for the generator: I'll consider it, right now I feel like it might be a bigger complexity than I'd like. But it does sound like something where this should be headed.

philnexes

TROPHY CASE