Home/ Questions/Q 643117
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T21:14:53+00:00

We have a service reference that points at a WCF service, this acts as

  • 0

We have a service reference that points at a WCF service, this acts as a proxy to our model layer where our data access logic is being handled. Under the hood we are using Linq2Sql as the ORM to facilitate the database communication.

We use the generated classes as our data access layer, but what gets returned is actually dumb DTOs objects which are nothing more then POCOs. I would like to do two things)

1) Control what is available on the client through the service reference in terms of custom types and their associated properties. This is to reduce the size of the classes going down.

2) I know that Linq2Sql is actually decorating all of the generated classes with but I do not want these classes coming down through the service reference.

At present, if we use the class as a return type of input parameter it gets serialized. This is fine, except I would like to restrict what properties are available

Thoughts?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    So I found this out. Basically when you create a service reference only the types that are used in some way are serialized down. By default, if no DataContract is present, everything is serialized.

    If a DataContract is present, it will look for DataMember decorated properties and serialize those only. Tricky

    • 0