Topic: Looking for Active XML .NET forum (Page 1 of 1)

I'm looking for a forum which is dedicated to .NET and would offer an active group of developers who work with XML and XSLT transformation on this platform. I recently signed up for the forums at ASP.NEt; I have 2 complaints: 1) no activity on this topic (see below for my post) 2) they have this horrible rich text editor. It is a joke!!

My Post to ASP.NET (copied here + the link):
http://forums.asp.net/1108449/ShowPost.aspx

.NET XML XSLT Transformation
Lets just all agree, this aint an easy task, to transform XML in .NET that is.

After I figured out that the following 8 (8? Wholly crap!!!!!!!!!!!! 8 Objects!!!!!!) object would be required: the Evidence object, the XMLUrlResolver object, the PermissionSet object, the XMLSecureResolver object, the XPathNavigator object, the XsltArgumentList object, oh, and the XmlDocument and XslTransform objects (of course), and then managed to piece these together in some sort of a logical way (which was: 2 days effort, probably 30 web pages, 50 attempts of chosing the right overload combination, and multiple return trips to the MSDN to understand what about my code is "obosolete") I break through with success!!!! But Wait, what? What crucial step did i miss? What is this error I am receiving now? Oh, woops yah, when you query a database, you have to fill a dataset, then persist (but not like the good 'ole days) to a XmlDocument using the XMLDocuments LoadXML method and the DataSet's GetXml method. An what do you end up with? An XML document missing the oh so important ?xml version decleration at the top!

I probably screwed up though. I'm sure I probably didn't persist the XML correctly, probably needed a couple of more objects to accomplish this. I probably went about it entirely the wrong way! Am I starting to sound synical? Sorry. Could someone just tell me the easy way to do this? An what was wrong with the XML that classic ADO use to create, I liked it. For one thing, the overall structure was better, more scalable. Node elements named after the field names is a bad Idea; better to call them nodes "Fields" with name attribute. This is way more useful when performing XSL transformations.

Thanks for listening to my rant. I do look forward to a positive response from the group; I really do want to learn how to do XSL transformations the correct way in .NET.

Karl - Phoenix, AZ

PS. Is it just me, or is there just and awful latency when typing in this rich editor?