Yogi_Bear_79,
There shouldn't be a problem with it, if you are finding it works, then
keep it. The only thing that you have to worry about with an array is the
backing store. For example, if you were using a file, or a DB, then you
don't have to worry about state being lost if your program crashes.
However, if your code crashes, then the array isn't backed by memory
anymore, and you lose what is in it.
Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
-
mv*@spam.guard.caspershouse.com
"Yogi_Bear_79" <IT*****@spamfree.com> wrote in message
news:0d********************@comcast.com...
I wrote a program that helps me manage my Internet Explorer Security.
Currently I have an arrary that has more than 10,000 value.
The code works fine, and speed doesn't seem to be an issue. I chose an
array, so that I could keep everything in one .exe versus, an exe calling
other files for data. Is there anything wrong with this approach?