* Relax faultcode parsing for Soap11 message errors.
The mono implementation was reading the faultcode content as an XmlQualifiedName, which applied the rule where you could not
start a name with a number. This caused interoperability problems with the .net framework because their parsing just looks
for <namespace>:<name>, where name can be any string.
Example:
<faultcode>s:1</faultcode>
On mono, a soap response that contains a fault code name of 1 will throw an error. If you run the same code on the .net framework, it will not.
Fixes https://github.com/mono/mono/issues/12995
* [csproj] Update project files
It's an optional element according to [1] and we were simply
throwing a NotImplementedException when encountering it.
Fixed by reading the element value instead. I noticed that we
had a 'details' variable that was never assigned, so the check
for `details == null` was always true and can be removed.
This makes inlining the body of the CreateFault() call easier
since we no longer need to choose different overloads and makes
the code consistent with the CreateFault12 method.
Also added a better exception in case of an unrecognized element.
The CreateFault12 method (handles SOAP 1.2) does not need a similar
fix since actor is not an element in that version [2].
Fixes https://bugzilla.xamarin.com/show_bug.cgi?id=42226
[1] https://www.w3.org/TR/soap11/#_Toc478383507
[2] https://www.w3.org/TR/soap12/#soapfault
* MessageFault.cs : support EnvelopeVersion.None as well, as almost
the same as SOAP12.
* MessageFaultTest.cs : add CreateFault test with MessageVersion.None.
svn path=/trunk/mcs/; revision=148797
* MessageFault.cs : Reason is mandatory. raise XmlException, and
CommunicationException in each CreateFault().
* soap-fault-incomplete.xml : new test file.
* MessageFaultTest.cs : new test.
* System.ServiceModel.dll_test.sources: added MessageFaultTest.cs.
svn path=/trunk/mcs/; revision=134197