StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1170308
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2009-07-23T07:56:39.487
FavoriteCount
0
LastActivityDate
2009-07-23T07:56:39.487
LastEditDate
LastEditorUserId
0
OwnerUserId
45943
ParentId
1169188
PostTypeId
2
Score
24
ViewCount
0
LastEditorDisplayName
text
Body
I will go from top (presenter) and describe the relations between participants. Presenter gets service object through dependency. Service functionality is outlined using its contract: <pre><code>class Presenter { public Presenter(IService service) { ... } } </code></pre> Service implementation is abstracted from particular data access layer implementation. Basically whenever service performs some action that requires data source interaction it creates an instance of unit of work and disposes it when it finished. <pre><code>interface IService { void Do(); } class Service : IService { private readonly IUnitOfWorkFactory unitOfWorkFactory; public Service(IUnitOfWorkFactory unitOfWorkFactory) { this.unitOfWorkFactory = unitOfWorkFactory; } public void Do() { // Whenever we need to perform some data manipulation we create and later dispose // dispose unit of work abstraction. It is created through a factory to avoid // dependency on particular implementation. using(IUnitOfWork unitOfWork = this.unitOfWorkFactory.Create()) { // Unit of work holds Entity Framework ObjectContext and thus it used // create repositories and propagate them this ObjectContext to work with IRepository repository = unitOfWork.Create<IRepository>(); repository.DoSomethingInDataSource(); // When we are done changes must be commited which basically means committing // changes of the underlying object context. unitOfWork.Commit(); } } } /// <summary> /// Represents factory of <see cref="IUnitOfWork"/> implementations. /// </summary> public interface IUnitOfWorkFactory { /// <summary> /// Creates <see cref="IUnitOfWork"/> implementation instance. /// </summary> /// <returns>Created <see cref="IUnitOfWork"/> instance.</returns> IUnitOfWork Create(); } /// <summary> /// Maintains a list of objects affected by a business transaction and coordinates the writing out of /// changes and the resolution of concurrency problems. /// </summary> public interface IUnitOfWork : IDisposable { /// <summary> /// Creates and initializes repository of the specified type. /// </summary> /// <typeparam name="TRepository">Type of repository to create.</typeparam> /// <returns>Created instance of the repository.</returns> /// <remarks> /// Created repositories must not be cached for future use because once this /// <see cref="IUnitOfWork"/> is disposed they won't be able to work properly. /// </remarks> TRepository Create<TRepository>(); /// <summary> /// Commits changes made to this <see cref="IUnitOfWork"/>. /// </summary> void Commit(); } /// <summary> /// Represents factory of <see cref="UnitOfWork"/>s. /// </summary> public class UnitOfWorkFactory : IUnitOfWorkFactory { private readonly IUnityContainer container; /// <summary> /// Initializes a new instance of the <see cref="UnitOfWorkFactory"/> class. /// </summary> /// <param name="container"> /// Dependency injection container instance used to manage creation of repositories /// and entity translators. /// </param> public UnitOfWorkFactory(IUnityContainer container) { this.conainer = container; } /// <summary> /// Creates <see cref="IUnitOfWork"/> implementation instance. /// </summary> /// <returns>Created <see cref="IUnitOfWork"/> instance.</returns> public IUnitOfWork Create() { var unitOfWork = this.container.Resolve<UnitOfWork>(); unitOfWork.SetupObjectContext(); return unitOfWork; } ... other members elidged for clarity } </code></pre> The implementation of IUnitOfWork receives instance of IUnityContainer and then creates child container and registers ObjectContext instance there. This child container will be used to create repositories and propagate ObjectContext. Here is a simplified implementation of IUnitOfWork: <pre><code>class UnitOfWork : IUnitOfWork { private readonly IUnityContainer container; private ObjectContext objectContext; public UnitOfWork (IUnityContainer container) { this.container = container.CreateChildContainer(); } public void SetupObjectContext() { this.objectContext = ... // Create object context here this.container.RegisterInstance(context.GetType(), context); } public void Create<TRepository>() { // As long as we registered created object context instance in child container // it will be available now to repositories during resolve return this.container.Resolve<TRepository>(); } public void Commit() { this.objectContext.SaveChanges(); } } class Repository : IRepository { private readonly SomeObjectContext objectContext; public Repository(SomeObjectContext objectContext) { this.objectContext = objectContext; } public void DoSomethingInDataSource() { // You can use object context instance here to do the work } } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POEF ObjectContext, Service and Repository - Managing context lifetime.
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USDzmitry Huba
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COuuh that's good !
 singulars
 PostPostId
 PO
 UserUserId
 USRoubachof

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.