datacontract

I have have a WCF derived/base contract issue. I have a server interface/contract that returns a BaseThing object: [OperationContract] BaseThing Get_base_thing(); The server that implements this has a DerivedThing (derived from BaseThing ) and wants to return this as a BaseThing . How to tell WCF that I only want to transport the BaseThing part of DerivedThing ? If in Get_base_thing I just return a reference to a DerivedThing then I get a SerializationException server side. I think I need to define a DataContractResolver and I looked at the MSDN article Using a Data Contract Resolver but this

Up to now, when working with WCF, I have always been exposing the whole either EF generated entities, or POCOs(by modifying the T4 template to include DataContract and DataMember on POCOs and properties) as DataContract. Now, I have come across a situation that I cannot expose the whole thing, and need to explicitly specify my DataContract to be a subset of the entities. It worth saying that one of my entities is something like below: And I want to just expose Id, Name, CategoryId, Price. Insert/Update of rest of the fields ( ActiveFrom , InactiveDate , Supported ) is something that will be

The following DataContract: [DataContract(Namespace = "http://namespace", Name = "Blarg")] public class Blarg { [XmlAttribute("Attribute")] public string Attribute{ get; set; } [DataMember(Name = "Record", IsRequired = false, Order = 4)] public List<Record> Record{ get; set; } } Serializes into this: <Blarg Attribute="blah"> <Record> <Record/> <Record/> <Record/> </Record> </Blarg> But I want this: <Blarg> <Record/> <Record/> <Record/> <Blarg/> The DataContractSerializer seems to be inserting the header parent automagically and I don't want it. How do I go about removing the wrapping <Record>

I'm using a class library that exposes a few objects. These objects have a couple of properties that hold data my clients need. I'd like to create a WCF service that returns the objects to my clients but I cannot update the class library in order to add the DataContract and DataMember attributes. What is the easiest way of exposing these objects? You can use a DataContractSurrogate . ...You can apply the DataContract attribute to the Person class, but this is not always possible. For example, the Person class can be defined in a separate assembly over which you have no control. Given this

i have two data classes which hold only data members(no functions). One is CallTask the other is SmsTask . These two classes have some common properties like ID , Tel . I put these common properties in a seperate interface class and i use this interface class in my project whenever appropriate. Now i added a WCFService to my project to share data between clients and server. Consider the following class design: public interface IGsmTask : IComparable { string TaskID { get; set; } string SessionID { get; set; } string Tel { get; set; } } class CallTask : IGsmTask { #region IGsmTask Members

My WCF service exports a single operation, marked with the catch-all action and reply action so that it represents a common entry point to the service: [ServiceContract] public interface IService { [OperationContract (Action="*", ReplyAction="*")] Message MyMethod (Message msg); } Client proxies are still generated as data contracts. What I'm finding, however, is that despite the client sending a data contract, when msg is serialized, the body appears to be the equivalent message contract to the data contract, not the data contract itself. Even this is fine, except that extracting the data