Should Entity Framework Context be Put into Using Statement?

by

If you create a context, you must dispose it later. If you should use the using statement depends on the life time of the context.

  1. If you create the context in a method and use it only within this method, you should really use the using statement because it gives you the exception handling without any additional code.

  2. If you use the context for a longer period – that is the life time is not bound by the execution time of a method – you cannot use the using statement and you have to call Dispose() yourself and take care that you always call it.

What does Dispose()do for an object context?

I did not look at the code, but at least I exspect it to close the database connection with its underlying sockets or whatever resources the transport mechanism used.

More Related Contents:

  1. There is already an open DataReader associated with this Command which must be closed first
  2. ‘Contains()’ workaround using Linq to Entities?
  3. Entity Framework Stored Procedure Table Value Parameter
  4. How can I automatically filter out soft deleted entities with Entity Framework?
  5. composite key as foreign key
  6. EF Code-First One-to-one relationship: Multiplicity is not valid in Role * in relationship
  7. Is it possible to capture a 0..1 to 0..1 relationship in Entity Framework?
  8. One to one optional relationship using Entity Framework Fluent API
  9. No connection string named ‘MyEntities’ could be found in the application config file
  10. How to compare only Date without Time in DateTime types in Linq to SQL with Entity Framework?
  11. Mapping composite keys using EF code first
  12. The mapping of CLR type to EDM type is ambiguous with EF 6 & 5?
  13. Filter all queries (trying to achieve soft delete)
  14. How to generate and auto increment Id with Entity Framework
  15. Missing ProviderName when debugging AzureFunction as well as deploying azure function
  16. SQL Injection attack prevention: where do I start
  17. Include with FromSqlRaw and stored procedure in EF Core 3.1
  18. get date part only from datetime value using entity framework
  19. ASP.NET Identity – Multiple object sets per type are not supported
  20. Entity Framework Code Only error: the model backing the context has changed since the database was created
  21. Getting all changes made to an object in the Entity Framework
  22. The LINQ expression could not be translated and will be evaluated locally
  23. Update records using LINQ
  24. Unable to edit db entries using EFCore, EntityState.Modified: “Database operation expected to affect 1 row(s) but actually affected 0 row(s).”
  25. Change db table name in EF4 (entity framework 4)
  26. Why is EF returning a proxy class instead of the actual entity?
  27. How does the SQLite Entity Framework 6 provider handle Guids?
  28. System.Data.Entity.Core.EntityCommandExecutionException Occurred in MVC app Using EF
  29. How to set Identity Seed value in code-first?
  30. How to write this EF Mock setup code as a reusable Generic Boilerplate?

Leave a Comment