I have to develop a service that will use types specified in a given XSD Schema (let's called this ACME.xsd) and I am wondering if anyone can help me with my problem of using this XSD right through including producing the WSDL.
I can generate C# classes from this ACME.exe using xsd.exe because its XML syntax is beyond the capability of SvcUtil.exe. With these classes, I can develop the ServiceContract and the service. All is fine.
I can produce the Service Contract WSDL and companion XSD Schema using SvcUtil.exe and I also noticed that it generates a schema containing the types I used that came from ACME.xsd. However, the content of this xsd and that in ACME.xsd are somewhat different.
The most noticeable differences are the targetNamespace and most of the xsd specification like restrictions and annotations are lost in this regenerated XSD.
1) Is it possible to instruct WCF to keep that XSD with it including the generation of WSDL? My Service Contract has to use these types in ACME.xsd because of interoperability issue.
2) I know if I do Contract-First approach, I most likely I can achieve what I want. But is it possible to achieve what I want by using WCF as an aid?
Thanks. Is there any smart way of doing this?
View Complete Post