Comments for Tom Goff's .Net Musings

Comment on SqlBulkCopy Bug by Joe

Joe — Thu, 24 Sep 2009 07:19:14 +0000

More frustrating if using schema. For example, [DataLoad.RAW].TableName fails. I have to replace the . with _

Too bad.

Comment on XML Serialization Sorrows by Valso

Valso — Wed, 26 Aug 2009 21:01:41 +0000

Brilliant!

Comment on XML Serialization Sorrows by Tom Goff

Tom Goff — Thu, 05 Mar 2009 16:32:56 +0000

Firefox is probably following the standard as defined by the World Wide Web Consortium (W3C). Just appears that Microsoft is being more flexible in allowing additional chars.

Comment on XML Serialization Sorrows by Dennis Gorelik

Dennis Gorelik — Wed, 04 Mar 2009 15:30:53 +0000

Tom,

Please consider InvalidChar.xml with invalid char:

When I try to open it in FireFox — I’m getting “XML Parsing Error: reference to invalid character number”.
FireFox is not developed by Microsoft, so I assume that FireFox 3.0.6 is enforcing commonly recognized XML standard in that case.
The ironic part is that I can open InvalidChar.xml in Internet Explorer 7.0 without errors.

What’s your take on this?
Why this chars are prohibited in XML?
How should I treat such characters if I need to serialize them into XML?

Comment on XML Serialization Sorrows by Tom Goff

Tom Goff — Wed, 04 Mar 2009 13:26:35 +0000

Hi Dennis, The issue has to do with the XmlTextReader.Normalization property. By default this property is set to false, which allows the encoded characters to be decoded (keep in mind that they encode just fine). When you don't explicitly create the XmlTextReader, one is created for you that has Normalization set to true. From the MSDN documentation on Normalization, there is a line that states that character range checking is not performed when Normalization is false.

If Normalization is set to false, this also disables character range checking for numeric entities. As a result, character entities, such as , are allowed.

Comment on XML Serialization Sorrows by Dennis Gorelik

Dennis Gorelik — Tue, 03 Mar 2009 18:23:36 +0000

Tom, thanks -- it helped me too. Did you find the reason why MS XML doesn't allow some characters to be encoded into XML?

Comment on Wanna Crash Visual Studio? by Smitty

Smitty — Fri, 13 Feb 2009 12:03:08 +0000

I have a much easier method

http://www.yankeeboysoftware.com/wordpress/?p=69

Comment on Custom Setup Action Woes by Utyxknly

Utyxknly — Sat, 13 Dec 2008 16:50:14 +0000

Thanks!,

Comment on XML Serialization Sorrows by Tom Goff

Tom Goff — Wed, 30 Jan 2008 13:16:27 +0000

Good to hear.

Comment on XML Serialization Sorrows by Stilgar

Stilgar — Tue, 29 Jan 2008 22:36:25 +0000

I just want you to know that your solution actually helped someone:)