http://weblogs.asp.net/vlindesay/archive/2003/09/15/27622.aspxFor the first time since 1997 and the first Microsoft XML toolkit / parser, I have had to hack into XML files using regular expressions (arrrrrg!) in order to get a valid XML document to load into Microsoft XML tools. An example of this type of XML isenCommunityServer 2007 SP1 (Build: 20510.895)http://weblogs.asp.net/vlindesay/archive/2003/09/15/27622.aspx#5338047Sun, 25 Nov 2007 23:59:12 GMTc06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:5338047Feed Search Engine - All Fresh Articles And News Are HereFeed Search Engine - All Fresh Articles And News Are Here<p>Pingback from &nbsp;Feed Search Engine - All Fresh Articles And News Are Here</p> <img src="http://weblogs.asp.net/aggbug.aspx?PostID=5338047" width="1" height="1">http://weblogs.asp.net/vlindesay/archive/2003/09/15/27622.aspx#27625Mon, 15 Sep 2003 17:31:00 GMTc06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:27625kpako@yahoo.com (Dare Obasanjo)kpako@yahoo.com (Dare Obasanjo)The easiest way is to post in one of our newsgroups such as microsoft.public.xml or microsoft.public.dotnet.xml. This particular bug is a known issue and will be fixed in the Whidbey release. <img src="http://weblogs.asp.net/aggbug.aspx?PostID=27625" width="1" height="1">