How gmendozas/easyactivities works
Project Type and Purpose
• This is a full-stack .NET “EasyActivities” suite for recording working activities.
• It consists of:
• A WPF desktop client (ClienteActividades)
• An ASP.NET Web API backend (ServicioActividades)
• A shared data-access library (RepositorioDB)
• A MongoDB database
• External geolocation service (Google Maps Location Services)
File Structure Analysis
• Top-level solution (ServicioActividades.sln) contains three projects:
a. ClienteActividades (WPF application)
• UI layer: App.xaml, MainWindow.xaml
• References GoogleMaps.LocationServices, MongoDB.Driver, Newtonsoft.Json
b. RepositorioDB (Class library)
• Contracts: IActividadRepositorio
• MongoDb folder: BaseRepositorio, Entidades (domain models), Repositorios (implementations)
• Uses MongoDB C# driver
c. ServicioActividades (Web API)
• Controllers: ActividadesController, ColaboradorController
• Models: Actividad, Colaborador
• Configuration in WebApiConfig.cs, Web.config
• References RepositorioDB, MongoDB.Driver, Newtonsoft.Json
README Insights
• “Suite to record working activities” confirms the workflow:
Client UI captures activity data → sends to Web API → persists via repository → stored in MongoDB.
Main Components
a. WPF Client
b. ASP.NET Web API Server
c. RepositorioDB Library
d. MongoDB Database
e. Google Maps Location Services (external API)
Relationships and Data Flow
• Client → (HTTP/REST) → Web API Controllers
• Controllers → (calls) → IActividadRepositorio in RepositorioDB
• Repository implementations → (MongoDB C# Driver) → MongoDB
• Client → (Google Maps SDK) → External Geolocation Service
Architectural Patterns and Key Technologies
• Client: MVVM-style WPF (.NET Framework 4.x), uses GoogleMaps.LocationServices library
• Service: ASP.NET Web API (REST), Controllers → Models → Repository
• Repository: Repository pattern abstracted via IActividadRepositorio, implemented with MongoDb driver
• Data store: MongoDB NoSQL
• JSON serialization: Newtonsoft.Json
Detailed Capture of Essential Elements
• Controllers invoking IActividadRepositorio
• Entity classes (Actividad, Colaborador) flowing through layers
• Config files only as a note (e.g., Web.config for connection strings)