tags:

views:

16

answers:

0
Q: 

EF where to create and dispose a context? In business layer or in the repository?

Is it better to create and dispose a context in the repository class? or is it better to create the context in the service and pass it to each repository through dependency injection?

If it is only created in the repository, the methods cannot do lazy loading (no use returning IQueryable) in the service/business layer.

related questions

SQL tracing LINQ to Entities
SQL Anywhere 11 (Sybase) with Entity Framework in Visual Studio SP1?
ADO.NET Entity Framework and identity columns
Is anyone using Entity Framework with an Oracle database?
LINQ to entities - Building where clauses to test collections within a many to many relationship.
Entity Framework: how to return a base type from L2E
Unit Testing in .NET: How to Mock Entity Data Provider
Entity Framework - Can you map the result type of an imported stored procedure to a custom entity type?
Entity Framework and Application Architecture (loose coupling, etc)
Can you use Microsoft Entity Framework with Oracle?
Using MySQL with Entity Framework
How to Implement Database Independence with Entity Framework
What is the best data access paradigm for scalability?
ADO.NET Entity Framework tutorials
How do you create a database from an EDM?
Anyone using the Entity Framework *Well*?
What real-world usages of ADO.NET Entity Framework do you know?
Which ORM framework can best handle an MVCC database design?
Where to start with Entity Framework
How to customize Entity Framework classes?
Linq to Entities vs ESQL
ADO.NET Entity vs NHibernate
Update database schema in Entity Framework
Expression.Invoke in Entity Framework?
Entity Framework vs LINQ to SQL