Priority: P0 (Foundation)
Problem
The CLI migration pipeline ignores Web.config registrations of custom controls. This blocks prescan from detecting ASCX files and custom assemblies.
Scope
- Parse Web.config and sections
- Extract assembly registrations and namespace tags
- Integrate with RuntimeDetector for prescan reporting
Deliverables
- WebConfigAssemblyParser class in src/BlazorWebFormsComponents.Cli/Analysis/
- Integration into RuntimeDetector
- Prescan output includes 'Custom Controls Found' section
- Unit tests: tests/BlazorWebFormsComponents.Cli.Tests/Analysis/WebConfigAssemblyParserTests.cs
- Integration test with WingtipToys/ContosoUniversity prescan
Acceptance Criteria
✅ Parser correctly extracts assembly/namespace from Web.config
✅ Prescan lists detected custom controls
✅ No crash on missing/malformed Web.config
✅ Unit tests pass
✅ Prescan works on WingtipToys and ContosoUniversity
Related Track Document
See dev-docs/control-migration/track-webconfig-parser.md
Priority: P0 (Foundation)
Problem
The CLI migration pipeline ignores Web.config registrations of custom controls. This blocks prescan from detecting ASCX files and custom assemblies.
Scope
Deliverables
Acceptance Criteria
✅ Parser correctly extracts assembly/namespace from Web.config
✅ Prescan lists detected custom controls
✅ No crash on missing/malformed Web.config
✅ Unit tests pass
✅ Prescan works on WingtipToys and ContosoUniversity
Related Track Document
See dev-docs/control-migration/track-webconfig-parser.md