Nicely organized series. I'm also building a project with similar web API backend and Angular frontend. I'm hoping you'll do an episode on securing the API with Azure ADB2C. My architectural challenge is to provide a way for multiple frontends to share the same database and member-space. This would permit all users authenticated for the API to use any of the frontends while accessing the same datastore of their personal activity.
Why not create a generic repository to handle all CRUD operations? Therefore, other repositories can inherit from the generic repository and you don't have to repeat yourself. You can also make the generic repo method virtual so you can override them and the generic repo can also be an abstract class so it can't be instantiated directly.
Is using repository pattern a best idea if in my environment backend going to be Microsoft sql server not matter what? should I just use angular calling the webapi and the api use the entity framework directly! please advice, thanks for the awesome series.
Repository pattern decouple your ORM (Entity framework), if you are sure you never need to change it in future and repository pattern will unnecessary add complexity and benefits are less, you can drop it.
Hope I could do that, but my full time job is not allowing me as it is too hectic to create a video in start of week. I work on these videos only on weekend. Teaching is my first love but I got married with full time job ;)
cant wait for this project to finish. thank you for all the contents
Your voice and explanation works me like a medicine. Thanks you very much..
Thanks Vasu :-)
Thanks. Very good explanation :)
love it. God bless you!
Thanks Raynaidy
Great job!
Nicely organized series. I'm also building a project with similar web API backend and Angular frontend. I'm hoping you'll do an episode on securing the API with Azure ADB2C. My architectural challenge is to provide a way for multiple frontends to share the same database and member-space. This would permit all users authenticated for the API to use any of the frontends while accessing the same datastore of their personal activity.
Nice thought, I had no plan for that, but now I will look how I can do that in this application. Added in my todo list.
Why not create a generic repository to handle all CRUD operations? Therefore, other repositories can inherit from the generic repository and you don't have to repeat yourself. You can also make the generic repo method virtual so you can override them and the generic repo can also be an abstract class so it can't be instantiated directly.
Yup we can do that
Is using repository pattern a best idea if in my environment backend going to be Microsoft sql server not matter what? should I just use angular calling the webapi and the api use the entity framework directly! please advice, thanks for the awesome series.
Repository pattern decouple your ORM (Entity framework), if you are sure you never need to change it in future and repository pattern will unnecessary add complexity and benefits are less, you can drop it.
@@StudyMash Thank you for super fast response.
Please enable subtitles like your other videos! Thank you.
anyway is it recommended to separate solution between frontend and webapi?
It doesn't make any difference, it is your personal preference.
Great tutorial so far sir.. One request. Can we please have two videos a week?
I know you are very busy but still if it is possible by any chance?
Hope I could do that, but my full time job is not allowing me as it is too hectic to create a video in start of week. I work on these videos only on weekend. Teaching is my first love but I got married with full time job ;)
@@StudyMash I totally understand it sir being a working professional :P. I am enjoying this series though. You are a great teacher. Keep it up.
Hi Can I get chance to work with you Please
Sure, we can, I was looking for some one who can help me to create some modules of this project
How to download code ?
This is hosted on github, below is the direct link to download code zip file
github.com/webtrainer-in/HSPA/archive/master.zip