0:00 / 0:00
The Future of Blazor on the Client
Microsoft Visual Studio
345K subscribers • 8 videos on Hallway
- Recommended by 1 person: 1 in engineering communities.
- Made by the vendor. The company whose product it covers made or sponsored it.
- May be out of date. The tools, versions or practices it shows have likely moved on.
Beginner. No background in the topic needed.
31K views7 years ago1 recommendation
Web developmentProgramming languagesC# and .NETVue, Svelte, Angular and othersWebAssembly
The future of running Blazor client-side in the browser via WebAssembly is discussed alongside desktop and mobile support.
Announcing .NET Core 3.0: aka.ms/dotnetcore3 #dotNETConf In this session we'll look at how Blazor in .NET Core 3.0 is a flexible and productive client UI framework for the web and beyond. We'll look at the future of running Blazor apps client-side in the browser via WebAssembly. We'll discuss the benefits of hosting Blazor WebAssembly apps with .NET Core to enable full-stack web development with .NET and C#. We'll also look at taking Blazor beyond the web to support desktop and mobile app development.Why it's here
1 person recommends thisMoments people linked to
u/losmackoin r/dotnet • Mentions
On “Linux/Mac Desktop app .net core”
By Dan Roth
[video
u/RirinDesuyoin r/dotnet • Mentions
On “Building Full-stack C# Web Apps with Blazor in .NET Core 3.0”
The easiest sample to use is the Asp Labs one. Here's the experimental repo. Caveat, it isn't something labeled as supported by MS yet and the blazor version isn't up to date if I recall. To be able to use the GA version, it'll be abit involved on the setup part. On a freshly created Blazor (server side) template, you'll need to use `ElectronNET.API` from nuget and install their dotnet tool called `ElectronNET.CLI`. You generally just follow their startup guide on their repo and you should have your new blazor template running on Electron via `electronize start` command. The difference between the AspLabs and the handrolled `Electron.Net` is that the AspLabs aims to make it a bit more idioma…
u/gavilanch2in r/dotnet • Mentions
On “What problem(s) does Blazor solve?”
For sensitive stuff you can go down the ASP.NET Core route. If you have your Blazor WASM with payment logic, you may put the payment form in the front-end, but use an endpoint of your ASP.NET Core App to process the payment. That way, everything is secured.
I'm not aware if you can combine WASM and Server-Side on the same project. Daniel Roth mentioned it in the latest .NET Conf, but he has not tested it by himself: [video