blazor server might get dropped?

Question

User2110873642 posted

i heard speculation that blazor server might be dropped when blazor WASM gets better.

there are a few things that i dont get.

comming from webforms, it was logical to pick a server side version of blazor, without even really thinking about it. also, for my web project, telemetry measurement is pretty important to my customers. it has to work as close as possible to native websites, and count page visits.

i heard other people say that blazor is here to stay. they werent talking about the server version werent they?

i cant imagine my website possible without a server or at least a server side api.  isnt it rediculous that blazor server is gonna be dropped? because the server side version seems less troublesome to me, than using some web api.

do i have to be concerned about blazor server dropping? i am just about to convert all my projects.

Answer 1

User-821857111 posted

The "proper" version of Blazor is the WASM version. The server version was released to give the masses something while they sort out various technical issues with developing against Web Assembly. This was pointed out to you about 3 weeks ago: https://forums.asp.net/t/2169153.aspx

Your application is largely CRUD, I believe, and you don't want to make it a Single Page Application. You don't want A PWA either.  If that is correct, you should be using Razor Pages. 

https://www.telerik.com/blogs/razor-pages-the-natural-successor-to-web-forms

https://www.learnrazorpages.com/

i cant imagine my website possible without a server or at least a server side api.

Web API is always hosted on a server. It's got nothing to do with Blazor. The Blazor part of the application can be executed on the client or the server.  There seems to be a fundamental misunderstanding on your part about what Blazor actually is.

Answer 2

User2110873642 posted

If that is correct, you should be using Razor Pages. 

the problem with razor pages is that there is no connection with the clientpage. i can not update the page when i want to. and i do not want to use javascript or ajax either. if this is the case, even webforms is more efficient for me.

i like blazor server, i just hate that it tries to be a single page app.

The server version was released to give the masses something while they sort out various technical issues with developing against Web Assembly

is this speculation or is there an official msft post about this? i certainly dont want it to be true. after all, i think that most people who adopt blazor ARE comming from a webforms background. and are adopting it for rich ui, and they would probably all dislike that it tries to be a SPA or PWA.

This was pointed out to you about 3 weeks

i didnt believe him. but now im starting to, and im not liking it..

Answer 3

User-821857111 posted

i like blazor server, i just hate that it tries to be a single page app.

Blazor is and always has been an SPA framework. Whether the application logic takes place on the client (WebAssembly version) or the server (via a SignalR roundtrip), it is still an SPA. You are fighting against the very nature of the framework. 

i didnt believe him.

If you refuse to believe what people here tell you, why bother asking questions in the first place?

is this speculation or is there an official msft post about this?

No it's not speculation. It's knowledge gained from following the project from its beginning. But, hey - if you don't like that, you can choose not to believe it.

Answer 4

User2041008840 posted

I am totally agree with you mike. The Blazor WASM is the future. 
I already moving my all software to blazor wasm its actually give best performance that spa razor pages, asp.net classic and asp.net mvc/core mvc. 

The blazor is the future, invest soon as possible in blazor. for the larger data and large crud, I will go to azure cloud and my front will be blazor wasm. 

on some point i dont use wasm and also spa with Ecommerce website or any website because for SEO does not work properly with spa.

Answer 5

User2110873642 posted

SEO does not work properly with spa.

that ain't true. google announced 4 years ago that it was ready for SPA and PWA apps. they said they were able to crawl javascript, and they would wait 30 seconds for afterrenders to load.

on the side of this, you can easely create a sitemap and link it to google. you can automatically generate a sitemap file at startup to your wwwroot. this is the better way anyway, and you should be doing it on other project types too.

Answer 6

User2110873642 posted

how do you safely create a remote CRUD, when all WASM code can be decompiled in the browser?

Answer 7

User-474980206 posted

the same way you would with webforms, never blindly trust posted data, always verify.

the server crud api should authenticate and validate its parameters, and only allow the users to CRUD what they are allowed to CRUD. This is just api design 101.

Answer 8

User2110873642 posted

but with blazor serverside, you can validate the UI the user has gone trough. such as captcha

Answer 9

User-474980206 posted

as captcha is just a javascript library that runs in the browser, and support SPA's you can do it with blazor WASM.  see

  https://developers.google.com/recaptcha/docs/v3

your verify api should return a token you include on api requests.  if its an anonymous site, otherwise why captcha, just have the verify return a bearer token you use on api calls. if its not anonymous(?) just add to the login process.

 

Answer 10

User2110873642 posted

as captcha is just a javascript library that runs in the browser,

i hope you are joking. if the validation isnt on your server end, it wont help.

https://developers.google.com/recaptcha/docs/v3

when talking about captcha you cant just assume were talking ReCaptcha.

Answer 11

User-821857111 posted

but with blazor serverside, you can validate the UI the user has gone trough. such as captcha

You should validate on the server when accepting data in a Web Assembly app too. Same as any other SPA.

how do you safely create a remote CRUD, when all WASM code can be decompiled in the browser?

Again, same as any SPA. Don't put critical business logic in the client application. Any processing that involves proprietary algorithms should take place on the server.