Ben a =E9crit :

[quoted text, click to view]

XML is just a way to exchange data with another AppDomain.
What you could do is design a class to maintain your data and
XmlSerialize it when you want to exchange data.

Collection-type attributes are supported by XML serialization.


In pseudo-code you would design a class like this :
class MyData
{
protected Hashtable m_Items;

public MyData()
{
m_Items=3Dnew Hashtable();
}

public Items[] Items
{
get
{
fill Array from m_Items (maybe you can cache the result
for better performance)
}
set
{
fill m_Items from Array (maybe you can cache the result
for better performance)
}
}
}


Regards.

I have also a xml file, which I read in, and have to work with the data
in the program and don't change it. (til yet).

I decided to use Hashtables, with (string, XmlNode)

the key is : node.SingleNode(...).InnerText;
the value: node

So I can identify the node by a node specific string, and have access to
the XmlNode istself.

I first wanted ArrayLists, but I wasn't a good idea.
Another possibility to read in the data in Datasets, I dropped this too
(why should I create relational data..., my flexibility is then gone).


So taking Hashtables is a good idea. I didn't find a better idea yet.

Best Regards,
Istvan