Warning: Fault named ApiException in operation copyCampaigns cannot be imported. Unsupported WSDL, the fault message part must reference an element. This fault message does not reference an element. If you have edit access to the WSDL docum ent, you can fix the problem by referencing a schema element using the 'element' attribute.
In any case, the difference between ASR and Svcutil.exe is that one has the UseSerializerForFaults option easily available to you as a switch on the command line. Using this switch instructs Svcutil.exe to use the XmlSerializer to handle faults instead of the default, which is the DataContractSerializer. In this case, although Svcutil.exe has indicated that the WSDL for the fault is flawed, it continues to import the service operation. If you want to enable VS ASR to do the same thing:
- Click Show All Files in the Solution Explorer.
- Open the Reference.svcmap file in your service reference.
- Set the option <UseSerializerForFaults> to false in Reference.svcmap and save it. (NOTE: Take care NOT to update the service reference, as doing so resets the option to true.)
- Open the reference.cs and you should see the operations generated.
Read more: Ralph Squillace -- Docs, Samples, Docs, Samples....
Posts
