XML Parsing Error: junk after document element

Hi.

I have an event handler in VB.NET that gets called several times.
The output of the event handler is XML that is being called by
an xmlhttp request from the client.

I am using a stringbuilder to create the XML document by
appending the various parts:

sbhtml.Append("<Some XML Tag>")

The problem is that the XML document gets recreated every
time the event handler fires and I get the junk error after the
first document's parent tag is closed:

XML Parsing Error: junk after document element

Location: http://localhost:5223/PresentationTi..._progress.aspx
Line Number 1, Column 191:<?xml version='1.0' encoding='ISO-8859-1'?bytessent><filesize>12444894</filesize><percent>0</percent></upload></
uploads><?xml version='1.0' encoding='ISO-8859-1'?...

SO: How do I prevent this? How Do I "UPDATE" the XML document every
time the event handler fires and not "APPPEND" a new document to the
recently created one?

Thanks.
Peter

re: XML Parsing Error: junk after document element

XML Parsing Error: junk after document element

An XML document must have one, and only one, top level element. You
can't append to it; you have to actually read the document in and
process it properly, inserting the new structure in a place that makes
sense syntactically.

Or -- a sloppy workaround, but sometimes useful -- don't append to your
top-level document, but to an External Parsed Entity which is referenced
by your document. External entities *can* be document fragments and have
multiple top-level elements, if they're referenced in an appropriate place.

--
() ASCII Ribbon Campaign | Joe Kesselman
/\ Stamp out HTML e-mail! | System architexture and kinetic poetry

re: XML Parsing Error: junk after document element

On Mar 12, 4:54 pm, Joe Kesselman <keshlam-nos...@comcast.netwrote:
Thanks for the response Joe.
After rereading my post, I am realizing this isn't an XML issue.
I understand that my document isn't well-formed, I guess I am
trying to figure out how to prevent the event handler from recreating
the XML and hence, causing the "junk" error. I think this is a
VB.NET issue. I'll repost. Thanks...