StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
232459
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2008-10-24T04:02:52.853
FavoriteCount
0
LastActivityDate
2008-10-24T04:02:52.853
LastEditDate
LastEditorUserId
0
OwnerUserId
30809
ParentId
232357
PostTypeId
2
Score
7
ViewCount
0
LastEditorDisplayName
text
Body
I'll take a wild stab at this and say you probably want the office app to phone home to your exe? In this context, the "exe" is the server and the office app is the client. If you're using .NET 3.0, WCF is likely your best bet. I would structure the solution into three parts: <ol> <li>"Shared Contracts". These are interfaces that describe your services. If you have custom data objects that will be passed between the applications, they should be defined in this assembly as well. This assembly is shared between the client and the server. See "<a href="http://msdn.microsoft.com/en-us/library/ms733070.aspx" rel="nofollow noreferrer">Designing Service Contracts</a>" for more info.</li> <li>"Service". This assembly is your "exe" and it will reference the contracts and define the classes based on your service contracts. Your app will also host a ServiceClient for your service. The configuration file for this app will define how your ServiceClient will be exposed to the client (available as a web service, tcp, etc). See "<a href="http://msdn.microsoft.com/en-us/library/ms733764.aspx" rel="nofollow noreferrer">Implementing Service Contracts</a>" for more info.</li> <li>"Client". Your plugin will reference the "Shared Contracts" assembly and will contain service-clients based on the contracts. The client can be auto-generated using the svcutil.exe tool.</li> </ol> Both the "exe" and the "plugin" will require configuration files that define the bindings. When you want to pass data between client and server, your client will create an object from the "Shared Contracts" assembly and pass it to the service-client. The client's configuration file will figure out where to send the data. For a step-by-step tutorial on how to create a basic WCF service, <a href="http://msdn.microsoft.com/en-us/library/ms734712.aspx" rel="nofollow noreferrer">check out this Tutorial</a>.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to do intra-application communication in .NET
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USbryanbcook
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow to do intra-application communication in .NET
 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.