How aneeshram-01/nzwalk works
Project type and purpose
• NZWalks is a full‑stack .NET application composed of:
a. NZWalk.UI – an ASP.NET Core MVC front‑end that renders views, serves static assets, and handles user interactions in the browser.
b. NZWalk – a .NET Web API back‑end that exposes REST endpoints for Regions, Walks, Images and Authentication.
• Its purpose is to let users register/log in, browse and manage hiking regions and walks, upload images, and persist data in SQL Server.
File structure
• Top‑level solution (NZWalk.sln) contains two projects:
• NZWalk.UI (MVC)
• NZWalk (Web API)
• NZWalk.UI folders: Controllers, Models/DTOs/ViewModels, Views (Razor), static assets (wwwroot/css, js, lib).
• NZWalk folders: Controllers, Models (Domain & DTO), Data (DbContexts), Mappings (AutoMapper), Repositories (interfaces + SQL/Local implementations), Middlewares, Migrations, CustomActionFilters.
• Configuration: appsettings.json, launchSettings.json.
Detail
• Both databases (app data vs. auth data).
• Call out custom filters and middlewares in the pipeline.
• Static content (CSS/JS) served by the UI.