Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>There are a few ways to <a href="http://msdn.microsoft.com/en-us/library/ms730167.aspx" rel="nofollow">register known types</a>. But first please study the <a href="http://msdn.microsoft.com/en-us/library/ms733127.aspx" rel="nofollow">articles</a> concerning DataContracts and the <a href="http://msdn.microsoft.com/en-us/library/ms731923.aspx" rel="nofollow">types supported by the DataContractSerializer</a>. </p> <p>Note that you didn't add the <code>DataContract</code> attribute on the <code>DerivedClass</code> <code>BaseClass</code>. Although classes marked with the <code>Serializable</code> attribute are valid and can be exposed in WSDL, the <code>DataContractAttibute</code> has serialization rules designed for interoperability and it is the preferred serialization mechanism for WCF.</p> <p>If you decide to register known types on the data contract then this should be enough:</p> <pre><code>[DataContract] public class DerivedClass : List&lt;BaseClass&gt; { /// ... } [DataContract] [KnownType(typeof(DerivedClass))] public clas BaseClass { //Add the DataMemberAttribute to the properties you want serialized. } </code></pre> <p>If you want to register the known types on the service contract level you add the <code>ServiceKnownType</code> attribute on the <code>ServiceContract</code>.</p>
    singulars
    1. This table or related slice is empty.
    1. POWCF call fails when serialize base class which is a generic List<>
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USPanos Rontogiannis
    1. USPanos Rontogiannis
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COBaseClass is defined as you have noted. The Client simply derived from that class to take advantage of the generic List<> operators/methods; The implementation would work if the client simply went the has-a approach rather than a is-a approach; that is, if the client didn't derive from List<BaseClass> but rather made it a property. But this would look clunky. Is it necessary for the serivce to know about derived implementations of List<BaseClass>? Seems not, the client needs to send the List<BaseClass> over; the client derived clss should be hidden from serivce
      singulars
      1. PO
      1. USMoe Howard
    2. COYou do not have to add it at the service contract AND the data contract level. One is enough. Another alternative is the configuration file or using the KnownTypeAttbibute .ctor that takes as parameter the name of a helper method returning an IEnumerable of known types. Anyway I can't see the point of your derived class. It makes your design harder to understand without any benefits (visible from your example and comments). Remove the derived class and use IList<T> or IEnumerable<T> in your service operations. This way you encapsulate the collection type and have simple maintainable code.
      singulars
      1. PO
      1. USPanos Rontogiannis
    3. COThe derived class is purely to operate on the List<BaseClass> and that is it. Just helper functions. Like functions that operate on the List<BaseClass>; for example, Set all item properties of the list to a value given some conditions and to calculate some values against the List<BaseClass>. Basically, all the data and operations is contained in DerivedClass rather than having a seperate "Helper" class that we need to create each time we need to perform a common tasks. Now if you are to say that having two classes (Derived and Helper) is a good design, I disagree.
      singulars
      1. PO
      1. USMoe Howard
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload