// the find
dotnetcore/Util
Util是一个.Net平台下的应用框架，旨在提升中小团队的开发能力，由工具类、分层架构基类、Ui组件，配套代码生成模板，权限等组成。
Full-stack .NET application framework aimed at Chinese mid-size dev teams. It bundles DDD base classes, EF Core repositories, Angular/NgZorro UI generation via C# TagHelpers, code generation, multi-tenancy, and a grab-bag of third-party integrations (Dapr, Quartz, Hangfire, Serilog, MinIO) under one umbrella. The core pitch is that a single .NET developer can own both the API and the Angular frontend without switching mental models.
The TagHelper-to-Angular pipeline is the standout feature: write strongly-typed C# Razor, get Angular/NgZorro components with Lambda expression binding that auto-extracts names, validation attributes, and model binding — eliminating a whole class of form wiring boilerplate. DI auto-registration via ISingletonDependency, IScopeDependency, ITransientDependency marker interfaces is clean and familiar, same pattern as ABP but lighter. The 50+ NuGet packages are genuinely modular — you can take Util.Domain without dragging in the UI stack. DDD scaffolding (AggregateRoot, Repository, domain events, tree structure support with EF Core) is solid groundwork for teams who want the pattern without building it from scratch.
IdentityServer4 is EOL — the successor is commercial (Duende). The README acknowledges this and calls it 'stable for now,' which is a liability for any project that needs token issuance. The documentation is almost entirely Chinese with no usable English README; if you don't read Chinese you cannot evaluate the framework's conventions without reading source code. Last push was October 2024 — nearly a year of silence for a framework that needs to track ASP.NET Core releases, and .NET 9/10 compatibility is unclear. The Dapper integration is explicitly flagged as incomplete in the README itself: no pagination, no Lambda query support, and it's currently only used for code generation metadata reads — so complex queries outside EF Core leave you stranded.