Thanks for the greate tutorial. Its exatly what I am currently working with. Cant wait for the next part Hope you also include that the users login are saved in the database for a real world example.
your videos are great & self explained. it would be highly appreciated if you please give next video on refresh token & cascading master tables & pdf excel export on that same project
Hello, I would like to add a token in a DelegatingHandler for an HTTP client, but I am encountering a "JavaScript interop calls" error. What solution would you suggest?
Hi @whisperman4902 ,@fabriziofs Maybe you are encountering a 'JavaScript interop calls' error when the UI loads for the first time in server-side mode with the default setting of prerendering on the server. You can disable server prerendering by updating the App.razor file like this:
Very good course. The layers make sense. The code is clean. Some tables like user and claims are missing, don't you think? I just don't understand why not use Identity? Even if it was just to create the tables... But anyway, your content is very good and well explained, thank you.🕶😀 Continue this series👍
@@luizfredericojr Thanks for your kind words. Good question! For simplicity, I'm not implementing user verification in this video. I plan to implement user verification using Identity and add refresh tokens in the next video 😊😊
This doesn't take the Blazor prerendering model into account. The one where Blazor wasm is split between a server and client app. It's a shame. Microsoft shafted us with this model just to load the wasm slightly faster. All configurations are out the window having to do the same for both domains of the app.
Thanks for your feedback! You’re right-Blazor’s prerendering model adds complexity, especially with managing configurations across server and client. While it improves load times and SEO, the trade-offs can be frustrating. For simpler apps, skipping prerendering might save effort.
Good explanation.Continue this series❤
Thank you! I will do😊😊
Wow muchisimas gracias, explicas super bien, gracias gracias gracias.
Thank you very much🥰🥰
This is precisely what I have been looking for. Excellent job! I subscribed.
Thank you 🥰🥰
Thanks for the greate tutorial. Its exatly what I am currently working with. Cant wait for the next part Hope you also include that the users login are saved in the database for a real world example.
@@CentauriDK Thanks for your support. I will publish more about this very soon. 😍😍
your videos are great & self explained. it would be highly appreciated if you please give next video on refresh token & cascading master tables & pdf excel export on that same project
Thank you. I will publish it soon 😊😊
Gracias, saludos desde Chile
Welcome, Chile is nice country🥰🥰
Great video, So usefull. Thanks
Thanks for your support 🥰🥰
Hello, I would like to add a token in a DelegatingHandler for an HTTP client, but I am encountering a "JavaScript interop calls" error. What solution would you suggest?
I had the same issue and any of the solutions out there works for me :(, if you find a solution please share it with us :)
Hi @whisperman4902 ,@fabriziofs Maybe you are encountering a 'JavaScript interop calls' error when the UI loads for the first time in server-side mode with the default setting of prerendering on the server. You can disable server prerendering by updating the App.razor file like this:
Very good course.
The layers make sense.
The code is clean.
Some tables like user and claims are missing, don't you think?
I just don't understand why not use Identity?
Even if it was just to create the tables...
But anyway, your content is very good and well explained, thank you.🕶😀
Continue this series👍
@@luizfredericojr
Thanks for your kind words.
Good question! For simplicity, I'm not implementing user verification in this video. I plan to implement user verification using Identity and add refresh tokens in the next video 😊😊
This was really good ❤
Can you make a video on how to do this with Azure AD on both web api and Blazor project
Thank you. I will make an video about this soon 🥰🥰
@@dosehieu appreciated …the lack of clear documentation on Microsoft has become a major issue for such implementation
This doesn't take the Blazor prerendering model into account. The one where Blazor wasm is split between a server and client app. It's a shame. Microsoft shafted us with this model just to load the wasm slightly faster. All configurations are out the window having to do the same for both domains of the app.
prerender:false it is I guess. Remember to add and configure : .AddInteractiveServerRenderMode() along with the webassembly one. Goddamnit!
Thanks for your feedback! You’re right-Blazor’s prerendering model adds complexity, especially with managing configurations across server and client. While it improves load times and SEO, the trade-offs can be frustrating. For simpler apps, skipping prerendering might save effort.
@ Thanks for this great tutorial. Helped me a lot in changing the way I used authentication and claims in the past.
Very glad to hear this helps! 🥰