FIELD NOTEBOOK  /  LEGACY .NET MIGRATION
DotNet Forward
VOL. 01 · p.03
PROJECT No. NET-10
STATUS · OPEN FOR Q3

Questions

Frequently asked questions

The deal-breakers, answered plainly. Anything missing? Raise it on a fit call.

Is AI-generated migration safe?

Safety is structural, not a promise. Every migration ships with characterization tests that prove the migrated code behaves identically to the original, and one senior engineer reviews and owns every change. AI is the accelerator, never the decision-maker.

Does my source code get sent to an AI provider?

This is the one to confirm with me directly. The exact data-handling policy is being finalized for launch. Options include working inside your environment for sensitive code and a written commitment on how tooling touches your repository. Bring it up early; I’ll give you a straight answer.

Will my application behave exactly the same?

That is the entire deliverable. Behavioral parity is captured in an automated test suite and is the acceptance criterion. The migration is “done” when that suite passes green against the new code.

Who owns the resulting code and IP?

You do. All delivered code is assigned to you on final payment. An NDA can be signed before I review anything.

What if you find something nasty mid-migration?

The Phase 0 assessment exists to surface surprises before a price is committed. Anything genuinely outside the assessed scope is handled through a clear change-order process. No silent overruns.

Do you handle ASP.NET Web Forms?

Yes. I’ll be straight that there’s no like-for-like path: Web Forms has no .NET Core equivalent, so the UI tier (.aspx pages, code-behind, server controls) is rebuilt on Razor rather than transformed. The safeguard is the same as every other migration — characterization and Playwright tests pin each page’s current behaviour first, and the rewrite has to pass them. It’s more involved than a class library or an MVC app, so it’s scoped and priced for that, but it’s part of what I do, not a separate gamble.

Do you deploy it or manage our cloud?

No. Deployment, CI/CD, and cloud architecture stay with your team. I hand back a building, passing repository. Keeping that boundary clear is what makes the fixed price reliable.

What .NET version do you target?

.NET 10, the current Long-Term Support release. It’s the supported, hireable, future-proof target, not an interim version that ages out in months.

An unhandled error has occurred. Reload Dismiss

Rejoining the server...

Rejoin failed... trying again in seconds.

Failed to rejoin.
Please retry or reload the page.

The session has been paused by the server.

Failed to resume the session.
Please reload the page.