1 minute read
When coding against team foundation server you must be aware that some of the exceptions thrown by Team Foundation Server are not Serilisable! I think that this was an oversite by Microsoft, but it is there none the less.
An example of this is; TeamFoundationServerUnauthorizedException
If you want to handle this exception accross Windows Communication Foundation you will need to create a custom exception of the same name and re-throw this accross your services.
<DataContract()> _
Public Class TeamFoundationServerUnauthorizedException
Public Sub New()
…
End Sub
End Class
Make sure that you mark it as a data contract and then you can throw it when you encounter the Team Foundation Server exception:
Try
’ Team Foundation Server Connection Code
Catch ex As TeamFoundationServerUnauthorizedException
Throw New FaultException(Of FaultContracts.TeamFoundationServerUnauthorizedException)(New FaultContracts.TeamFoundationServerUnauthorizedException())
Catch ex As System.Exception
Throw New FaultException(Of System.Exception)(ex, “Failed to do team server thing”, New FaultCode("Team Foundation Server:EH:S:0001"))
End Try
This will allow you to handle Team Foundation Server exceptions for your Windows Communication Foundation service application on the client.
Subscribe to Martin's articles
Writing since 2001
Articles, usually weekly on Mondays. One click to leave.
Was this useful?
Enjoyed this? One click, no account.
Smart Classifications
Each classification [Concepts, Categories, & Tags] was assigned using AI-powered semantic analysis and scored across relevance, depth, and alignment. Final decisions? Still human. Always traceable. Hover to see how it applies.