VS2005/.NET 2.0 does a really good job of serializing classes. A lot of the
types and collections (like the infinitely very useful List(of <T>)) and
even deeply nested classes are recognized by the serializer and turned into
XML primitives and arrays and defined in the WSDL. The client (.NET, Java,
or whatever) should have no trouble reconstructing these classes... they're
described quite well in the WSDL.
However, this is only practical for classes that contain only data (document
paradigm)... not for classes that contain built-in validation or otherwise
do "work" (entity paradigm).
--
-C. Moya
www.cmoya.com
"Mantorok" <sp******@spam.com> wrote in message
news:3a**************************@news.rmplc.co.uk ...
Hi all
I have a web-service that references another project (the component) that
actually carries out the work, the web-service is simply acting as the
public interface.
The web-service on occasion may return a class that is defined in the
component project.
When I reference the web-service from a new project will it pick up these
classes that are defined in the component project? Or will they be ignored
and I'll end up with a broken web-service.
The reason I'm asking is because Beta 2 failed to do this and I'm not sure
if the released version will work, and unfortunately I haven't got time to
check it.
HTMS
Any ideas?
Thanks
Kev