> > Once loaded into a .net string, it is Unicode. [cut] > That's the rub, but it's so obvious you can forget it. The "problem" exists in the reverse direction because you will see countless people in web searches asking "why is my saved XML coming out as UTF-16?". It turns out they're using a StringWriter or similar.
> Either way, the moral is to avoid loading Xml from System.Strings. I know you most often get X-DOM objects out of files or streams, but sometimes you have to make them from strings. I'm getting raw xml strings back from a native DLL. Although my BOM crash was caused by me doing something wrong inside a faulty WEB API media formatter (which I decided I didn't need anyway). Greg K
