WPF

namespace WcfServer
{
    using System;
    using System.Runtime.Serialization;

    /// <summary>
    /// The contract that defines the customer structure.
    /// </summary>
    [DataContract]
    public class Customer
    {
        /// <summary>
        /// Gets or sets the customer forename.
        /// </summary>
        [DataMember]
        public string Forename { get; set; }

        /// <summary>
        /// Gets or sets the customer surname.
        /// </summary>
        [DataMember]
        public string Surname { get; set; }

        /// <summary>
        /// Gets or sets the date of birth of the customer
        /// </summary>
        [DataMember]
        public DateTime DateOfBirth { get; set; }

        /// <summary>
        /// Gets the Id of the customer.
        /// </summary>
        [DataMember]
        public int Id { get; internal set; }
    }
}

Johnny J. wrote:

But isn't it so (with reference to your example) that the Customer class with
its DataContract attributes needs to be defined and have identical definitions
on both sides of the WCF wall?

Mycroft Holmes wrote:

WCF does not allow a dynamic structure

void lbDirectiveList_SelectionChanged(object sender, SelectionChangedEventArgs e)
{
   Directive dire = (Directive)lbDirectiveList.SelectedItem;
   txtfilter.text = dire.DirectiveName;
   txtdesc.text = dire.Description;
}