从WSDL生成代理

Question

I have a single self-contained (third party) WSDL file with say 10 operations. (server is not .net) All operations have their own XML namespaces defined for operations, messages and all the underlying types.

Some of the underlying types in different operations have same names and sometimes same content or same structure (not always) as well but they are actually different as they are defined in different xml/xsd namespaces (so they are unique).

When I import this WSDL into my c# client project, I can give it one unique namespace in the VS porject and it generates the proxy/stub. The problem is wherever the different operations have same (xml type) names for the underlying types then it generates the c# class names like: MyType1, MyType2...

Additionally the third party server, can update the service and so the WSDL is updated and the underlying types are generated again into .net classes like MyType1, MyType2... but this time, maybe previously generated MyType6 is generated as MyType7 and this breaks the client/consumer code.

What solution exists to address this problem?

We are thinking to customize the wscfblue code but it seem to be a cumbersome work and would require maintenance..

Environment:
-VS2013 Ultimate (Client)
-.net 4.5 (Client)
-Unknown technology (Server) -> generates WSDL and provides the endpoint.

Answer 1

You can generate the proxy using svcutil.exe and provide mappings from xml namespaces to CLR namespaces with /n. It also supports multiple mappings, which it sounds like you need.

Example: use svcutil to map multiple namespaces for generating wcf service proxies