Entity framework context as static

Question

In a web application it would be ok if i declare the context of a entity framework model as static? it would be ok? its not recommended? why? Thanks!

damn I'm glad you asked this - I stumbled across it by accident — Calanus, Jul 31 '09 at 11:58

score 34 · Answer 1 · answered May 20 '09 at 16:18

34

Almost definitely not.

ObjectContexts get bigger and bigger as more Objects are queried / saved.

Also sharing an ObjectContext between threads, as you would be doing, is not recommended, because of the locking issues and undeterministic side-effects you would have to deal with.

I wrote a tip on this topic a while back.

Tip 18 - How to decide on a lifetime for your ObjectContext

answered May 20 '09 at 16:18

Alex James

20,874
3
50
49

I was just going to link that post myself – aleemb May 20 '09 at 18:35

score 6 · Answer 2 · edited May 23 '17 at 10:31

6

This answer sort of answers your question, so does this one. I certainly wouldn't consider having it as static!

Rick Strahl has an in depth article on the lifecycle management.

edited May 23 '17 at 10:31

Community

1
1

answered May 20 '09 at 14:20

RichardOD

28,883
9
61
81

score 2 · Answer 3 · answered May 20 '09 at 14:21

I had done this the first time I implemented the entity framework. The problem was that the whole application was getting "completed" events so I had to do a lot of code figuring out where the call came from.

I decided to refactor so each page would have an instance of the context. I like it much better now.

/my experience

Entity framework context as static

3 Answers3

Linked