Yup, I'm finding LINQ is looking real good and there's no reason I shouldn't 
or couldn't use 3.5.

Did you know Firefox will not display raw XML (the entire collection of 
nodes) in the same way IE will and does? I can't stand the thought of 
publishing files for the public with <!--comments--> warning users not to 
copy and paste without using view source to see the entire collection of 
elements which is then not formatted; the other choice being a comment 
warning to use the File menu to save the file and then the user wondering 
why without being told why? It infers something wrong with my app unless I 
name Firefox. Have you run across this when attempting to use Javascript 
window.open to display raw XML in a new window?

"Martin Honnen" <mahotrash@y...> wrote in message 
news:Ovv5IeKSJHA.4524@T......
> Hillbilly wrote:
>> There's one primary collection of a parent node which has several child 
>> nodes (channel). There's another collection having a different parent 
>> which has several child nodes of its own (item); there are x number of 
>> items. Both channel and items have to be assembled into an XML document.
>>
>> What strategy is currently easiest to learn to actually produce results 
>> when getting the data out of a form, ADO or LINQ?
>
> Well as you mention LINQ you seem to use or target .NET 3.5 and in that 
> case using LINQ to XML is certainly a good idea.
>
> -- 
>
> Martin Honnen --- MVP XML
> http://JavaScript.FAQTs.com/