I have winforms that accesses the data layer via web services. Exception occurred on the data access layer and I put try{}catch{} statements on the client layer(winforms) to capture the exception. The original exception type is SqlException but when the try{}catch{} on the client(winforms) captured the exception of diffent type which is SoapException.
My question is can I make the SoapExcepton return to its original exception which is SqlException
Is it possible to get back my original exception (From SoapException to SqlException)
Hot Topic
- How can I duplicate elements in a windows for - like groupboxes or image objects
- Migration from .net to vs2005
- !!! IF MICROSOFT HEAR US!!!
- How I can add button efects?
- C# Needs a Property keyword like MC++ has now
- Could I "inlcude" a C# source file?
- Unable to update the dependencies of the project
- Keep getting exception message that Type is not marked as Serializable
- Printing an image
- How to create local instance of the remote object
Visual C#
- Checking values of variable at runtime.
- No clue about arrays, everything fails ...
- InvalidCastException , Exception from HRESULT: 0x80004002 (E_NOINTERFACE)
- Generics and "==" or "!="
- copy data from an pointer
- Does using(IDisposable) induce boxing?
- Formatting a string
- Is the new Media Foundation a replacement of Direct Show?
- Intellisense is missing a class.
- Missing character in string
Is it possible to get back my original exception (From SoapException to SqlException)
Nasyua
rfreire
Well basically, no you can't get anything except a soap exception at the client end. Avery's blog has some information on this topic and explanations why. Basically, the soap exception you are seeing is transposing the inner exception as the 'SoapFault'. Avery suggests that you >COULD< serialize your inner exception into the Soap exception however then you would need to deserialize the soap fault message to determine what the original error was. This would probably be better suited to simply use numerical fault codes to indicate why the error occurred. This is by design to facilitate loose coupling in the web service world.
http://dotavery.com/blog/archive/2004/02/10/472.aspx
- David Sandor