one-modernizer demo evidence
A compact visual summary of the generated migration evidence for the Catalog Item Management slice: graph discovery, assessment, spec, architecture, implementation, and validation.
The validation report records a real GitLab CI build as proven, 100% rule/flow/test/data/error coverage, and remaining production follow-ups around EF migrations and environment-level testing.
demo/eShopModernizing/eShopLegacyMVCSolution/.migration/validate/catalog-item-management/report.md
One cohesive feature from the Microsoft eShopModernizing sample: Catalog Item Management, a CRUD-heavy ASP.NET MVC 5 / EF6 slice with service, domain, data, view, image, and framework coupling.
Each stage consumed the previous output. The point is not one big prompt; it is an evidence chain that stays inspectable.
Graphify scanned the legacy MVC source and produced graph navigation.
Feature inventory selected Catalog Item Management as the demo slice.
Rules, flows, data structures, tests, errors, and unknowns were extracted.
Target service, ADRs, mappings, and deployment shape were defined.
A .NET 8 ASP.NET Core MVC + EF Core solution was generated.
Build, contracts, traceability, and quality gates were checked.
The decomposition stage turned legacy behavior into a migration contract for the generated target.
The architecture keeps this migration as a single catalog service: ASP.NET Core MVC, EF Core 8, SQL Server/Azure SQL, Docker, and observability/security follow-ups surfaced as ADRs.
catalog-service Controllers/CatalogController.cs Services/ICatalogService.cs Services/CatalogService.cs Models/CatalogItem.cs Models/CatalogDBContext.cs Views/Catalog/*.cshtml Dockerfile + docker-compose.yml openapi.yaml
The useful part of the demo is that every claim can point back to a file. These are the raw artifacts behind the summary.
Corpus size, graph stats, hubs, and extraction quality.
Open GRAPH_REPORT.mdFeature ordering, strategy, risks, and open decisions.
Open migration-sequence.mdExtracted rules, flows, test cases, and unknowns.
Open summary.mdTarget platform, ADRs, mapping completeness, and structure.
Open architecture summaryThe generated .NET 8 catalog solution and its README.
Open target READMEStatic Pages wiring for the presentation bundle and published demo evidence.
Open root .gitlab-ci.ymlThe generated .NET 8 build, test, and package stages used when local restore/build was blocked.
Open catalog .gitlab-ci.ymlBuild verdict, spec coverage, contracts, quality, and follow-ups.
Open report.mdIt is not a dramatic payment system. It is a realistic enterprise tangle: EF6 queries, HiLo key allocation, view models, images, config-driven mock vs SQL service selection, and System.Web MVC coupling. That makes it a good modernization demo because the risk is in seams and evidence, not in invented domain theater.
Re-run full tests on a Windows/.NET SDK host, generate EF Core migrations, and decide on production hardening such as request DTOs, authentication, optimistic concurrency, and validation strategy.