The short answer to the earlier post is, ‘Don’t use a MemoryStream object
with an XmlWriter.’ The expected results are received in my case when an
HttpContext.Response.OutputStream is used instead.

Signature
Bryan, Emperor of String.Empty
http://songhaysystem.com
> I have seen that empty rectangle before- seems like default behaviour
> -why I have no idea.
[quoted text clipped - 16 lines]
>
> Dickster
Amol Kher [MSFT] - 31 Mar 2006 09:21 GMT
I think the issue you are seeing is because you dont set the MemoryStream
back to its initial position before passing it into the Dom?
ms.Seek( 0, SeekOrigin.Begin );
> The short answer to the earlier post is, 'Don't use a MemoryStream object
> with an XmlWriter.' The expected results are received in my case when an
[quoted text clipped - 20 lines]
>>
>> Dickster