Net 2.0 XmlWriter Create and Attributes

[jschell]

The following two cases behave differently in Net 2.0. The
Case_Create_Str ingWriter throws an exception while the Case_XmlTextWri ter
does not.

Is there a problem with this code?
Or is this a known problem?

--------------------------------------------------------------------------
using System;
using System.Xml;
using System.Text;

namespace TestXmlNil2005
{
class Program
{
static void Main(string[] args)
{
Case_XmlTextWri ter();
Case_Create_Str ingWriter();
}

static void Case_Create_Str ingWriter()
{
try
{
System.IO.Strin gWriter sw = new System.IO.Strin gWriter();

XmlWriter xw = XmlWriter.Creat e(sw);

WriteXml(xw);

System.Console. WriteLine("xml Create-StringWriter=" + sw.ToString());
}
catch (Exception e)
{
System.Console. WriteLine("xml Create-StringWriter=ex ception = " +
e.Message);
}
}

static void Case_XmlTextWri ter()
{
System.IO.Strin gWriter sw = new System.IO.Strin gWriter();
XmlTextWriter xw = new XmlTextWriter(s w);

WriteXml(xw);

System.Console. WriteLine("xml XmlTextWriter=" + sw.ToString());
}

static void WriteXml(XmlWri ter xw)
{
xw.WriteStartEl ement("document ");

xw.WriteAttribu teString("xsi:n il", "true");

xw.WriteEndElem ent();
xw.Flush();
xw.Close();
}

}
}

[Derrick Coetzee [MSFT]]

jschell wrote:

The Case_Create_Str ingWriter throws an exception [...]

static void Case_Create_Str ingWriter() {
System.IO.Strin gWriter sw = new System.IO.Strin gWriter();
XmlWriter xw = XmlWriter.Creat e(sw);
WriteXml(xw);
}

static void WriteXml(XmlWri ter xw) {
xw.WriteStartEl ement("document ");
xw.WriteAttribu teString("xsi:n il", "true");
xw.WriteEndElem ent();
xw.Flush();
xw.Close();
}

The problem is that you can't specify a namespace using the ns:name syntax
directly in this way. Instead, use an overload of WriteAttributeS tring()
which explicitly takes both a namespace and name:

xw.WriteAttribu teString("xsi", "nil","http ://uri.of.xsi.name space/","true");

The reason that your original code mysteriously works for XmlTextWriter but
not XmlWriter is that XmlWriter sets the CheckCharacters attribute of its
XmlWriterSettin gs instance to true by default, which causes it to check for
invalid characters that XmlTextWriter does not have the ability to check
for. You can read more here:

http://msdn2.microsoft.com/en-us/library/kkz7cs0d.aspx

I hope this helps.
--
Derrick Coetzee, MCAD, MSFT (Speech Server)
This posting is provided "AS IS" with no warranties, and confers no
rights. Use of included code samples are subject to the terms
specified at http://www.microsoft.com/info/cpyright.htm