StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1499426
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2009-09-30T17:01:39.727
FavoriteCount
0
LastActivityDate
2009-09-30T20:28:56.963
LastEditDate
2009-09-30T20:28:56.963
LastEditorUserId
13087
OwnerUserId
13087
ParentId
1498772
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Try catch(Exception) on the client side, and inspect the type of the exception being caught as well as any inner exceptions. It might give some clues. Some other remarks: <ul> <li>ApplicationException is deprecated. You should normally derive from System.Exception.</li> <li>I normally add the [Serializable] attribute to custom exceptions. Not sure if this is important.</li> <li>You should normally override System.Exception.GetObjectData rather than explicitly implementing ISerializable.GetObjectData. In your case you're not serializing any additional data, so I would neither override it nor explicitly implement it. Again I'm unsure if this would have any impact.</li> </ul> My template for a serializable custom exception looks like the following, and I haven't had any problems with serialization over a remoting connection. <pre><code>[Serializable] public class CustomException : Exception { /// <summary> /// Initializes a new instance of the <see cref="CustomException"/> class. /// </summary> public CustomException() { } /// <summary> /// Initializes a new instance of the <see cref="CustomException"/> class with /// a specified error message. /// </summary> public CustomException(string message) : base(message) { } /// <summary> /// Initializes a new instance of the <see cref="CustomException"/> class with /// a specified error message and a reference to the inner exception that is a cause /// of this exception. /// </summary> public CustomException(string message, Exception inner) : base(message, inner) { } /// <summary> /// Initializes a new instance of the <see cref="CustomException"/> class with /// serialized data. /// </summary> protected CustomException(SerializationInfo info, StreamingContext context) : base(info, context) { } } </code></pre> UPDATE Also if you're hosting the server code in IIS, you need the following in web.config to allow exceptions to propagate to the client: <pre><code> <system.web> ... <customErrors mode="Off" /> ... </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PO.NET Remoting Exception not handled Client-Side
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USJoe
UserOwnerUserId
1. USJoe
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. 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
 VTDownMod
CommentsPostId
1. COI implemented my AuthenticationException per your custom exception template. The exception was still NEVER caught on the client side. The server halted with "AuthenticationException was unhandled by user code" Do I have to specify to the server application that there is a client willing and waiting to handle any exceptions that are thrown?
 singulars
 PostPostId
 PO
 UserUserId
 USDan Joseph
2. CO"Do I have to specify to the server application ..." - see update above
 singulars
 PostPostId
 PO
 UserUserId
 USJoe

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.