I have about 10K of data that varies User to User.
I had not even considered "where" the file would go. So I really
the advice regarding the location.
Portability is not a concern to me. Performance is not really an issue.
I have written some code to serialize the various parameters I need.
I was just concerned about dumping 10K of information into the Registry.
It seems that I would somehow be polluting the registry with junk.
On the other hand, I do not know what a best practice is here.
"Joseph M. Newcomer" wrote:
How large is "a bit large"? Generally these descriptions have no
meaning. If you say "I
have about 128K of data to store" then I would agree that it seems
large. But you might
mean "300 bytes of data" or "3000 bytes of data", in which case it is
much harder to
justify using files.
Files have several advantages, such as they are editable, they can be
sent to others, etc.
In that case, you would probably want to store them in the user's
AppData folder (you have
not specified where you would keep the .INI file. It would *not* be
kept int the
executable directory, which would represent Worst Possible Practice in
interpretations of good practice).
On the other hand, it is hard to store structured data effectively in a
.INI file; for
example, try storing anything that is other than a simple variable.
Lots of luck. But
you can keep your own data in a .XML file, which can handle structured
On Wed, 17 Sep 2008 06:18:01 -0700, Cameron_C
Could someone offer me an opinion on whether or not storing
specific information in an INI file rather that the registry could be
considered an "approved" technique.
Everything I have read suggests that information should be stored in
In my case I have a bunch of User customizable reports, and I save the
customization qualifiers in an ININ file, rather than the registry,
volume of information seems a bit large (IMHO) to keep in the
I am just fishing for some advice here.
Joseph M. Newcomer [MVP]
MVP Tips: http://www.flounder.com/mvp_tips.htm