Related Posts
What shops are looking for new copywriters?!?
Location constraint:
I have got a very good offer that i cannot deny, but location is Hyderabad, I want this in Bangalore location. I am not onboarded yet, spoke to HR , he said it is not a big problem, Thoughtworks is very flexible.
Currently it is WFH, but once it is back to office.. I dont want to relocate. How easy it is relocate from Hyderabad to Bangalore, Thoughtworks
Additional Posts in .NET (Dot Net) Developers
New to Fishbowl?
unlock all discussions on Fishbowl.



Bowl Leader
I think using Entity Framework would help to build a Fully functional app with less time.Also we don't have to worry much about Database to .net object mapping ,framework does it for us. But when it comes to performance intensive operations developers still use stored procedure, views etc. Also sometimes it depends on the process setup in particular enterprise chose between EF and old way ,as there are restrictions in connecting to prod environments.
I would always chose Entity Framework if it is accepted by an enterprise & will use Stored procedure,views,raw sql etc. When ever complexity increases.
Entity Framework is an ORM(Object Relation Mapper). There are other ORMs as well like dapper. Entity Framework is official ORM for .net created by Microsoft. This is the basic concept.
Now coming to your question, yes, using ef is considered better in most cases, especially in web application/services development.
ORM is the concept which is implemented using ef. Read about ORM first, it will give whole picture and make learning easier. Learn from Kudvenkat Youtube videos.
oh thanks
First learn basic ado. Net, then move to EF.