Blazor United -- I love it. Especially the auto mode for first-time vs cached. More often than not, projects evolve into something bigger than the original design. And when they do, starting from a project type such as this, affords the flexibility without having to completely change the architecture. For that reason alone, I think this adds tremendous value! Steve's new super mega thing
This is nuts. You've covered all of the disadvantages to Blazor WASM and made it all magic. And you can spin it all up without the heavy lifting of something like React. Also, the "server side" devs won't fear it.
You guys took it one step ahead, it's incredible! People were asking if it was possible to support Blazor Server and WebAssembly side-by-side in the same app. Now you made their choice for them!
This is it right here. The automatic switchover from Blazor Server to Blazor WASM once assemblies are downloaded is the killer feature that's going to make Blazor a viable option for A LOT more use cases.
Amazing!! Mind-blown emoji. We use pre-rendering right now to improve the load time of our Blazor wasm apps. Better user experience and critical for SEO, but there’s still the Blazor initialization delay. It’d be amazing to move this to the background. Any plans to take advantage of this new progressive/auto feature to benefit this scenario? I’d be amazing to render on the server for SEO and speed, but then transition to WASM in the background, avoiding the Blazor WASM initialization delay.
I love where this is headed. Using Blazor for public-facing websites came with trade-offs until now, but this makes it a no-brainer! Giving developers control over render modes is perfect, abstracting that away behind magic would be a regression imho. I do hope that the server-rendered bits do not suffer from the circuit-server pinning challenges that come with Blazor server. That's the biggest challenge with Blazor Server for us currently, as it makes load balancing and deploying updates very difficult.
It would be cool if you guys could add SSG (Static Site Generation), ISR (Incremental Static Regeneration), On Demand ISR. Really looking forward for this. Anyway, I feel like it's the time to invest time in Blazor. Great work.
This is what I've been waiting for. This component architecture we had a little bit with webform. Always wondered why it had to be different. Lovely, just lovely. How can we accelerate this. I hope we done have to wait for next dotnet release. Please please let this come very soon. I so cant wait.
Steve, you are a god! This was the missing link that would make Blazor truly the number 1 choice for frontend, with absolutely no disadvantages from my point of view!
More importantly, it is great to hear directly from Mr Steve Sanderson via this channel, the architect of Blazor and one of my favorite devs and a genius. Hope he presents more content here, it will be very helpful. Thanks Steve!
This is amazing. We use blazor server side for the reduced dev effort for POC but has the shortcoming of scaling up to users, you have now solved that with us being able to program hot pages as static content ♥️
This is really good stuff, Steve. Very relevant to what we're doing and would undoubtedly help us greatly if something like this makes it to production.
as usual another AMAZING Steve Demo ;) I like Blazor Wasm over Blazor Server BUT, now I can see how the Server rendered mode will show the usesr a FULLY interactive page wile the WASM bits are being cached :)) thats the killer feature for Blazor Wasm that I am excited about. Another BIG use case is making certain few components/pages of the App that have high intellectual Property value as Server Rendered so their DLLs are not exposed in the browser's cache while keeping all other components Auto or Client rendered. ANOTHER Huge win for Blazor United
No one can beat Blazor now. This is the best thing happening right now. I need something this for one of the project I am working on. I am using Blazor server but I do not want ws. And now you are working on it, So Thank You for this great addition to the Blazor. Waiting this to be released
This is really great idea! And I think you can also add some attributes like AtClient AtServer where Blazor components preferably be rendered. So, you can render whole pages and "big" things at server and use wasm to interact with controls and JavaScript at client side. Sometimes you expect region of the page to behave like SPA, but the application overall use server-side rendering. This way you can open several tabs on your browser and be in the same context, but not necessarily synchronize some wasm stuff, which mostly designed to interface interactions.
I've been developing in Blazor WASM for several months and what you've presented here is fantastic! I am using several third party Blazor components now, however, so I hope this will work seamlessly with those.
This is something I've wanted for a long time. Thank you for taking the obvious next step to making "real" server-side blazor work. I love the freedom of choice too, there are definitely scenarios where having these types of choices makes a ton of sense.
I lead my company’s innovation developer group and focus on extreme agile developed prototypes. We are highly focused on delivering as fast as possible and this sort of framework is perfect for what we do. Very excited for preview releases!
Brilliant work! I have been experimenting with combining Razor components for the login process of my Blazor apps so the WebAssembly can only be downloaded by authenticated users but your work with Blazor United looks much more practical and extensible. So excited to keep it all in the Blazor pages/components.
Steve please make this channel live and running, we love and miss your voice, style, and simplicity. please please, we need to listen to you regularly.
Oh I want this. It would sure be a lot easier than the huge amount of js/ajax we have to write to mimic an SPA and still keep our SEO for our public pages. Great stuff.
I just wonder how authentication and authorization would work in this scenario, as Razor Pages, Blazor Server and Blazor Webassembly have all different implementations that define if a user is authenticated or not and how to handle authentication state.
This is and excellent point. As part of your sample code, it would be great to have aunthetcation/authorization demo code in there as well. The opensource OpenIddict library would be a good library to use for this.
I think that is the point, in blazor server the connection is directly, so, if you want to use Blazor United, you need to decouple the front and the backend (Similar of how Next.js works)
With Cookies, I believe. Just like static pages in Razor Pages does today. Works for Server-side rendering already. It would most likely work the same way for components of mixed Rendering Modes as well. It all depends on your set-up.
@@marna_li there should be support for token-based authentication, it is used most of the time with SPAs. but I don't know how tokens can work with server -side rendering.
Does the mixing of SSR, streamed SSR, blazor wasm and blazor server create any complications for authorisation? Especially when you're going as far down as per component choices. Either way Blazor rocks, I really love working with it
Loved it. Especially the Auto mode. But I'm a little curious about Authentication and Authorization handling if there are no API services to validate the authenticity of the request.
Definitely need that last bit. My latest project is actually two builds, blazon server side and wasm. For most landing or first visits, I use server side. For users for paid or specific application within my web app, i route them to the wasm.
Love it. Thank you Steve and to your team! Amazing things from Blazor team. This clearly shows the power and flexibility of Blazor and .NET technologies!!!
I'm eagerly anticipating the upcoming releases, as the evolving landscape of WebAssembly, Blazor, and related technologies often leaves me indecisive about the best choice. One of my core requirements is robust support for MySQL and MariaDB databases, as I have several Windows Forms projects that I'm keen to transition to web-oriented platforms. However, these projects currently utilize MySQL and setting up a web user authentication system with this databases has proven to be a significant challenge for me.
It would be amazing if we could use WebAssembly mode only when an internet connection isn’t available (to enable offline mode/PWA), but use Server mode otherwise-this way we could get all the benefits of Server when online (like directly access DB, without need for an API) but still get offline capability. I hope if “United” makes it to production, this use case will be supported.
Well, this is actually awesome. I was doing some Blazor webassembly work but this will be great to not to think much on server/client app. Just use it as per the need to the level of a particular component or automatically for a page. Just waiting for something similar for desktop development, like select the project type to something specific and it will work as native desktop app in Win / Mac / Linux. No need to do any extra / third party / special stuff... Something similar to Win Form but will work as OS agnostic way. Having said that, this is just brilliant.
Love to see blazor challenging the JS supremacy and bringing new stuff to the table! Been working with blazor for a year now and I don't want to work with anything else, it's an awesome tech.
This is the best thing I've ever seen! I've been using razor pages + blazor server embeds which works, but feels a bit of a hack. Please do this. All of it.
this is awesome.. I think alot of performance scenarios especially downloading megabytes of webassembly libraries can be solved with blazor-united! this is truely a game changer to the blazor world... makes me want to use Blazor againfor future projects... can't wait to try it out.. i am hopeful that i gets GA release!
This is AWESOME, i would also love to see the entire "Document" methods on Blazor, killing the JsRuntime and encapsulating it just to the browser methods inside a set of methods. WOULD BE INCREDIBLE.
Excellent! As many others have put we need authentication to be seamless with it. I would also love to see wasm be able to call server API methods as easily (or nearly) as you can in blazor server. Along the lines of putting an attribute on your API methods that allows them to be called like any other method. The framework handles the http communication. Similar to grpc I guess.
This is a game changer. Wasm takes too long to download for public websites. On the server-side circuit reconnections feel like you are streaming. This will be helpful in both scenarios.
Brilliant - PLEASE include the ability to start with server and move to WASM on the next refresh, after everything is downloaded!! The startup time can be a real killer in WASM, this looks perfect!!!
