StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16447256
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-05-08T17:59:57.243
FavoriteCount
0
LastActivityDate
2013-05-08T17:59:57.243
LastEditDate
LastEditorUserId
0
OwnerUserId
1816704
ParentId
16440988
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
ASP.NET has a type of Dependency Injection built-in. What that means is that instead of having a hard reference to a specific class, the controller has references to interfaces. The <code>Resolver</code> is then configured to return a certain type when an instance is requested. For example (sample code, I don't know the exact methodnames) <pre><code>Resolver.Bind<IActionInvoker>().To<ActionInvoker>(); // if an IActionInvoker is requested, return an instance of type ActionInvoker. </code></pre> After this configuration a call to <code>GetService</code> will get you an instance of <code>ActionInvoker</code> So, to answer your questions: <ol> <li>How the IActionInvoker interface is instantiated over here, and returned by ActionInvoker property ?</li> </ol> <blockquote> <blockquote> by configuring the resolver in before hand, the resolver knows which type to create and return </blockquote> </blockquote> <ol> <li>Does the reference to the property returns an object of AsyncControllerActionInvoker class, so that we can use that object to make a call to InvokeAction(ControllerContext, actionName) method.</li> </ol> <blockquote> <blockquote> Yes and no. Yes the property will assure that you have an object which implements <code>IActionInvoker</code> which you can use to call <code>InvokeAction</code>. And no, your not guaranteed that it is of type <code>IAsyncActionInvoker</code> (depends on the configuration of the resolver) </blockquote> </blockquote> <ol> <li>What the does Resolver.GetService() and Resolver.GetService() do ?</li> </ol> They ask the resolver to instantiate an object that implements the given Interface. The resolver will look up the interfaces in its configuration, instantiate the appropriate object and return it to the caller. Dpendency Injection is a way to decouple your code. Since you only reference the interface, you have no hard dependencies and you could just reconfigure the DI container (<code>Resolver</code> in this case) and you will be using another class, without your client class ever knowing about it.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POExecuteCore() method in ASP.NET MVC
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USKenneth
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
CommentsPostId
1. COMany many thanks, was very helpful for me in understanding the topic. Could you suggest me some links from where I can know more about this topic and about ASP.NET built in dependency injection ?
 singulars
 PostPostId
 PO
 UserUserId
 USBibhu

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.