BUG UPDATE shown in the video: This isn't actually isn't a bug, but I didn't realize additional code was required to make this work. You have to set a [CascadingParameter] HTTP Context property - you can see the code example here: learn.microsoft.com/en-us/aspnet/core/release-notes/aspnetcore-9.0?view=aspnetcore-8.0#add-static-server-side-rendering-ssr-pages-to-a-globally-interactive-blazor-web-app
I believe the bug you mentioned may be somehow related that you only have one project set up and configured to support server side rendering alone. When you have different interaction modes, .net configures two projects by default. You may want to try the same with default setup for interactive rendering.
Hey thanks for watching. You should only need two separate projects if one of the render modes is webassembly because that complies a separate dll that gets sent to the browser. Both server side rendering modes should be able to be used interchangeably in the same project. The reverse of this scenario does work, where server static is the default but you enable interactive on a single component for example, assuming you configure interactive server in your program.cs
Yes, you can add classes to the main grid component that are rendered in the final table output, and columns and rows can be styled as well. It'll just take some manual class assignments to the components and tinkering
Please help me : This browser does not support WebAssembly. This problem has occurred in some clients with Windows 11 and google chrome, whose browser is updated.
BUG UPDATE shown in the video: This isn't actually isn't a bug, but I didn't realize additional code was required to make this work. You have to set a [CascadingParameter] HTTP Context property - you can see the code example here: learn.microsoft.com/en-us/aspnet/core/release-notes/aspnetcore-9.0?view=aspnetcore-8.0#add-static-server-side-rendering-ssr-pages-to-a-globally-interactive-blazor-web-app
nice demo of the server reconnect experience
Nice introduction to .NET9
Thank you!
I believe the bug you mentioned may be somehow related that you only have one project set up and configured to support server side rendering alone. When you have different interaction modes, .net configures two projects by default. You may want to try the same with default setup for interactive rendering.
Hey thanks for watching. You should only need two separate projects if one of the render modes is webassembly because that complies a separate dll that gets sent to the browser. Both server side rendering modes should be able to be used interchangeably in the same project. The reverse of this scenario does work, where server static is the default but you enable interactive on a single component for example, assuming you configure interactive server in your program.cs
Thank for this usefull presentation.
The only problem with Virtualize is that it doesn't support components.
is it possible to show quickgrid as bootstrap?
Yes, you can add classes to the main grid component that are rendered in the final table output, and columns and rows can be styled as well. It'll just take some manual class assignments to the components and tinkering
Please help me : This browser does not support WebAssembly.
This problem has occurred in some clients with Windows 11 and google chrome, whose browser is updated.
Hi, do you have a complete latest blazor course from scratch on your channel?
I don't, but I've been thinking of making one
@@alexthecodewolf Thanks, would be waiting for it.
With a primary constructor, this could be even simpler
True!
Does it retain state after reconnection?
Not in my testing unfortunately