StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POExplicit interface implementation cannot be virtual
primarykey
Id
7090122
data
AcceptedAnswerId
7090196
AnswerCount
6
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-08-17T08:52:42.650
FavoriteCount
4
LastActivityDate
2013-09-17T09:34:45.927
LastEditDate
2011-08-17T11:19:21.987
LastEditorUserId
778876
OwnerUserId
778876
ParentId
0
PostTypeId
1
Score
12
ViewCount
4883
LastEditorDisplayName
text
Body
For the record, I've already seen this <a href="https://connect.microsoft.com/VisualStudio/feedback/details/93163/allow-explicit-interface-implementations-to-be-virtual-and-to-be-called-from-derived-classes">connect item</a> but I can't really understand what would be the problem in supporting this. Say I have the following code: <pre><code>public interface IInterface { void Method(); } public class Base : IInterface { virtual void IInterface.Method() { throw new NotImplementedException(); } } </code></pre> what is the problem with the virtual identifier? Having a virtual modifier would make it possible to <code>override</code> indicating there's a different implementation in the base class. I can make it work now by removing the virtual method and creating the derived class like this: <pre><code>public class Derived : IInterface { void IInterface.Method() { throw new NotImplementedException(); } } </code></pre> however this way I've really no indication at all that I'm overriding something. Update: According to the C# (part: 20.4.1 Explicit interface member implementations) spec there are 2 reasons. <ol> <li>Hiding of certain methods (which I'm using it for). </li> <li>Having 2 functions with the same signature but different return types (usefull for IClonable for example).</li> </ol> It doesn't say anything however about why you can't make these methods virtual. Update2: Given the answers I think I should rephrase the real question here. If The above 2 reasons are the reason why explicit implementation of interfaces was made possible in the first place. Why would it be a problem if you make a method virtual. 
Tags
<c#><compiler-construction><interface><explicit-interface>
Title
Explicit interface implementation cannot be virtual
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USthekip
UserOwnerUserId
1. USthekip
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. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POExplicit interface implementation cannot be virtual
 UserUserId
 USRune Star
 VoteTypeVoteTypeId
 VTFavorite
2. VO
 singulars
 PostPostId
 POExplicit interface implementation cannot be virtual
 UserUserId
 USPraggie
 VoteTypeVoteTypeId
 VTFavorite
3. VO
 singulars
 PostPostId
 POExplicit interface implementation cannot be virtual
 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.