关于XmlWriter生成XML时属性顺序的技术咨询（附代码）

Let's break down everything you need to know about attribute order when working with XmlWriter in .NET, especially given the code snippet you shared.

First: The XML Specification Perspective #

W3C's XML Recommendation explicitly states that the order of attributes in an element has no semantic meaning. All XML processors are required to treat attributes as unordered collections, so from a standards-compliant standpoint, you shouldn't rely on or worry about attribute order for functional purposes.

How XmlWriter Handles Attribute Order #

By default, XmlWriter doesn't strictly follow the order of your WriteAttributeString calls—especially when dealing with namespace-related attributes (like your xmlns:rd). Here's what happens:

• Namespace attributes are prioritized: XmlWriter automatically moves all namespace declarations (attributes starting with xmlns: or the default xmlns attribute) to the front of the attribute list, regardless of when you call WriteAttributeString.
• For non-namespace attributes, it generally follows the order of your calls, but this isn't guaranteed in all edge cases (like if you're mixing default namespaces and prefixes).

Looking at your code (completed for clarity):

XmlWriterSettings settings = new XmlWriterSettings();
settings.Indent = true;
settings.IndentChars = "\t";
XmlWriter writer = XmlWriter.Create("sample.xml", settings);
writer.WriteStartDocument();
writer.WriteStartElement("Report", "http://schemas.microsoft.com/sqlserver/reporting/2008/01/reportdefinition");
writer.WriteAttributeString("xmlns","rd", null, "http://schemas.microsoft.com/SQLServer/reporting/reportdesigner");
writer.WriteEndElement();
writer.WriteEndDocument();
writer.Close();

The output will likely have the default xmlns attribute first, followed by xmlns:rd, even though you called WriteAttributeString for xmlns:rd after defining the element's default namespace. That's XmlWriter's default behavior to group namespace declarations together.

If You Must Enforce a Specific Attribute Order #

While this goes against XML's intended design, if your use case requires strict attribute ordering (e.g., for legacy systems that incorrectly rely on order), you have two main options:

1. Use XmlDocument Instead #

XmlDocument preserves the exact order in which you add attributes to an element. Here's how you could rewrite your code with it:

XmlDocument doc = new XmlDocument();
XmlElement reportElement = doc.CreateElement("Report", "http://schemas.microsoft.com/sqlserver/reporting/2008/01/reportdefinition");
// Add attributes in your desired order
XmlAttribute rdNsAttr = doc.CreateAttribute("xmlns", "rd", "http://www.w3.org/2000/xmlns/");
rdNsAttr.Value = "http://schemas.microsoft.com/SQLServer/reporting/reportdesigner";
reportElement.Attributes.Append(rdNsAttr);
doc.AppendChild(reportElement);

XmlWriterSettings settings = new XmlWriterSettings();
settings.Indent = true;
settings.IndentChars = "\t";
using (XmlWriter writer = XmlWriter.Create("sample.xml", settings))
{
    doc.Save(writer);
}

2. Implement a Custom XmlWriter #

You can create a wrapper around the default XmlWriter that overrides attribute writing to preserve order. This is more complex, but useful if you need to stick with XmlWriter for performance reasons.

Key Takeaway #

Unless you're dealing with a non-compliant legacy system, don't waste time worrying about attribute order. XML is designed to be order-agnostic for attributes, and relying on order can lead to fragile code.

内容的提问来源于stack exchange，提问作者Chanchan