Since 2019, our team has been using Blazor in production. We’re all C# developers, so picking Blazor for our newest project made sense, even though it was only a week old! Seeing the experiences of other teams, I believe that switching to Blazor really saved our project.
Our experience has been pretty smooth, but we’ve learned a bunch along the way. In this session, I’ll share some practical tips and learnings we’ve picked up about when to use what and how to avoid problems when switching your project to Blazor.
Jimmy Engström has been developing ever since he was 7 years old and got his first computer. He loves to be on the cutting edge of technology, trying new things. When he got wind of Blazor, he immediately realized the potential and adopted it when it was in beta. He has been running Blazor in production since it was launched by Microsoft. He is the author of "Web Development with Blazor" and the co-host of Coding After Work (podcast and stream). His passion for the .NET industry and community has taken him around the world, speaking about development. Microsoft has recognized this passion by awarding him the Microsoft Most Valuable Professional award 10 years in a row. He occasionally blogs at www.engstromjimmy.com.
