Last post Jul 03, 2020 12:12 PM by wavemaster
Jun 30, 2020 05:35 PM|bot123|LINK
Say I want to re-write a website that has different components in their own separate Blazor apps/projects (but it will flow like one application to the user). Which would be best to go with (WASM or server) for these different functionalities and why?
1. A candidate type website for students wishing to submit their resumes and communicate with the company (candidate.Samewebsite.com).
2. a recruiter site for employees in the field entering initial records about students (recruiter.Samewebsite.com).
3. a site that holds data for the CEO to be able to check-in real-time throughout the day (risk.sameWebsite.com)
An example of what I'm looking for is: says I had a part of the website where users who are using the product will be in rural areas with sketchy internet, I would think of going with WASM to reduce server dependency.
With this in mind, if I were to choose a path to go with, would it be very difficult to change my mind and make one of the other options? Or is it a complete re-write wit a lot of copying and pasting?
Jul 02, 2020 05:54 AM|Mikesdotnetting|LINK
WebAssembly is considered the proper implementation of Blazor. The Blazor Server approach was introduced as a stop gap until the WebAssembly version was ready. Now that it has been released, there's no real benefit to using the server option. Comparison
between the 2 approaches is detailed here: https://docs.microsoft.com/en-gb/aspnet/core/blazor/hosting-models?view=aspnetcore-3.1
It should be pretty straightforward to change from one hosted model to the next.
Jul 02, 2020 04:27 PM|wavemaster|LINK
I got the impression that if you use Identity functionality that it needs to live on the server.
Or am I mistaken?
Jul 03, 2020 06:06 AM|Mikesdotnetting|LINK
There is an implementation of Identity for Blazor WASM based on IdentityServer that uses JWT bearer tokens: https://docs.microsoft.com/en-us/aspnet/core/blazor/security/webassembly/hosted-with-identity-server?view=aspnetcore-3.1&tabs=visual-studio
It's designed primarily to protect API endpoints (i.e. the data access layer) which will be on a server along with the default identity database.
Jul 03, 2020 12:12 PM|wavemaster|LINK
Perfect base for someone to make a nice tutorial called "how to add IdentityServer to your existing WASM app"
Something like that will generate some traffic.