Assembly: System.Xaml (in System.Xaml.dll)
Initializes a new instance of theclass from a stream.
|XamlXmlWriter(Stream, XamlSchemaContext, XamlXmlWriterSettings)|
Initializes a new instance of theclass from a stream using a writer settings object.
Initializes a new instance of the TextWriter basis.class from a
|XamlXmlWriter(TextWriter, XamlSchemaContext, XamlXmlWriterSettings)|
Initializes a new instance of the TextWriter basis using a settings object.class from a
Initializes a new instance of the XmlWriter basis.class from a
|XamlXmlWriter(XmlWriter, XamlSchemaContext, XamlXmlWriterSettings)|
Initializes a new instance of the XmlWriter basis using a settings object.class from a
Closes the XAML writer object.(Inherited from XamlWriter.)
Releases the unmanaged resources used by XamlWriter.Dispose(Boolean).)and optionally releases the managed resources. (Overrides
Determines whether the specified object is equal to the current object.(Inherited from Object.)
Allows an object to try to free resources and perform other cleanup operations before it is reclaimed by garbage collection.(Inherited from Object.)
Serves as the default hash function. (Inherited from Object.)
Returns a string that represents the current object.(Inherited from Object.)
Writes an object for cases where the specified object is a default or implicit value of the property that is being written, instead of being specified as an object value in the input XAML node set.(Overrides XamlWriter.WriteGetObject().)
Writes namespace information to the underlying XmlWriter or TextWriter. May throw an exception for certain states; however, may instead defer writing the namespace information until the writer and the XAML node stream that is being processed reaches a position where a XAML namespace declaration can be inserted.(Overrides XamlWriter.WriteNamespace(NamespaceDeclaration).)
Writes a XAML start member node to the underlying XmlWriter or TextWriter. Throws an exception if the current position of the XAML node stream is within another member, or if it is not in a scope or writer state where a start member can be written.(Overrides XamlWriter.WriteStartMember(XamlMember).)
Writes a XAML start object node to the underlying XmlWriter or TextWriter. Throws an exception if the current position of the XAML node stream is not in a scope where a start object can be written, or if the writer is not in a state that can write a start object.(Overrides XamlWriter.WriteStartObject(XamlType).)
This class is typically used in serialization scenarios.
The XamlWriter API has several methods that write different types of XAML nodes. Collectively, these are referred to in documentation as the Write methods of a XamlWriter. uses several internal state classes to determine what to do when one of its Write implementations is called. A Write call uses the states to determine whether the requested element, attribute, or value can be written, or whether an exception is thrown. For example, if you call WriteEndObject and the state of the current node position is on a value or within a member, an exception is thrown. Typically, callers of the API should be aware of the type of the current XAML node that is coming from the XAML reader and the XAML node stream. Based on this knowledge, callers should avoid calling Write APIs that are not relevant to the current node type.
The XAML namespace writing behavior of WriteNamespace. Instead, other Write calls, such as WriteStartObject, might require that the namespace declaration be written at particular points in the node structure. The XAML writer either generates a prefix by its own logic, or uses information from the INamespacePrefixLookup service to determine a preferred prefix. Also, explicit WriteNamespace calls might defer or might return nothing if the XAML namespace declaration is already applicable and declared elsewhere.is complex and is not limited to explicit calls to
An InvalidOperationException often indicates that a XAML reader passed an invalid node structure into the XAML node stream. In this case the node structure is invalid for reasons that are not related to validation of a XAML schema or a XAML schema context. Rather, the node stream is invalid in its basic form. For example, if a faulty XAML reader implementation generated a XAML node stream that contained two consecutive StartObject nodes, the attempt to call the second WriteStartObject would throw an InvalidOperationException. All XAML writers would consider such an operation to be invalid. Another example of an InvalidOperationException is when XAML namespace information is unavailable through the XAML schema context that applies to the current node stream position.
A XamlXmlWriterException indicates an exception where this particular XAML writer implementation chooses to throw an exception based on its intended functionality. A XamlXmlWriterException can indicate specific cases where a violates its own state or settings. For example, a XamlXmlWriterException might result from attempts to write XAML namespace information into a position that the and its serialization format do not support, or writing duplicate members when the instance's XamlXmlWriterSettings forbid it.
Available since 4.0
Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.