StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18230221
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-08-14T11:14:10.857
FavoriteCount
0
LastActivityDate
2013-08-14T11:14:10.857
LastEditDate
LastEditorUserId
0
OwnerUserId
745969
ParentId
18228962
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
Services expose methods (Operation Contracts) to the client. Your interface doesn't have any methods, so there's nothing to implement (from a service perspective). You could do something like this: <pre><code>[ServiceContract] public interface INewUser { [OperationContract] UserInfo CreateNewUser(string userName); } </code></pre> Then in the implementing class, you'd have: <pre><code>public NewUser : INewUser { public UserInfo CreateNewUser(string userName) { return new UserInfo() { UserName = "John Doe", UserRole = 5, LoweredUserName = "john doe" }; } } </code></pre> <code>UserInfo</code> would be the class used to represent the info, per your original code, marked as a data contract: <pre><code>[DataContract] public class UserInfo { [DataMember] public string UserName { get; set; } [DataMember] public int UserRole { get; set; } [DataMember] public string LoweredUserName { get; set; } } </code></pre> This is a trivial example based on your above code, to show you how it can all go together. HOWEVER What you really should do is look at your existing library, wrap the functionality in a WCF service, and mark the <code>NewUser</code> class up as a data contract. It looks like you're focusing on the data, and you should first focus on the functionality. Put another way, what methods in your current library use <code>NewUser</code>, as either inputs or return types - that is what goes into the service, not the properties of the <code>NewUser</code> class.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POConverting a Get/Set class into a WCF service
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USTim
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POConverting a Get/Set class into a WCF service
 singulars
 PostTypePostTypeId
 PTQuestion
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
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
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.