A sample application demonstrating migration from ASP.NET Web Forms to Blazor for .NET 8.
eShopOnBlazor is a sample application that demonstrates how to migrate a traditional ASP.NET Web Forms application to Blazor, Microsoft's modern web framework. It serves as a practical reference for developers transitioning from Web Forms to Blazor, showcasing architectural patterns and migration strategies.
ASP.NET Web Forms developers looking to transition their applications to Blazor, and developers seeking real-world examples of migration strategies from legacy web frameworks to modern component-based architectures.
Developers choose this project because it provides a concrete, educational example of migrating a full e-commerce application, illustrating equivalent Blazor components for Web Forms controls and following Microsoft's recommended practices for incremental adoption.
Migration of a traditional ASP.NET Web Forms app to Blazor
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Updated for the latest .NET 8 framework, ensuring the sample remains relevant for current development environments, as stated in the README.
Provides a concrete, full e-commerce application migration from Web Forms to Blazor, illustrating real-world patterns and component comparisons, as highlighted in the project description.
Linked directly to Microsoft's free eBook 'Blazor for ASP.NET Web Forms Developers,' offering comprehensive, official guidance alongside the code sample, per the README links.
Showcases Microsoft's recommended practices for gradually migrating legacy applications, emphasizing component-based design to minimize disruption, as noted in the philosophy.
Active development has moved to a new repository (https://github.com/dotnet/eShop), so this repo may not receive future updates, bug fixes, or support, as admitted in the README.
Primarily focuses on migration from Web Forms, so it lacks coverage of advanced Blazor features, modern UI frameworks, or best practices for greenfield development.
As a demonstration, it omits critical production-ready features like comprehensive security, error handling, and scalability, making it unsuitable for direct deployment.