modular wsdl for client creation?

[=?Utf-8?B?TWFyaw==?=]

Hi...

I'm trying to separate the definitions for the object types a web service
will act on from the wsdl file, moving them into a separate schema.
Basically, my wsdl has an
<xsd:import namespace="foo" schemaLocation= ".\objects. xsd"/at the top.

I was hoping to do this because the objects may be useful to different types
of services in different places.

I'm having a problem, however, getting a web reference to make the right
client code. I enter a file:/// url in the Add Web Reference window with the
wsdl and xsd locally (have to let the embedded IE load local files). The
wizard pulls up the files and I see the list of methods in the pane but when
I go ahead and say Add Reference, I get compilation errors saying that it
can't find the datatypes to make code from

Is this something I just shouldn't be doing? I've tried xsd:import and
xsd:include but they both through similar kinds of errors.

Thanks
Mark

[Steven Cheng[MSFT]]

RE: modular wsdl for client creation?

Hi Mark,

How are you doing on this issue, does the information in my last reply help
you some?

If you have any further questions, please don't hesitate to post here.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


This posting is provided "AS IS" with no warranties, and confers no rights.