StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
13345008
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-11-12T13:56:00.223
FavoriteCount
0
LastActivityDate
2012-11-12T13:56:00.223
LastEditDate
LastEditorUserId
0
OwnerUserId
843984
ParentId
4677876
PostTypeId
2
Score
6
ViewCount
0
LastEditorDisplayName
text
Body
I'd recommend not sending enums over WCF interfaces. Suppose you have the following enum: <pre><code>[DataContract] public enum WeekdayEnum { [EnumMember] Monday = 0 } </code></pre> If you return the enum over WCF, everything will work well: <pre><code>[ServiceContract] public class Service1 { [OperationContract] public List<WeekdayEnum> GetWeekdays() { return new List<WeekdayEnum> { WeekdayEnum.Monday }; } } </code></pre> Add to the enum without updating the Service Reference in the client and you're still fine: <pre><code>[DataContract] public enum WeekdayEnum { [EnumMember] Monday = 0, [EnumMember] Tuesday = 1 } </code></pre> However, if you return the added value from the service without updating the client Service References, the legacy clients will break: <pre><code>[ServiceContract] public class Service1 { [OperationContract] public List<WeekdayEnum> GetWeekdays() { // NetDispatcherFaultException on legacy clients that only have Monday return new List<WeekdayEnum> { WeekdayEnum.Monday, WeekdayEnum.Tuesday }; } } </code></pre> I've had issues with this in projects where supporting legacy clients is important. The solution has been to simply send DTOs over the WCF instead of enums. E.g. the WeekdayEnum could be replaced by sending the values over a simple DTO: <pre><code>[DataContract] public class WeekdayDto { [DataMember] public int Id { get; set; } [DataMember] public string Name { get; set; } } </code></pre> This way, your legacy clients stay happy.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWCF Versioning Enums
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USLauri Harpf
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. This table or related slice is empty.
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.