StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4105372
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-11-05T11:17:42.717
FavoriteCount
0
LastActivityDate
2012-02-09T11:51:31.470
LastEditDate
2012-02-09T11:51:31.470
LastEditorUserId
459406
OwnerUserId
459406
ParentId
2480927
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
I think you're looking for the <a href="http://www.springframework.net/doc-latest/reference/html/objects.html#objects-method-injection-lookup" rel="nofollow">lookup-method injection</a> feature. You have loaded the Spring.NET application context somewhere at the start. The code-based dependency on Spring.NET there is minimal. The problem is that everywhere you need an (adviced) service, you explicitly depend on Spring.NET with ContextRegistry.GetContext().. You can work around that with method replacement using lookup-method, example: Create an AbstractCommandFactory: <pre><code>namespace MyNamespace { public abstract class AbstractCommandFactory : ICommandFactory { public abstract ICommand getMyCommand(); } } </code></pre> Using Spring.NET you can getMyCommand return a Spring.NET object: <pre><code><objects> <object id="commandfactory" type="MyNamespace.AbstractCommandFactory, MyAssembly"> <lookup-method name="getMyCommand" object="commands.mycommand" /> </object> <object id="commands.mycommand" type=MyNamespace.MyCommandImplementation, MyAssembly" /> </objects> </code></pre> Now when you initialize the Spring.NET Application Context, load this command factory and pass the reference along. When you need an instance of MyCommandImplementation, you just request one from the factory instance: <pre><code>public void doSomeWork() { // factory is an ICommandFactory // instantiated earlier using the explicit context.getObject("commandfactory") ICommand myCommand = this.factory.getMyCommand(); myCommand.Execute(); } </code></pre> Now your explicit dependency on Spring.NET is very minimal: only at the initial load + instantiation of your factories. The rest of your code stays clean. Bonus points: you can more easily create ICommandFactory/ICommand mocks to unit-test your code.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POCan Spring.Net function as PostSharp?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. UStoong
UserOwnerUserId
1. UStoong
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. This table or related slice is empty.

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.