Legacy .NET modernization. With guardrails, not guesswork.

It depends on page count, control complexity, and how much logic lives in code-behind. Small internal apps move in weeks; a mid-size line-of-business app is typically a multi-month program — but sequenced as a strangler-fig migration, you ship converted sections continuously instead of betting on a big bang. The Readiness Assessment gives you a sprint-level estimate for your actual codebase, not a generic range.

Yes. Microsoft deprecated the free .NET Upgrade Assistant in late 2025 and now points teams at GitHub Copilot app modernization — which requires a paid Copilot plan (Pro, Business, or Enterprise). The old tool still exists behind a disabled-by-default setting in Visual Studio 2026, but it's no longer developed. That's the gap we fill: deterministic, human-verified migration work, with AI used for speed under engineering guardrails rather than as the decision-maker.

AI handles a real share of the mechanical work — package swaps, namespace changes, API substitutions — and we use it for exactly that, under guardrails that build- and test-gate every change. What it cannot do reliably is verify your business logic still behaves identically, untangle undocumented legacy patterns, or decide what should be redesigned instead of ported. Teams that ran an AI agent over a large legacy codebase usually describe the same result: 70% done, and the remaining 30% is the actual project. That last mile is what we do.

Both reach end of support on November 10, 2026 — after that, no security patches. .NET 10 is the current LTS, supported to November 2028. The 8-to-10 jump is usually mild (far easier than leaving .NET Framework), but 'usually' isn't a plan: dependencies, analyzers, and deployment images all need verification. If you're on 8 or 9 today, the upgrade belongs on this year's roadmap.

WCF never made the jump to modern .NET, but you have real options: CoreWCF covers most bindings and contracts for a low-friction port, while gRPC or REST is often the better target for services due a redesign anyway. The assessment maps every service to a target and flags the contracts that need special handling — message-layer security and exotic bindings are where the surprises live.

The entry point is a 1-hour session for $80 flat. The Modernization Readiness Assessment — a fixed-scope, one-sprint engagement — starts at $4,800, and the $80 session counts toward it if you proceed. Full migrations vary too much to price honestly on a webpage: simple ports land in the low tens of thousands, complex re-architectures run higher. That's exactly why the assessment exists — it produces a sprint-level estimate for your codebase that you can execute with us or any team.

No. Rewriting everything at once is how migrations fail. Common paths: keep the WebForms UI temporarily while the backend moves to .NET 10 behind an API (strangler-fig), convert forms-heavy screens to Blazor where the component model maps naturally, or go API-first and leave the UI decision for later. The right answer depends on how much of your risk lives in the UI layer — that's an assessment question, not a default.

If we can't help you within the first 15 minutes — whether because the problem is out of scope or we're not the right fit — we'll tell you, end the session, and refund the fee. We'd rather lose an hour than take your money for work we can't deliver.