>I have a TCP webservice which ran fine until I added a dll containing some
> common objects to webservice.
[quoted text clipped - 6 lines]
>
> The dll is referenced, any ideas what the problem might be here?
The client and service can NEVER, EVER, share types. They are two unrelated
entities.
Consider: how would you solve this problem if the client was written in Java
and the service in .NET? You would bt unable to share the DLL. That's how
you should solve this problem, right after you remove from the client that
reference to types shared by the service.

Signature
John Saunders [MVP]
smesser - 27 Jul 2007 19:06 GMT
Yes, you are correct and my problem wasn't what I thought it was.
A developer that is working on this code after me added a new set of objects
to the
server and was mix/matching between to two sets. Therefore the generated
proxy code was giving the client problems.
I had initially thought that the client needed to reference the common dll
but in reality it just needed good proxy code to work with.
Thanks for your comment.
> >I have a TCP webservice which ran fine until I added a dll containing some
> > common objects to webservice.
[quoted text clipped - 14 lines]
> you should solve this problem, right after you remove from the client that
> reference to types shared by the service.