Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It looks like this may be a Mono <code>XmlSerializer</code> limitation. I have a small test app which works under .NET, but not under Mono 3.0.6.</p> <p>But this looks fairly simple to work around:</p> <pre><code>[XmlIgnore] public Texture2D SideSprite { get; set; } [XmlElement("SideSprite")] [EditorBrowsable(EditorBrowsableState.Never)] public Texture2DProcessor SideSpriteProcessor { get { return SideSprite; } set { SideSprite = value; } } </code></pre> <p>We have the same issue in my Noda Time project, as XML serialization doesn't mix well with immutable types. I've given pretty much the <a href="http://noda-time.googlecode.com/hg/docs/userguide/serialization.html" rel="nofollow">same advice</a> there.</p> <p>EDIT: Okay, so here's some sample code which <em>does</em> work:</p> <pre><code>using System; using System.IO; using System.Xml; using System.Xml.Schema; using System.Xml.Serialization; public class Person { public string Name { get; set; } } public class PersonWrapper : IXmlSerializable { public Person Person { get; set; } public static implicit operator Person(PersonWrapper wrapper) { return wrapper == null ? null : wrapper.Person; } public static implicit operator PersonWrapper(Person person) { return new PersonWrapper { Person = person }; } public XmlSchema GetSchema() { return null; } public void ReadXml(XmlReader reader) { string name = reader.ReadString(); reader.ReadEndElement(); Person = new Person { Name = name }; } public void WriteXml(XmlWriter writer) { writer.WriteString(Person.Name); } } public class Company { [XmlElement(typeof(PersonWrapper))] public Person Director { get; set; } [XmlElement(typeof(PersonWrapper))] public Person Manager { get; set; } } class Test { static void Main() { var serializer = new XmlSerializer(typeof(Company)); var original = new Company { Director = new Person { Name = "Holly" }, Manager = new Person { Name = "Jon" } }; var writer = new StringWriter(); serializer.Serialize(writer, original); Console.WriteLine("XML:"); Console.WriteLine(writer.ToString()); var reader = new StringReader(writer.ToString()); var deserialized = (Company) serializer.Deserialize(reader); Console.WriteLine("Deserialized:"); Console.WriteLine("Director: {0}", deserialized.Director.Name); Console.WriteLine("Manager: {0}", deserialized.Manager.Name); } } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POC# [XmlElement] attribute doesn't implicitly cast Type?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJon Skeet
    1. USJon Skeet
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POC# [XmlElement] attribute doesn't implicitly cast Type?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWow I didn't think about having a seperate property for my textureprocessor. Does this "[EditorBrowsable(EditorBrowsableState.Never)]" make it so where it won't show up in intelisence?
      singulars
      1. PO
      1. USDaniel Johnson
    2. CO@DanielJohnson: Yup. You *can* still refer to it from code, but hopefully people won't :)
      singulars
      1. PO
      1. USJon Skeet
    3. COIt would really be nice if i could just have one attribute to go on a variable to make it use the processor. It worked in this [link](http://stackoverflow.com/questions/20084/xml-serialization-and-inherited-types)
      singulars
      1. PO
      1. USDaniel Johnson
 

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