How to use Codex to migrate WebForms to Blazor
A developer reported migrating WebForms to Blazor with Codex in roughly 48 hours, followed by extensive testing and QA fixes. The team then changed authentication and deployed the application to OpenShift.
news.ycombinator.com
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Migrate [legacy WebForms application] to Blazor while preserving [required behaviors]. Use [existing end-to-end test suite] to verify the replacement. Work through [QA findings], then plan [authentication migration] and deployment to [target infrastructure] for review.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source poster / publisher
- nharziro
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- The author reported a launched Blazor replacement, OpenShift deployment, and improved stability, speed, and functionality after testing and fixing around 20 QA findings.
- Human involvement
- The original developer guided the work, existing end-to-end tests checked functionality, and QA found bugs that were fixed before launch.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- Use Codex to port the legacy WebForms application to Blazor.
- Run the replacement against the existing Python end-to-end tests.
- Fix the bugs QA found before launching.
The author migrated a legacy .NET WebForms application to Blazor, reporting that the code migration took roughly 48 hours. They believed they used GPT-5.2 through Codex. The application already had a strong Python end-to-end test suite, which the team ran against the replacement to verify that existing functionality was preserved.
Testing continued after the migration. QA found around 20 bugs, which the team fixed before launching. The team then moved authentication from Shibboleth to Entra OAuth and deployed the application to OpenShift. The old WebForms application had been confined to virtual machines because the cluster lacked Windows worker nodes.
The author reported that the modernized application was more stable, faster, and more functional. They attributed success to their own deep knowledge as the original developer and to the comprehensive QA suite. They estimated the Codex work cost about $150 at January token prices. Who it's for: Teams considering a framework migration where application expertise and an existing behavioral test suite can support verification.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: Hacker News · nharziro
Frequently asked questions
How did the team verify that functionality survived?
They ran the new application against the existing Python end-to-end test suite, then fixed around 20 bugs found by QA before launching.
Why did the migration enable deployment to OpenShift?
The author said the old WebForms application could not run on their OpenShift cluster because it had no Windows worker nodes.
More details
Remaining steps
- Move authentication from Shibboleth to Entra OAuth.
- Deploy the modernized application to OpenShift.
About this account
Codex accelerated the code migration, while the original developer supplied application knowledge and the team verified behavior before launch.
Platform: Hacker News. Attribution: https://news.ycombinator.com/item?id=49796026. Prompt: Suggested (written by Agents In Use, not the author's). Sourced by the Agents In Use pipeline.
Credit: nharziro on Hacker News
Source published
Added to Agents In Use
Source checked
Tools and topics
Codex · .NET · Blazor · Python · Entra OAuth · OpenShift
.NET · Blazor · Migration · End-to-end testing
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.