dotnet-scaffold-service

To scaffold a dotnet domain service, this tool generates a reusable logic-service skeleton with an interface, internal sealed implementation, and optional models following the Umbrella ServiceBase pattern. It handles complex domain logic by wiring dependencies and Lazy<T> repository injections automatically.

Setting up Lazy<T> repository injection is handled by generating an internal sealed service class that implements a public interface. The scaffolded implementation follows the Umbrella ServiceBase pattern, automatically wiring Lazy<T> repository dependencies for efficient domain service initialization.

Yes, this dotnet service scaffolding enforces Core.Logic boundaries and respects non Web references. It generates domain services within Core.<AppName>.Core.Logic, ensuring clean architecture separation by preventing improper web project dependencies in your logic layer.

To generate DI registration extensions, the scaffolder creates or updates IServiceCollectionExtensions.cs. This automatically wires your newly generated domain services and their Lazy<T> repository dependencies into the dotnet dependency injection container.

You create optional models under Services\<Domain>\Models when your domain service requires dedicated data transfer objects. The scaffolder generates these alongside the interface and internal sealed implementation to support complex logic operations beyond simple CRUD.

No, this scaffolder is specifically designed for Umbrella Core.Logic projects. It generates service skeletons implementing the Umbrella ServiceBase pattern with specific DI wiring and Lazy<T> repository integration, making it unsuitable for standard CRUD services outside this architecture.