How fullstackproltd/aspnetcorespa works
Project Type & Purpose
• This is a full‐stack web application built on ASP.NET Core 7.0 using a Clean Architecture style.
• It exposes two backend services:
• “Web” – an ASP.NET Core Web API hosting an Angular 15 Single Page Application (SPA) under /ClientApp, SignalR hubs, and controllers for business data.
• “STS” – an ASP.NET Core IdentityServer4 application that handles authentication/authorization (OpenID-Connect/OAuth2).
• Core domain/business logic is in the Core projects (Domain, Application, Common). Infrastructure implements persistence, identity, email, file builders.
High‐Level File Structure & Architectural Patterns
• src/Core
• Domain: Entities and aggregates.
• Application: Mediator (CQRS) handlers, abstractions (IApplicationDbContext, IEmailService, etc.), cross‐cutting behaviors (logging, validation).
• Common: shared constants, mappings, result models.
• src/Infrastructure
• Persistence: EF Core DbContexts (ApplicationDbContext, LocalizationDbContext, IdentityServerDbContext), migrations, configurations.
• Identity: IdentityServer4 store entities.
• Email, Files (CsvFileBuilder), Certificate services (KeyVault).
• Custom middlewares & extensions.
• src/Presentation
• STS: IdentityServer host with Razor Pages UI for account management, custom profile service, security headers, Dockerfiles.
• Web: API controllers, SignalR hubs, Angular SPA (under ClientApp), middlewares, Dockerfiles.
• tests: Integration tests for Web API and unit tests for controllers.
a. Main Components
1. Angular SPA (ClientApp)
2. Web API service (Presentation/Web)
3. IdentityServer (Presentation/STS)
4. Core (Domain + Application layers)
5. Infrastructure services
– ApplicationDbContext (SQL Server/SQLite)
– LocalizationDbContext
– IdentityServerDbContext
– EmailService (SMTP or external provider)
– KeyVaultCertificateService
6. External dependencies (Databases, Key Vault, SMTP, Azure/Heroku, Docker)
b. Relationships & Data Flows
• User browser → Angular SPA
• SPA → Web API endpoints (HTTP/REST)
• SPA → STS for login (OIDC redirect)
• Web API ↔ IdentityServer (token validation via introspection or JWKS)
• Web API → ApplicationDbContext & LocalizationDbContext (EF Core)
• STS → IdentityServerDbContext (EF Core)
• Backend services → EmailService & CertificateService
• All services optionally containerized via Docker Compose or deployed to Azure/Heroku
c. Architectural Patterns & Principles
• Clean Architecture / Onion Architecture:
• Outer layers (Presentation) depend inward only on Application layer abstractions.
• Infrastructure sits at the perimeter implementing Application interfaces.
• CQRS with Mediator for commands & queries
• Domain Entities in Core.Domain
• Dependency Injection throughout
• Cross‐cutting concerns (logging, validation) via pipeline behaviors and middlewares
• Micro‐frontends / multiple hosts separated for security (STS vs Web)
d. Key Technologies & Frameworks
• ASP.NET Core 7.0, IdentityServer4, Entity Framework Core 7.0
• Angular 15 + CLI, SignalR, SASS, PWA support
• Docker & Docker Compose, Azure App Service, Heroku Container Registry
• Jest & Protractor for front-end tests, xUnit/MSTest for back-end tests
• Swagger (Swashbuckle) for API exploration