[I scratched part of this answer in response to the comment by DaBombNL. Still, Mehdi is recommended to ask questions more clearly; he could mention
XmlAttributeOverrides (is that it all about?) explicitly — SA]
Sorry, this is invalid question. The notion of "override" is only relevant to the virtual class methods or properties (more exactly, getters or setters of a property) and nothing else.
The attribute
System.Xml.Serialization.XmlIncludeAttribute can is applied to a class, structure, method or an interface, see
http://msdn.microsoft.com/en-us/library/system.xml.serialization.xmlincludeattribute.aspx[
^].
By the way, the
XmlIncludeAttribute class itself is not sealed, so you could create a derived class out of it, but why? The purpose of any attribute is to add some meta-data to the code; it basically plays the same role as type name or inheritance relationship, etc. The presence/absence and properties of the attribute and its properties simply serve as a reference for some code (serialization code in this case); basically, the code detects the presence of some attributes, reads their properties and "decides" how to proceed based on this meta-data.
If I dare to suspect that you're not well familiar with the override concept, I would suggest you should set aside all your serialization and learn it right away, as this is a hart of OOP; you could not do any real programming without.
I hope, this is not that bad: you could simply misuse the terminology.
In this case, you need to explain your base idea (not how to "override" but what you want to achieve).
—SA
Submit an article or tip