How santicaceres1/centroeventos works
Project type and purpose
• This is a full-stack .NET 8 application using Clean Architecture for managing university sports events, users, reservations, and attendance.
• The layers are clearly separated: a Blazor UI (CentroEventos.UI), a pure business-logic layer (CentroEventos.Aplicacion), and an EF-based persistence layer (CentroEventos.Repositorios).
File structure
• Top-level solution file (CentroEventos.sln) orchestrates three projects.
• CentroEventos.Aplicacion (“Application”):
• Entidades (domain objects)
• CasosDeUso (use-case classes implementing business rules)
• Repositorios (interfaces)
• Servicios (authentication, authorization, hashing)
• Validadores and Excepciones (validation logic)
• CentroEventos.Repositorios (“Infrastructure”):
• EF Core DbContext and repository implementations for EventoDeportivo, Persona, Reserva, Usuario.
• CentroEventos.UI (“Presentation”):
• Blazor components and pages (.razor), appsettings, static assets, Program.cs for DI.
• SQLite file for local persistence.
Key insights from README
• Confirms Clean Architecture: UI → Application → Repositories.
• Persistence uses plain text files in console version, but the UI uses EF/SQLite.
• Business rules (no over-booking, no deleting entities with dependent data, etc.).
• Authentication/authorization via IServicioAutorizacion and permissions.