support for FaultContractAttribute in service definition wsdl generated by XmlSerializer

[edgridin]

To achieve similar behavior with DataContract serializer, it will be ensured, that the naming of fault contract message ends with suffix Fault - if the class ends with Fault, the name remains, otherwise the suffix is added.

For each specified FaultContract attribute

• an element is added
  <xsd:element name="OperationFault" nillable="true" type="tns:OperationFault" />

• a corresponding complex type is specified

      <xsd:complexType name="OperationFault">
        <xsd:sequence>
          <xsd:element minOccurs="0" maxOccurs="1" name="Code" type="xsd:string" />
          <xsd:element minOccurs="0" maxOccurs="1" name="Message" type="xsd:string" />
        </xsd:sequence>
      </xsd:complexType>

• fault is added after input and output messages under portType -> operation
  <wsdl:fault name="OperationFault" message="tns:IServiceWithFaultContracts_GetEnum_OperationFault_FaultMessage" />

• fault is added after input and output messages under binding -> operation

      <wsdl:fault name="OperationFault">
        <soap:fault use="literal" name="OperationFault" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" />
      </wsdl:fault>

[edgridin]

hi @andersjonsson ,
sorry for disturbing, I know, we all are busy with other projects, but maybe you could take a look at this PR?
Thank you in advance.

best regards,
Ed

[andersjonsson]

TBH I don't know enough about Faults to be sure but it looks fine to me 😅

[edgridin]

thank you @andersjonsson !
I don't know that much about Github, but do you think, it could be possible, to have kind of continuous delivery? So that a PR merged in develop would automatically publish a new package version on Nuget?
Would save some time for you and other maintainers, don't you think?

Best regards,
Eduard