Github Copilot Fails Web Forms to Blazor #githubcopilot

In this video, I explore what it’s really like to use GitHub Copilot to convert an old ASP.NET Web Forms application into a modern Blazor WebAssembly app. The original project is very simple — just a single page that creates a product and stores it in a database — but it’s a realistic example of the type of legacy system many developers still need to maintain or upgrade today.

My goal was to see how far AI can assist with a Web Forms → Blazor migration. When the experiment begins, there is no Blazor code at all. Even after several hours, Copilot struggles to automatically produce a working Blazor app. At the four-hour mark, the solution technically compiles, but the Web Forms project is still far from fully migrated and the Blazor portion is nearly empty.

This video walks through the entire process, showing the limitations, challenges, and opportunities when relying on AI tools for application modernization. If you're considering moving from .NET Framework Web Forms to the latest .NET Blazor stack, this experiment will give you a clear, realistic expectation of what AI can and cannot do today.

What this video covers:

Converting legacy ASP.NET Web Forms to Blazor using GitHub Copilot

How AI handles older codebases and outdated UI frameworks

Challenges when migrating server-side event-driven Web Forms logic

Observations after 3–4 hours of automated migration attempts

What developers should prepare for when modernizing legacy .NET applications

Why fully automated Web Forms → Blazor migration is still not straightforward

Видео Github Copilot Fails Web Forms to Blazor #githubcopilot канала Codeless Developer