21 | Repository Pattern In ASP.NET Core 6 | ASP.NET Core Repository Pattern | Models (Hindi/Urdu) 

Glad it was helpful!

User does not necessarily means the user who is using the application through UI. It also means another company or developer. For example, you azure services or any othe package that performs some service for you. You use their service in you code but don't know they have done in the code. That really what abstraction is I hope I am clear and it makes sense. Let me know😊

@@raj_k_dev oh brother thank you Very much i got your point... But why it's recommendation in coding website because we are not developing package there So if we are building a website that that is of no use correct?? I saw interface is recommending to use. Can you please clear it for me.?.

What ever example I will give you it will confuse you . Give me an example with which you want understand and I will explain you you r example. Coming to interfaces they have many benefits apart from abstraction like reusability, stability and testing etc. For example if you an employee interface and you implement it in internal employees with DoWork() if tomorrow there is another employee type comes as external you can implement the same interface DoWork and code accordingly. Since you are using abstraction you initial code where you call do work does not need to change much. Now one question coming to your are mind that why not use class it self without interface, in that case you have to create multiple object for each these class then place condition statements. I know it will make you more confusing to read this explanation that is why I said give you own example where you want to know why we use it. Might create a video on this topic myself as it is always confusing to beginners/ experience devs to.

as in video said that Repository patterns helps in loosely couple approached means when we change anything in any class or in any object so it does not affect any other class or object

In general, writing methods in camel case is not a bad practice. In fact, camel case is a common convention for naming methods in many programming languages and frameworks. Camel case is a naming convention where the first letter of the first word is lowercase, and the first letter of each subsequent word is capitalized, with no spaces between the words. For example, "getUserInfo()". However, it's important to note that different programming languages and frameworks may have different naming conventions. For example, some may prefer snake case (where words are separated by underscores) or pascal case (where the first letter of each word is capitalized, with no spaces). Ultimately, the most important thing is to be consistent with the naming convention used in the language or framework you are working with, or with the conventions agreed upon by your team. This will help make your code more readable and maintainable. If you are working on your own, you can choose whichever naming convention you prefer, as long as you are consistent with it throughout your code.

​@@programentorsir dapper PR vedio bnaye