Hi
It is XmlFormatter the serializer associated to the [DataContract] attributes
Which are the main differences between XmlFormatter and Xmlseriilizer Why another xml serializer
Thanks in advance
Javier
Thinking in the serialization
Hot Topic
- Replacing the +/- in a TreeView
- How to determine which part of a FlowDocument is visible in a FlowDocumentReader?
- Best way to implement this interface?
- Simulate Keyboard Message
- Directions/Sys Reqs/Pre Reqs needed: VS2005 beta 1 going to VS2005 beta 2
- Serious Error while deleting the row
- Frame Navigation
- What is orthodox way of creating a 1:m report
- .Net 2.0 SDK install problems?
- XamlReader and {StaticResource }
Visual Studio
- disabling the visual studio hosting process..
- Programming Outlook
- C# with Excel -- How to select a sheet?
- ServerDocument VSTO2 question
- Export / Save Workbook without Customization
- Deployment error with CR XI R2 on Windows Server
- Purpose of debug and release configurations
- CMDUSED_SECTION and shared commands
- Installing Visual Basic 2005 Express
- Enum?
Thinking in the serialization
Norbert Mika
//we have different design goals for XmlFormatter,I hope following info will help
The XmlFormatter is the next generation, unified serialization engine that merges much of the functionality found in the current serialization offerings (BinaryFormatter, SoapFormatter, and XmlSerializer). An instance of the XmlFormatter is capable of serializing and deserializing an instance of any CLR type that is marked with the Serializable ([Serializable]) or DataContract attributes ([DataContract]) to/from an arbitrary XML format.
The attributes stem from the System.Runtime.Serialization namespace that is the home of the new XmlFormatter infrastructure. The XmlFormatter is similar to the well-known XmlSerializer (as well as the Binary Formatter and SoapFormatter)
http://www.douglasp.com/blog/PermaLink.aspx guid=bff35b26-4739-4971-9a05-507e5aaddd7a
http://weblogs.asp.net/cschittko/archive/2003/10/29/34414.aspx
-Thank you
Madhu
mrayyan
The new serializer is called DataContractSerializer now (no longer XmlFormatter).
One of the primary motivations for DCS was to provide a constrained mapping to XSD that will improve interop in code-first design scenarios.
As a result, there are some pretty significant differences between DCS and XmlSerializer. I just shipped an article that covers these differences in detail but it won't hit MSDN Mag for about another month or so. I'll post it on my blog once it's available.