XAML has up to now played a big role in WPF and Silverlight and is seen as a markup language to design GUIs. That is not quite true. XAML describes objects, their properties and their relations. It is not limited to designing user interfaces. That is why XAML has been separated from WPF and Silverlight in .NET framework 4.0.
Let's assume you have a class
BigSerializableObject and want to save it to a file with all properties and attached objects. Later, you want to be able to load it again from the file and get a new instance which is a perfect copy of the object you originally serialized. You might do this with XML. Serializing is not much of a problem. Deserializing is a completely different story. You would have to navigate through the XML nodes, create instances of the required objects, fill them with the proper values and assemble them according to the structure of the XML. That also means writing lots of code.
Things get far easier when using the
System.Xaml.XamlServices class. Serializing the object is very similar to what you might be used to from XML:
using (TextWriter XamlWriter = File.CreateText("Test.xaml"))
{
System.Xaml.XamlServices.Save(XamlWriter , MyBigSerializableObject);
}
That's it. Your object has just been serialized to XAML into the file
Test.xaml. The only condition is that your object and all objects attached to it must be serializable.
Now we want to load our object again from the file
Test.xaml. If possible, we want it as an object instance, just like it was before. And we don't want to write any code which constructs the object from the file. Try this:
using (TextReader XamlReader = File.OpenText("Test.xaml"))
{
BigSerializableObject MyNewBigSerializableObject = (BigSerializableObject)System.Xaml.XamlServices.Load(XamlReader);
}
Again, that was it. You now have a new instance of your original object, loaded from the file.
