How rthworyt/empleossur-desarrollo works
Project type and purpose
• This is a full-stack ASP.NET Core 6.0 Razor Pages application called “EmpleosSur,” a job-board platform.
• It follows a layered (onion/hexagonal) architecture:
– Core layer: domain entities and interfaces
– Infrastructure layer: EF Core DbContext, migrations, repositories
– Application layer: business-logic services
– Web layer: Razor Pages, controllers, DTOs, static assets
File structure
• Top-level solution file (EmpleosSur.sln) with four projects:
– EmpleosSur.Core: Entities (Candidato, Empleo, Empresa, Usuario, etc.), helper classes, repository & service interfaces
– EmpleosSur.Infrastructure: Data folder (EmpleosSurDBContext), EF Core migrations, concrete Repository implementations
– EmpleosSur.Application: Service implementations (CandidatoService, EmpleoService, PagoService, etc.) that coordinate repositories and enforce business rules
– EmpleosSur.Web: Razor Pages UI and minimal Controllers/DTOs; Program.cs and appsettings for startup configuration; wwwroot for CSS/JS/Bootstrap assets
• Recognize patterns:
– Dependency inversion: Application and Infrastructure depend on Core interfaces
– Repository pattern for data access
– Service layer for use-case orchestration
– Razor Pages + MVC Controllers for presentation
README
• The README simply contains “Yes.” No additional architecture notes. Rely on the file tree for insights.
Detail without overthinking
• Service and repository as sub-components under their layers