Right, that makes sense.

Thanks for the update.

Imar
---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.
While typing this post, I was listening to: Singing The Blues by Tricky (Track 3 from the album: Angels With Dirty Faces) What's This?

Hi, I have a similar problem where rodmcleay's solution is no good.

For simplicity, say I have a very simple classlib (Common) that is used on both the client side and the server side of a web service.

namespace Common
{
  class Person
  {
    public string firstName, lastName;

    // FullName represents functionality used on both sides
    public string FullName {
      get { return firstName + " " + lastName; }
    }
  }
}

This class is used as parameters for a web service.
How do I get both sides to use the same type without having to cast?

I have done some research and only found "crappy" solutions to the problem.

The WebServiceBinding attribute looks promising, but I have not found any way to keep the classes I use in my web service from being replicated in the auto generated References.cs.

It's very easy to edit the References.cs-file manually to make it fit my classes. However, I am lazy and would like to not have to edit the References file every time I change the web service interface.

Any bright Ideas?

(

Best regards,
Torbjorn

I have same problem and tried referring to the class from webservice but the constructor(with parameters) is not accesible. As of now, i serialize and deserialize ... not happy though. Can some one help me with a easier solution?

Iam in same boat. I tried serializing and deserializing and it works. But if I refer to the class in webservice directly instead of local reference, I am not able to access the constructors of the classes. Any suggestions?