StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7654362
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-10-04T21:38:29.650
FavoriteCount
0
LastActivityDate
2011-10-04T21:38:29.650
LastEditDate
LastEditorUserId
0
OwnerUserId
234
ParentId
6140211
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Although it looks like you're doing the same thing both times, it's actually completely different: In the first code example: <pre><code>dynamic connection = fc.Connection; connection.System = ""; </code></pre> what happens is you get <code>fc.Connection</code>, and then invoke the <code>System =</code> property setter using <code>dynamic</code>. The dynamic language runtime goes off and queries the COM interfaces, and invokes a particular method on a particular COM interface. You can't actually see what interface or method it's using from the C# side of things. In the second example (I've replaced the <code>var</code> to make things more clear): <pre><code>SAPLogonCtrl.Connection connection = fc.Connection as SAPLogonCtrl.Connection connection.System = ""; </code></pre> what happens is you get <code>fc.Connection</code>, and then cast it to <code>SAPLogonCtrl.Connection</code>. You then try and call <code>SAPLogonCtrl.Connection.System =</code> and then it fails. I suspect that it's failing because the object is not actually an instance of <code>SAPLogonCtrl.Connection</code> but it may be a proxy or some other object. Most COM interop is split into an interface (there's most likely an <code>SAPLogonCtrl.IConnection</code>) and a class. When calling methods, you usually need to call through the interface. The <code>dynamic</code> code will be doing it all for you behind the scenes. You could try searching for the interface, and calling using that. If it ends up that <code>SAPLogonCtrl.IConnection</code> exists, the solution may be as follows. <pre><code>var connection = fc.Connection as SAPLogonCtrl.IConnection // note the I! connection.System = ""; </code></pre> At any rate, remember to call through the interface when dealing with COM interop
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODynamic vs Typed produces strange results
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USOrion Edwards
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PODynamic vs Typed produces strange results
 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
 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.