D
Derrick
Thanks to many on this newsgroup, I now have a prototype Windows Forms C#
app that reads xml documents into DataSets via XmlDataDocument, and does
*stuff* with it.
I basically have about 25 megs worth of xml data that I read in and operate
on. Once loaded, before doing anything of substance with the data, my app's
memory footprint goes up to nearly 140 megs right off the bat.
Question is, if this is not an expected observation, what should I look at,
in general, to cut down the footprint closer to the size of loaded files?
Thanks in advance!
Derrick
app that reads xml documents into DataSets via XmlDataDocument, and does
*stuff* with it.
I basically have about 25 megs worth of xml data that I read in and operate
on. Once loaded, before doing anything of substance with the data, my app's
memory footprint goes up to nearly 140 megs right off the bat.
Question is, if this is not an expected observation, what should I look at,
in general, to cut down the footprint closer to the size of loaded files?
Thanks in advance!
Derrick