StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POHow to differentiate between various exception while calling a webservice in using .net?
primarykey
Id
2956030
data
AcceptedAnswerId
2956191
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-06-02T08:23:02.713
FavoriteCount
0
LastActivityDate
2010-06-02T09:37:00.910
LastEditDate
LastEditorUserId
0
OwnerUserId
104023
ParentId
0
PostTypeId
1
Score
0
ViewCount
146
LastEditorDisplayName
text
Body
I am consuming one webservice, while consuming there can different types expception might occur depeninding on various situation like.. network failur, invalid soap data or exception from serverside also might occur. How can I differntiate between these different excpetion? Because in my application, with these exceptions I need to update the various status Like: if network failure occurs Status will be "unable to connect webservice" so I can try after sometime later. If exception comes from Web server , no need to call/try again. nRk
Tags
<asp.net><web-services><c#-3.0>
Title
How to differentiate between various exception while calling a webservice in using .net?
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USnRk
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. PO
 singulars
 PostTypePostTypeId
 PTAnswer
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.