good initial study, but a real app requires mapping between 2 to 3 database entities, such as order, stock and good sql in the relationship between tables.
Hi Patrick, thank you for another Blazor CRUD video. I was wondering if you could make a video about a CRUD page for one entity which multiple foreigns keys in it ? We only work with one foreign key. I believe that the @code section in the product page is a lot different when we want to use multiple foreigns key. For example a customer with FK CustomerTypeId, AddresstypeId and for exampleTariffGroupId (different charges based on tariffGroup), which in the SQl are entitities on it's own, but in the Create page everything is combined.
I am curious about typical Blazor WASM standards for these front-end services. Is it preferable to call your API every time a page or component wants to access the Products listing? Or is more preferable to manage the state of the Products on the front end? So whenever you do a CRUD operation you are sending data to the API but also just updating/reading from to your local Product collection, that way you don't need to fetch the entire collection again every time a component wants to know about Products. I can't find too many tutorials or in depth standards for Blazor state management or what a good pattern is. Would be a good video idea to follow up on.
thx for your video, i have a question: why create the services both in the client and server? and also creating the same dependencies again in the client and server?
Hello Patrick Sir, You have been amazing Teacher regarding the .NET Web Api Series. I have purchased the blazor ecommerce as well. I had 1 simple doubt regarding the CORS policy for .NET 7. I have done many research regarding this but i was not able to get even though i followed the documentation of Microsoft. Any suggestion would be fine. Thank you
what if i created a standalone blazor wasn project that calls what i believe is an api.net api project. can i retroactively have my api serve my blazor files?
Thanks for this. Suppose I have a custom validation that uses Dictionary that is being returned by the Server, how would I handle it on the service layer of the client? should my Create/Update method return a Dictionary that contains the error? or its better to throw exception? Thanks!
🚀 Join the .NET Web Academy here: www.dotnetwebacademy.com/courses/academy?coupon=dnwapreoyt
Thank you very much for your invaluable contents. Keep up this great work!
You are awesome! Thank you soooo much! Really appreciate it!! ❤️
とても参考になりました。ありがとうございます
Where can i find the video where you do the Server side?
he will not answer beacuse he is selling the video on his channel
Thank you Patrick for this wonderful and clear video tutorial. :)
Thanks
Great stuff!
Thank you! 😊
Would you consider adding DTOs to future videos with API development so they more closely resemble Industry level work? That would be a huge help!
Muchas gracias.
38:28 @Patrick God, is correct insert navigation manager into service ?
Shouldn't it be placed in the Blazor component?
Came here to ask about this too.
Thanks for excellent content, Patrick!
good initial study, but a real app requires mapping between 2 to 3 database entities, such as order, stock and good sql in the relationship between tables.
Patrick, would it be possible to make a video on things like Azure and what we should know as developers in Azure?
Hi Patrick, thank you for another Blazor CRUD video. I was wondering if you could make a video about a CRUD page for one entity which multiple foreigns keys in it ?
We only work with one foreign key. I believe that the @code section in the product page is a lot different when we want to use multiple foreigns key. For example a customer with FK CustomerTypeId, AddresstypeId and for exampleTariffGroupId (different charges based on tariffGroup), which in the SQl are entitities on it's own, but in the Create page everything is combined.
I am curious about typical Blazor WASM standards for these front-end services. Is it preferable to call your API every time a page or component wants to access the Products listing? Or is more preferable to manage the state of the Products on the front end? So whenever you do a CRUD operation you are sending data to the API but also just updating/reading from to your local Product collection, that way you don't need to fetch the entire collection again every time a component wants to know about Products.
I can't find too many tutorials or in depth standards for Blazor state management or what a good pattern is. Would be a good video idea to follow up on.
I'm sure Patrick can help with that. You can also have a look here ruclips.net/video/sHuuo9L3e5c/видео.html
thx for your video, i have a question: why create the services both in the client and server? and also creating the same dependencies again in the client and server?
How would you get the userid in the aspnetuser table when you add authentication and add it with the crud?
Are there any lectures on "asp net core identity individual user accounts" in your lectures?
abount setting role, change user id string to int etc....
Hello Patrick Sir, You have been amazing Teacher regarding the .NET Web Api Series. I have purchased the blazor ecommerce as well. I had 1 simple doubt regarding the CORS policy for .NET 7. I have done many research regarding this but i was not able to get even though i followed the documentation of Microsoft. Any suggestion would be fine. Thank you
what if i created a standalone blazor wasn project that calls what i believe is an api.net api project. can i retroactively have my api serve my blazor files?
Thanks for this. Suppose I have a custom validation that uses Dictionary that is being returned by the Server, how would I handle it on the service layer of the client? should my Create/Update method return a Dictionary that contains the error? or its better to throw exception? Thanks!
Hi Patrick, could you share the demo code for this project?
There is no github repo... invalid link
Should work now. Thanks for reaching out! 😊
@@PatrickGod Thank You! And much appreciate your work, man!
First comment.
Congrats! 😉