Where should helper classes like TypeHelper, StringHelper etc be?

[prince272]

Should helper classes be inside the Core project or the Infrastructure project?

[prince272]

I just wanted to know how well you''ll be able to organize NopCommerce files using this CleanArchitecture Template.

[Xeinaemm]

Code without external dependencies - core, but more likely you should create a shared library to keep reusable code and then link this as a dependency.

Something like this:

CleanArchitecture/src/CleanArchitecture.Core/CleanArchitecture.Core.csproj

Line 9 in 95083ac

<PackageReference Include="Ardalis.GuardClauses" />

From my perspective - I'm splitting Core into Contracts, Domain, Messages. Infrastructure into Persistence, Application, Application.Setup, Message broker. Web into UI, API(ie. API, ReadApi, PresentationApi).

Core

• Contracts - basic models, DTOs, the definition of endpoints for API.
• Messages - models as above but for Message Broker.
• Domain - domain models that hold business logic in entities and value objects without EXTERNAL implementation. Just domain, root objects, etc.

Infrastructure

• Application - implementation of business logic, CQRS that can handle commands and change domain by commands which base on external resources(other API).
• Application.Setup - just setup to run a whole application like Autofac setup.
• Persistence - mapping of views, tables from DB
• Message Broker - CQRS implementation of handlers and system that run message broker service (write mode)

Web

• API - POST Actions that invoke CQRS and then message broker(yep, next CQRS system)
• ReadAPI - internal/external definition of data that your or any system can get
• PresentationApi - internal read data for UI.

I just want to mention - most shareable code like CQRS, DDD base implementation that is the root of everything is from a shared library. You will not find this in the description above, but if you want to place this somewhere it would be core and shared folder.

[ardalis]

I'd agree with @Xeinaemm