We are undergoing a migration from classic ASP with SQL and Sprocs. Our choice fell upon c#.net 4 Webforms with Entity Framework 4.
My question is how to handle the context. Example:
Calling repository function GetProductById(), which open up a new context (using) and then we change something on the object and we save it.
When we save it we wont be in the same context as when we fetched the object.
The above didn’t really work for us. We then tried to send the context around in our application. While this worked we didn’t really want to work this way if we didn’t have to.
We are currently using a third option, storing the current context in a global variable. We dispose the context when we have saved it. However we’re not sure if this is a viable way in the long run or if we’re to hit a wall with this method.
We’ve tried to search for best practices on this topic but not really been able to find any. Would appreciate and help on this topic.
The Unit of Work pattern described in this article might help, although the examples in the article are with an MVC app rather than an WebForms one.
http://msdn.microsoft.com/en-us/ff714955.aspx