Result preview
dotnet/eShop
Sample structure
Web APIControllers + minimal routes
ApplicationServices and orchestration
InfrastructureAdapters, jobs, hosting
DataDbContext + entities
Snapshot
mainScanner brief
Architecture
Layered web API
A multi-project ASP.NET Core solution with web API boundaries, application services, EF Core persistence, integration messaging, and deployment assets.
Start hereeShop.sln - start with the full project graph.
ShapeLayered web APIPrimary solution: eShop
StartCatalog.APIOpen the solution, then inspect API entrypoints.
DataCatalogContext3 entities across EF Core contexts.
Runtime2 servicesPostgreSQL, Redis detected. Tests: Basket.UnitTests.
142 text files scanned; 9 projects; 34 endpoints; 1 DbContext
Solutions1Projects9Endpoints34Warnings3
Architecture Map
Scanner map
ProjectsTop 3
Catalog.APIWeb API
net8.0Microsoft.EntityFrameworkCoreSwashbuckle.AspNetCore
Ordering.InfrastructurePersistence
net8.0Npgsql.EntityFrameworkCore.PostgreSQL
Basket.UnitTestsTests
net8.0xunitFluentAssertions
APIsTop 3
GET/api/catalog/itemsCatalogControllerPOST/api/ordersOrdersControllerGET/healthProgram.csData Model1
CatalogContext
CatalogItemCatalogBrandCatalogType
Risks3
HighSecret-like text
Sample settings include values that look like credentials.
Confirm they are not live.MediumRuntime setup
Infrastructure wiring is split across Docker and launch settings.
Check local service requirements.LowREADME gap
Local database setup is not obvious from the scanned files.
Document the first run path.Onboarding Path
eShop.sln - start with the full project graph.
- Start with the solution file and identify API entrypoints.
- Read the application services before infrastructure adapters.
- Check appsettings and Docker Compose for required local services.