StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POOverloading method's delegate parameter with an interface version
primarykey
Id
20082551
data
AcceptedAnswerId
20084780
AnswerCount
3
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-11-19T21:34:18.330
FavoriteCount
0
LastActivityDate
2013-11-20T17:50:45.923
LastEditDate
2013-11-19T23:51:30.407
LastEditorUserId
1127924
OwnerUserId
1127924
ParentId
0
PostTypeId
1
Score
1
ViewCount
107
LastEditorDisplayName
text
Body
Interesting problem here. I have a class that deals with System.Data elements that was original written to use concrete classes as parameters. It was recently updated to use interfaces instead so that we had greater compatibility with other databases. My problem comes from the following method, and its updated counterpart: Old: <pre><code>public bool Transact(Func<DbTransaction, bool> functionBlock) { ... Stuff ... } </code></pre> New: <pre><code>public bool NewTransact(Func<IDbTransaction, bool> functionBlock) { ... Stuff ... } </code></pre> The old version results in a <code>DbTransaction</code> object being spit out that we can send to other methods in our projects, while the newer one gives back an <code>IDbTransaction</code>. I named the updated version NewTransaction so that the older projects out there will not be broken should the end up sitting alongside the newer library (DLL Hell and whatnot). I can make rename NewTransact to Transact and it will compile just fine, but I don't see a way to call one over the other. My current solution will work just fine, but eventually NewTransact will no longer be "new". At that time, removing the old method and changing the name on the new one will just cause the problem to show up again. My question is: Is there a way to pick which specific method is called if they're both the same name? I'm guessing there isn't, but I figured this would make a good question. EDIT: The key component to this question is maintaining backwards compatibility. Any answer that would require updating old software to continue to function is irrelevant. If I wanted to go back and update other projects I would simply do that in the first place rather than creating these overloads.
Tags
<c#><interface><delegates><backwards-compatibility>
Title
Overloading method's delegate parameter with an interface version
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USLogarr
UserOwnerUserId
1. USLogarr
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
 POOverloading method's delegate parameter with an interface version
 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.