How josesepulvedavelez/focalizacionexcel works
Project type and purpose
• This is a full‑stack .NET solution named “PapsiviFocalizacion,” consisting of a Blazor web front‑end, a .NET Web API back‑end, a Core/domain library, and an Infra/data‑access layer.
• Purpose: manage “focalización” data (departments, ESEs, municipalities, resolutions, users, registrations) and provide both administrative and reporting UIs.
File structure
• Top‑level solution (PapsiviFocalizacion.sln) contains four main projects:
• PapsiviFocalizacion.Web – Blazor WASM/Server UI (Pages, Shared, DTOs/Models, wwwroot assets)
• PapsiviFocalizacion.Api – ASP.NET Core Web API (Controllers, appsettings, Program.cs)
• PapsiviFocalizacion.Core – Domain/Business layer (Models, DTOs, repository interfaces)
• PapsiviFocalizacion.Infra – Infrastructure layer (Repository implementations, EF Core or ADO to SQL scripts)
• There are database scripts (1 Creacion de tablas.sql) and sample data. Configuration files live under each project (launchSettings.json, appsettings.json).
Detailed capture of essential elements
• How DTOs travel from client → API → Core → Infra → DB and back
• Configuration (appsettings.json) feeding into API and Web projects
• Solution file (.sln) as an overview entry point if useful
• Call out sample‑data and external calls (weather.json) as secondary services
Putting it all together:
[Browser / Blazor UI]
↓ HTTP
[ASP.NET Core Web API]
↓ DI resolves
[Core / Domain Interfaces & Models]
↓ Implementation
[Infra / Repository Layer]
↓ SQL
[Database (SQL Server)]