Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
Is 'Database Driven Development in windows' same as Application development uses Entity Framework. or is this (DB Driven Dev) has to use different framework or design?
Please comment. Thanks.
Database Driven Design is basically where you have the database design done first, then you program an application based upon the database. Database driven design
Entity Framework is a Object Relational Mapping tool. Using EF, you can do a "code-first" database design where EF will create your database for you, but that's still not database driven design.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
I work on school enterprise project and I need create data layer with design patterns. Can you give me some hint where to start and how patters could I use ? Thanks
Edit:
I have not use frameworks for ORM.
You could try the repository pattern and unit of work pattern
One of the common pattern for the data layer is the Data Access Objects. Anyway you can also use ready-to-use libraries such as the Microsoft Solution Entity Framework or NHibernate.
Also you can read this link with a lot of suggestions
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I'm looking for better architecture for my project which huge data (many stored procedures,views, tables).
Could anyone suggest which one is better - EF6 or Enterprise library to interact with data for better performance.
I know both are completely different thing. One is Object Relational Mapper and other is wrapper around ADO.NET. But i just want to know whether there will be any performance improvement if i just use enterprise library to access data in my project or should I go with the entity framework 6?
There are many stored procedures in my project.
Thanks
Definitely you should use Entity Framework 6 as Enterprise library is a little bit too old. You can achieve the same performance as pure ADO.NET using it but in most cases Entity Framework allows you to create code much faster (and that really matter).
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
I have a dispute with my colegue about how Entity Framework interacs with MS SQL SERVER.
We are arguing about if Entity Framework loads all the values from Db tables in Objects or not.
EDITED: when we select data using LINQ i my opinion LINQ query works with entity objects not direct with tables so the information in objects where previously obtained from the table.
The whole idea behind EF is to solve the impedance between relational an object oriented worlds, so, I don't see the point in your question..
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I need your opinion on which is better. In an ASP.net MVC project, is it recommended to have one DataModel for my whole database or one for each table in my database?
Note : I'm using EF dataFirst Model with a oracle database.
Lolz thats a nice question. I think you are new to MVC and EF.
Use one DataModel for the whole Database. Entity Frame work supports Oracle databse.
One DbContext represents one database. But, you can have mutliple databse in your project. So, you will have their respective DbContext's.
there are three approch to work with entity framework :
Model First
Data First
Code First
Configuring and using different approches are explained here
https://www.simple-talk.com/dotnet/.net-framework/different-approaches-of-entity-framework/
But, I personally prefer Database First.
If you want to learn more abt ASP.NET MVC with EF look here, Its with Data First
http://www.codeproject.com/Articles/695850/Complete-CRUD-Operations-in-MVC
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I want to generate C# code automatically, for data access in my asp.net projects. Which of the approaches (also why) is more suitable for automatic C# code generation: Entity Framework or ApexSql Code?
Please note that I'll be updating db model from time to time. I want to do this with minimal effort (e.g. without need to run a sql diff tool if possible).
I may be wrong, but I don't think ApexSql has code generation like EF. From what you have mentioned, it sounds like you want EF Code First.
Code-First Development with Entity Framework 4