How sandip124/expensetracker works
Project Type and Purpose
• ExpenseTracker is a full-stack ASP.NET Core solution for managing incomes and expenses across multiple workspaces.
• It provides both a server‐rendered MVC web application and a RESTful Web API alongside core business logic and data access layers.
• The README confirms its goal: create workspaces and manage transactions (CRUD, reporting, budgets).
File Structure Analysis
• Top‐level solution file: ExpenseTracker.sln.
• src folder contains six projects, each representing a layer or component:
• ExpenseTracker.Common – shared helpers (pagination, transaction scope) and generic repository interface.
• ExpenseTracker.Contracts – DTO definitions for request/response messages.
• ExpenseTracker.Core – domain entities, DTOs, exceptions, service/repository interfaces, business logic implementations.
• ExpenseTracker.Infrastructure – EF Core DbContext, migrations, repository implementations, configuration, logging adapters.
• ExpenseTracker.Web – ASP.NET Core MVC web app (views, controllers, view models, services, middleware, DI setup).
• ExpenseTracker.WebApi – ASP.NET Core Web API (controllers, middleware, DI, response wrappers).
• tests folder holds unit tests for entities and core services.
Architecture Insights
• Layered architecture (Presentation → Application/Service → Domain → Infrastructure/Data).
• Dependency injection (DiConfig classes in Core, Infrastructure, Web, WebApi).
• Repository pattern with generic and specific repositories.
• Contracts project enforces clear data exchange formats.
• Two frontends leverage the same core/infrastructure: MVC web UI and REST API.