Become a .NET & Blazor expert with weekly tutorials featuring best practices and the latest improvements, right in your inbox.
From localhost to live URL in one video
|
Hey friend, Building a Blazor app is the easy part. Getting it deployed so other people can actually use it is where most developers get stuck. It is also one of the biggest reasons developers joined the Blazor AI Workshop last week. The "I can build it, but I cannot ship it" gap is real. So I made a focused YouTube video showing the simplest way to deploy a Blazor app to Azure. A tic-tac-toe game with SignalR, real-time updates, a history feature with SQL Server. Deployed to Azure with continuous deployment from GitHub. Including the idempotent migration trick so your database setup actually works in production. If deployment has been the part holding you back, this video is the unblocker. Take care, Patrick P.S. The full 3-hour Blazor AI Workshop recording goes much deeper. Empty folder to deployed app with AI as the coding partner the whole way through. AGENTS.md, vertical slice architecture, multi-user sharing, OpenAI integration. Available here. |
.NET Web Academy
Become a .NET & Blazor expert with weekly tutorials featuring best practices and the latest improvements, right in your inbox.
Hey friend, A developer I know built his whole career on one bet: that young developers would never want to touch old code. So the legacy systems quietly running real companies would always need someone, and he would be that someone. For twenty years it paid. Then AI arrived and went straight for the part he thought was safe. Because the hardest part of modernizing an old system was never the typing. It was the understanding. Reconstructing thirty projects and three contractors' worth of...
Hey friend, The other day I found a bug in StackBuddy, an app I built. Normally I'd open it, file a ticket for myself, and move on. Instead I turned to my AI and just said, "log a dev ticket for that." And it did. A real ticket in my own bug tracker. Title, description, priority, the whole thing. I never opened the actual app. The thing that makes that possible is called MCP, Model Context Protocol. Ignore the name for a second. Out of the box, an AI can only talk. It writes and explains, but...
Hey friend, I don't really write code by hand anymore. I describe what I want, and the AI builds it. For a while, that scared me. If I am not writing the code, does everything I spent years learning still matter? Does my stack matter at all? If you are a developer right now, I would bet you have felt some version of that too. Here is where I landed. It flipped the whole thing for me. The other day I was debugging a slow app, talking it through with the AI. Would WebAssembly help here? Is it...