Two Reports.
One Scan.

Point the analyzer at your solution folder and get a Technical Report for your developers and a Business Risk Report for your leadership – both as standalone HTML files you can open anywhere.

View Sample Technical Report → View Sample Business Report →

Technical Report

A dense, data-driven breakdown of your codebase – built for the engineers who'll do the migration work.

Codebase Inventory

Every .vb, .cs, .aspx, .ascx, .frm, and .vbp file counted, categorized, and measured. Lines of code per file, per project, and totals. Forms, controls, modules, and web pages inventoried separately.

Framework & Runtime Analysis

Target framework versions detected across all projects. Multi-targeting analysis. SDK version fingerprinting. Identifies projects stuck on .NET Framework 2.0, 3.5, or 4.x.

NuGet Dependency Audit

Every package.config and .csproj PackageReference scanned. Version compared against latest stable. Known CVE exposure flagged. Archived or abandoned packages identified.

Code Pattern Detection

Inline SQL queries, HttpContext.Current usage, global state, synchronous I/O patterns, missing error handling, and other migration-sensitive patterns detected and counted.

Module Size Analysis

Largest files by line count. Most referenced classes. Complexity hotspots. Circular dependency detection. God class identification (500+ line threshold).

Security Findings

Known insecure patterns: MD5/SHA1 for passwords, ViewState MAC disabled, stack traces in error pages, hardcoded credentials in config files. File and line number referenced.

Business Risk Report

Non-technical language, business-level risk framing. Built to land in a board deck or an IT steering committee.

Security Risk Dashboard

End-of-life frameworks, vulnerable library versions, and known CVE exposure windows. Color-coded severity. Compliance implications flagged for SOX, HIPAA, and GDPR contexts.

Developer Availability Risk

Technologies with shrinking talent pools analyzed. VB6 developers represent less than 0.1% of active developers. Web Forms less than 2%. Hiring cost and timeline projections.

Cost of Inaction Timeline

Year-by-year breakdown of what happens if migration is deferred. Framework EOL dates, support end dates, projected rate increases, and compliance deadline windows.

Modernization ROI Scenarios

Three migration paths – security hardening, partial modernization, full modernization – with effort estimates, risk reduction percentages, and 3-year savings projections.

Technical Debt Breakdown

Debt categorized by type: security, framework, code quality, and dependencies. Proportional breakdown shows where modernization effort will be concentrated.

Recommended Next Steps

Prioritized action list based on your specific codebase findings. Effort estimates for each step. Written for handoff to a project manager or engineering lead.

How It Works

1

Download the Analyzer

Free Windows EXE. No installation.

2

Point It at Your Code

Select your solution root folder.

3

Get Both Reports

Two HTML files appear in your output folder in under 5 minutes.