Tales from the .NET 8 Migration Trenches -

Migrate to .NET 8 with confidence by learning from experts on the challenges and opportunities of upgrading from .NET 4.x, including handling changes in configuration options, business logic, and more.

Key takeaways
  • Migrating from .NET 4.x to .NET 8 requires significant changes and planning.
  • Upgrade project to a newer .NET version or create a new .NET 8 project.
  • ASP.NET Core and ASP.NET MVC 5 have different configuration options.
  • Migrate controller actions and sessions to ASP.NET Core.
  • Business logic and dependency injection need to be reviewed and updated.
  • Handle changes in data protection certificates and session state.
  • Reverse proxy can be used to forward requests from ASP.NET 5 to ASP.NET Core.
  • ASP.NET Core’s routing system is different from ASP.NET MVC’s.
  • Bundle and minification methods need to be updated.
  • Use ASP.NET Core’s built-in features, such as caching and session management.
  • Handle differences in middleware and middleware ordering.
  • Consider using ASP.NET Core APIs to handle requests from ASP.NET 5.
  • Review and update application configurations, such as authentication and authorization.
  • Monitor and test the application after migration.
  • Consider using a shared library for common code between ASP.NET 5 and ASP.NET Core.
  • ASP.NET Core 8 has improved performance and scalability.
  • Migrating to ASP.NET Core 8 can improve application security and reliability.