Azure EntraId on-premis also works basically the same way? Great video thank yoU!

I am using VueJS and REST-API and all running in a Golang Project. I completely moved everything from C# to Golang.

Thank you Shawn! For many years you have been on my radar as v. informative and v. interesting... love fact you seem to be fan of Vue + Tailwind - you clearly actually DO substantial real-world dev. (so much trash published by people who seemingly just think about real world dev, but rarely if ever actually do it). haha. Don't get me started on some of the MS Patterns and Practices stuff (I mean wow!). 100% agree (with my admittedly v. limited experience with Blazor) that you are correct with the summary (if I got it right?) i.e. " Is it worth it? Probably not (assuming you are comfy with js/ts and e.g. Vue). Unless you have some v. specific requirements that make WASM a real contender for the functionality you need. " Pls do shout if that is NOT a good paraphrasing of your topline? Also totally hear you with the clunky tooling e.g. need to restart the app (vs what we now come to expect i.e. ~immediate ~perfect hot reloading dev experience for frontend). I do wonder 1. if you were a fan of Knockout before Vue (do I remember some old blog posts about KO)? 2. if you prefer Vue (3) Composition API (over Options) 3. if you tend to use Pinia or similar in Vue3? FYI I'm pretty firmly 1 = Yes, 2 = Yes 3 = No Apologies if you've totally covered all of that on a blog/other vids (don't have much time to research/hone these days). ;( Much appreciated!

This is the exact video I was looking for to get my new project off the ground. Some of the different options and configurations aren't easily discoverable sometimes especially with something completely new like Aspire so this was great to see. Thanks!

I’m picking up web dev after about 15 years of not coding. Blazor is what I’ve been learning and it’s awesome. I’m avoiding JavaScript for time being as I have stuff I need to get done.

Very good. But for the front end, how about Blazor wasm? Can you give me where i can get the information?

This is a great video

For developers that don't know / don't want learn frontend (html / css etc) then Avalonia UI is a better tech stack. With design preview integration to VS and Rider it becomes a much better developer experience without having the need to stop / start the app for each xaml change.

I am learning something about Bootstrap today. Thank you Shawn.

I think you're wrong for most cases.. I find Blazor way more productive than the mess of JavaScript tooling etc. I use it exclusively now and it's only getting better. Sure hot reload can be hit and miss sometimes. There is components.. and I've even done a project with web, Windows and Android (with Maui Blazor) with common C# components across it all. I haven't hit a use case yet where it's really stopped me.. there's been a few JS interops with minimal JS in that case. I think if you're starting a new data display/crud project, it's a no brainer. And another key factor is it's inherently more secure because you're not exposing your source code (and possibly APIs etc) in raw JavaScript (even more so if it's just server side rendered - and you can mix that now per component).. C# and LINQ in the browser is just wonderful and all that Nuget goodness and updates are usually easy. dot NET 9 also addresses some of the early complaints about Blazor. Maybe it's not up to doing any heavy canvas or gaming app yet but I haven't tried. Team up Blazor with ActualLab Fusion for real-time data and you can do some killer stuff...

"I've been in the software engineering field since 1985...." I still have a long way to go. Thank you.

I have need for a collection of records (immutable) to do some quick lookups of various properties (no changes). Which might be a faster collection to use, and do collections affect the records they hold?

I use Blazor Server for our in-house web apps and I love it! C# makes it much easier and I can write an app more quickly. Also, JetBrains Rider makes c# dev a much better experience than Visual Studio.

Use Blazor with MudBlazor, Bolero and use the Elm(ish) pattern. Once you have understood the functional approach, you get results quickly. I made an in-house web app running with Blazor Server (WASM is out of question, our company PCs all run Sophos which analyses all binaries once they come in which slows the application to a crawl) and the customer wanted one component of that application as a client-side app, exchanging the server-based functions with some simple file I/O. I managed to slap that component into a separate Blazor WASM application and use Electron to make the local application for the customer.

When I restart app, all data in db lost. How can I fix this?

I wish I’d discovered Blazor earlier! Moving from JavaScript through Node, Express, TypeScript, React, and React SSR felt like a constant juggle of libraries, packages, and compatibility issues. Each JS project needed a mountain of dependencies, which we could only hope would work well together across versions. And then there’s always that one person at work pushing to experiment with Bun, adding to the chaos. Remember when we used to think of React as a slow and clunky choice? Now, it’s evolved massively, much like Blazor.

The main thing I get from this video is that front-end web developers and back-end web developers are flexing two very different skill sets and expecting one developer to have true mastery on both sides might not be realistic.

Thank you!

When it comes to front end nothing beats JavaScript

Can this solution be used for small to medium sized apps in prod?

Good video Shawn, helps, great seeing you!

I still think blazor sucks but hey that's me I'll be JAMSTACK for a long time now even though I migrated from .NET. I love C# but I hate ASP. BTW Shawn's courses are always good and filled with great info. Keep it up shawn!

Blazor rocks - so much less work than angular

Thank You! Hope in v4 will be "partials" functionality by default without any additional tools. For example partials head, nav, footer and including them the most simple way into the HTML-pages.

Solid material. When you go over reference types nullability with such ease, you know straight away that you are listening to a an expert. Thanks.

I think Blazor is the way to go for all. The question remains is which to use, SSR or CSR or Auto, this what will differ from project to another. I think as well there is no problem at all with bridging between JavaScript and the assembly code. It cannot be easier. I used it heavily in both Interactive Server Mode and WASM. I also got a quite enough experience with Angular and React. I can confidently say that everyone should consider Blazor, even those who are living in JavaScript/TypeScript world.

Without knowing scope of your upcoming video, here's my thoughts. Love VS/Rider for their intellisense over VSC, in turn i dont like configuring VS/Rider like i do with VSC the default explorer view is preferred to me. It is also weird why Rider comes with plugins installed, they ought to defer that to their marketplace.

How do you get your npm scripts in the file browser?

In the past, I've considered Tailwind and similar style frameworks as obstructive CSS (a term I made up), much like how we view obstructive JavaScript. With the continuous evolution of CSS, we should keep questioning the relevance of Tailwind. Personally, I have never been a fan of how it clutters our HTML. However, you've shown how TW is trying to embrace and include the new CSS standards. I always worry if I am giving up the new capabilities/standards of the underlying CSS engine when committing to a style framework. Thank you, Shawn.

I love the @theme change using css properties. We ship our product to a partner channel, that in turn customizes it. Using a standard like this helps, they can just adjust the value of the property without touching our stuff!

The biggest lie about Blazor is people calling is a "JavaScript Killer". I wish we wouldn't do that. JS is a tool in our toolkit the same as any other tool. Use it where necessary, use it when you want, use it as you'd use any other tool. JSInterop is massively powerful, and even more powerful if your CSP isn't hyper-strict. You can inject tiny payloads of JS into any page that needs it, and clean up the DOM as components are disposed.

Love this video, thanks Shawn

Is it possible to make a .net core web application that use nuxt3 framework? and how could i make this project compatible with nuxt (building deployment etc). .net core with using modern ui development frameworks like vue nuxt react etc. it can be rough What is the correct way to make kind of this project? Backend and Frontend must be seperate or not? i cannot find any detailed documentation for this And thanks for the video

Oh heavens me ... this was a master-effing-piece. Thanks for the clarity it brought.

Please do a 10 thousand feet view of Blazor (both server and client side) -- just basic description of what the different parts are , how they come together, how they talk to each other --- with the simplest possible project that can demo it. How to think and reason about Blazor. Would be a great great illuminator. Blazor is too big and fuzzy --- and horribly confusing.

I've been using Blazor wasm for about 3.5 years now, and have been able to build some pretty interesting projects. I like it a lot, but am not quite a Blazor evangelist. The biggest problem by far is the tooling which is painful to deal with. Hot reload just doesn't work. So anytime you need to make even a minor change to the markup, you have to stop/restart, wait for the build to finish, the browser to launch, the debugger to attach, etc. It can be pretty tedious.

When I saw those glasses put on immediately subscribed. Great value content!

Thanks a ton, very clear very nice and i am thankful for the public repo!

great vid. You cleared up a lot of confusion I previously had!

I've been using Blazor recently, and honestly it's the only thing that's made web development enjoyable for me at last

I'm by no means a Blazor fanboy (I flip flop between Blazor and Svelte for my own projects) but re: 12:40 I'm interested to know why you consider learning Blazor to almost be lesser of a task/outcome compared to Javascript in the realm of web frontends? If Blazor is able to do everything you need, why is javascript even necessary? I've found recently that I'm not actually learning JS anymore, I'm learning React/Svelte/Angular and they just happen to use javascript. Ultimately the user doesn't care if the experience is good enough.

The development speed is high with Blazor, which is very important cost-wise. I experienced how slow the development process with React can be and the amount of garbage you need to write to satisfy the framework. However, AI assistant coding tools can change the narrative, and JavaScript wins because there are cheaper/younger developers in the market.

Wth... you just corrected a really confident yet wrong thought I had. instantly subscribing.

Is there a way to code-split it based on routes to make it lighter?

Visual Studio support is still not so great due to incomplete hot reload feature, but if you can digest few weak spots it can do nice job. It is perfect for building internal tools (thinking about enterprise companies) or smaller businesses. I've been into programming since late 90s and doing mostly system engineering, HATED doing any web coding. But with Blazor it's awesome. Coming from mostly low level C programming, I am one of those who believe web should fully embrace web assembly. This is why I see Blazor as a step in the right direction. It's far from perfect, but for simple and quick stuff it's good enough. And I underline this "good enough". I just hope MS keeps it alive longer than some previous frameworks :)

Totally Fully agree, have developed MFC, Win Forms, WPF and meanwhile Web only for decades and see Blazor in the niche you see it. Thx for digging deeper and verifying that.

Great content. I like it. Thanks!

Thanks Master Shawn, where can get the free SQL database hosting?

I agree 100% with you. And when you repeatedly hear: "it's good for internal organization apps"...means that's a mess!

Surprised to see quite a few folks having issues with Hot Reload. It seems always work for me. I'm doing Blazor WebAssembly with .Net 8.