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 few weeks ago, I was on a live call with a group of .NET developers. No agenda. No slides. Just real developers talking honestly about what is actually working with AI tools right now - and what is not. One of the first things Paul said set the tone for the whole session: "In the hands of an experienced developer, any AI tool is an accelerator. In the hands of a rookie, it's just dangerous." I keep thinking about that line. Because I think it is exactly right - but it also misses...
Hey friend, This week, I built a working Blazor app from scratch in about 30 minutes. But that's not really the point. The point is how. Not by throwing a prompt at Claude and hoping for the best. But by thinking about architecture first, defining instructions and skills for the AI upfront, and then letting it implement while you stay in control and review the output. That's the difference between AI doing your job and AI doing the boring parts of your job. The video walks through exactly...
Hey friend, A year ago, I said AI coding tools weren't the future. I want to correct that. The distinction I missed: there's a real difference between vibe coding (copy-paste until it compiles, no understanding required) and skilled AI-assisted development (you own the architecture, AI implements it, you review the output). I was criticizing the first and accidentally dismissing the second. In 2026, skilled AI-assisted development is the professional standard. Not using these tools is now a...