Gosh darn it MS guys, I mean ... excuse me a bit cause I'm a little
fustrated by having to include my external schemas into my WSDL definition
every time I make a chage because the WSDL.EXE is broke.
I'm refering to the following known problem:
http://support.microsoft.com/default...b;en-us;820122
BUG: "Unable to Import Binding from Namespace"
Error Message Occurs When You Try to Create an XML Web Service Proxy File by
Using the Web Services Description Language Tool
Any information on when this bug will be addressed?? if not is it at all
possible that the code could be shared so that the community can fix it. Its
really helpful to difine you schemas in externals file and use them in your
Contract descriptions (WSDL) when desiging your services from a contract
first perspective, but if the WSDL.EXE Code Generation tool cannot generate
the code properly, then consumers of the service will curse and think that
your contract is ill defined.
I really apologize to you all, please bare with me, this problem is just a
bit fustrating.
Cordell Lawrence
Teleios Systems Ltd.
