I would like to know why this doesn't work too, as it is stalling a piece of
a project I'm working on. MS where are you?

Eirik M.

Its not in the SOAP spec for the InnerException property to be returned.
You will have to implement a custom solution.  I did this and it works fine.
You basically create a function that returns an XmlNode and create your
fault details there.  Then when you throw a SoapException, you pass the
method call the XmlNode and the soap exception.

This will return your SOAP fault properly.  Now to get the values on the
client side, you will have to manually create a method to return your
details either as an XmlDocument, XmlNode, or specifically make properties
that correspond to your InnerException elements and parse them out upon
instantiation of your Proxy class.  When your Proxy gens a SoapException,
pass it to your custom handler.

As an example, for a custom innnerexception property
"InnerExceptionMessage", when you encounter the SoapException, pass it to
your exception handler

catch(System.Web.Services.Protocols.SoapException se){
   myExceptionHandler myeh = new myExceptionHandler(se);
   string myInnerExceptionMessage = myeh.InnerExceptionMessage;
}

Your exception handler constructor would look something like this...

public myExceptionHandler(SoapException se):base (se.Message, se.Code,
se.Actor, se.Detail, se.InnerException) {
   XmlNode nMessage = null;

   nMessage = se.Detail.SelectSingleNode("InnerExceptionMessage");
   if(nMessage != null){
       sMsg = nMessage.InnerText;
       if (sMsg != null)
           this.ieMsg= sMsg;
       }
   }

note the "ieMsg" is declared as a private string to return from your custom
property of your myExceptionHandler class...

public string InnerExceptionMessage {
   get {
       return ieMsg;
   }
}

Hope this helps.

--------------------------------------------------------