I'm working with writing some services that support the OAGIS (http://www.openapplication.org) set of messages. My problems are:
-OAGIS uses XMLÃÂ attributes all over, so IÃÂ can't use DataContracts (i have to use the XmlSerializer)
-OAGIS imports schemas all over, if I include all the xsd's needed to pass to svcutil for codegeneration off my filesystem, the path is too long and svcutil blows up.
I am trying to do the following:
1. Use xsd.exe or svcutil.exe to generate code that will get compiled into a DLL containing ONLY the data contracts (using XmlSerializer) for schema datatypes in OAGIS that are shared by all of their messages.
2. Use svcutil to generate code for WSDL files that come with OAGISÃÂ that reference the schemas in step 1, using the /r switch to pass the dll compiled in step 1 (so that the common types dont get re-generated).
I'm running into two problems.
-One, when I run step 2 its generating all the datatypes I pre-generated in step 1 anyway. I can't seem to get it to not regenerate them.
-Two, svcutil (in step 2)ÃÂ also generates code into justÃÂ one of the fourÃÂ namespaces I pass to it, but ignores all the others for some reason. Passing these same 4 namespaces to the first invoke of svcutil (in step 1)
View Complete Post