http://blogs.msdn.com/ericwhite/archive/2009/01/28/manually-cloning-linq-to-xml-trees.aspx[Blog Map] (July 1, 2009 - Updated - OK to normalize empty elements to an element with a self-closing tag.) There are a variety of circumstances where you want to clone a LINQ to XML tree while making modifications to the cloned tree. It’s possible toenCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/ericwhite/archive/2009/01/28/manually-cloning-linq-to-xml-trees.aspx#9385573Sat, 31 Jan 2009 03:47:07 GMT91d46819-8472-40ad-a661-2c78acb4018c:9385573Pavel Minaev [MSFT]<p>I always wondered why the standard XLINQ API doesn't have some sort of visitor for creating a new tree from the old one. With that, and some creative use of predicates, I think we could actually get almost on par with XSLT for tree rewriting (I still prefer it to XLINQ because of the conciseness and clarity of XSLT transforms which only need to modify a few specific nodes out of many).</p> <p>By the way, I've posted here under the alias 'int19h' previously. Now it's new job, new email, and new blog account :)</p> http://blogs.msdn.com/ericwhite/archive/2009/01/28/manually-cloning-linq-to-xml-trees.aspx#9426268Mon, 16 Feb 2009 21:37:52 GMT91d46819-8472-40ad-a661-2c78acb4018c:9426268Microsoft XML Team's WebLog<p>In certain scenarios, it is important to be able to compare two XML trees for equivalence. For example,</p>