Do you have a .NET Framework project out there that’s really looking to be updated to dotnet? Have a look at the path we chose when upgrading a production webshop running on WebForms with every imaginable anti pattern, into a modern framework with a MVC public site and a Blazor administration interface. On this trip we will go through subjects like analysis, planning, architecture, some best practices and what will you need to do to move it from on premise or Infrastructure As A Service to a fully managed Platform hosted solution.
Back in 2003, I discovered .NET. Coming from a background of mostly using C++ for client- and PERL/ASP Classic for web-development, discovering and developing with .NET was like the clouds opening up and a ray of sunshine washing over me. Since then, I've been working with .NET in various forms, from ASP.NET WebForms to ASP.NET MVC to ASP.NET 5+, from Windows Forms to WPF to UWP, from WCF to WebAPI to gRPC, from SQL Server to MongoDB to CosmosDB. While I've dabbled with other languages and platforms since, .NET has been my home, and pulling me back in as my platform of choice. Today, my day job is running a consulting firm specializing in .NET development and Azure architecture. At other times, I run an open, inclusive and educational twitch stream helping people experience and learn .NET.
