StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
5941482
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-05-09T19:24:57.777
FavoriteCount
0
LastActivityDate
2011-05-09T19:30:29.847
LastEditDate
2011-05-09T19:30:29.847
LastEditorUserId
400223
OwnerUserId
400223
ParentId
5926447
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
This answer is to elborate my thoughts on this interesting problem. Not a real answer, but a contribution to the whole discussion that is too small for a normal comment. I checked a few things, this interface: <pre><code>namespace DifferentAssemblyNamespace { public interface IBar { event Action<dynamic> OnSomeEvent; } } </code></pre> and its implementation: <pre><code>// implicit interface implementation // generates compile error "Explicit interface implementation" public class Foo1 : IBar { private Action<dynamic> foo; public event Action<dynamic> OnSomeEvent { add { foo += value; } remove { foo -= value; } } } // implicit interface implementation // generates compile error "Not supported by the language" public class Foo2 : IBar { private Action<dynamic> foo; event Action<dynamic> IBar.OnSomeEvent { add { foo += value; } remove { foo -= value; } } } </code></pre> will never work, seems that one rule is excluding the other necessary rule. but.. if we call generics for help, and use a Type parameter instead of using <code>dynamic</code> directly like: <pre><code>namespace DifferentAssemblyNamespace { public interface IGenericBar<T> { event Action<T> OnSomeEvent; } } </code></pre> and its implementation. <pre><code>// implicit interface implementation public class Foo3<T> : IGenericBar<T> { private Action<T> foo; event Action<T> IGenericBar<T>.OnSomeEvent { add { foo += value; } remove { foo -= value; } } } </code></pre> for some reason we can build (as it should) and run: <pre><code>/** does build **/ IGenericBar<dynamic> f = new Foo3<dynamic>(); f.OnSomeEvent += new Action<dynamic>(f_OnSomeEvent); </code></pre> seems that the Type Parameter does something extra that the compiler is happy with. I am not sure what is going on, so I would like to know as well. assumption, highly hypothetical (perhaps crap) <blockquote> but currently I put my two cents on the comparison of types there must be made via the add/remove accessors in the linked list that holds the target/methods of the event. I bet that the compiler falls over the problem that it cannot guarantee what dynamic is in the external assembly, thus cannot determine if an element is already in the list or not, which is necessary to add or remove them.(Hence explicit interface implementation) We all know it is just some of a attributed object but it still seems that it needs an extra step where some strong-type is guaranteed, and that is what T does, at compile time. </blockquote> / assumption, highly hypothetical (perhaps crap)
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PO"cannot implement interface member" error when interface and concrete are in different projects
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCaspar Kleijne
UserOwnerUserId
1. USCaspar Kleijne
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.