Well, for what its worth I completely agree with you about the
registry. I've always thought the Windows registry was a bad idea on
Microsoft's part, and never use it myself because I can serialize,
encrypt, and write the same data to a file on the hard drive thus
invalidating any need for a registry in the first place. Plus even
Microsoft recommends using the registry sparingly for the same reasons
you mention. So I personally choose to avoid it altogether.
As for using plane text ini or conf files you have a point, but I
still contend serialization is the best way to handle it for most
practical situations. Plus the .Net Framework has serialization
functions that will save serialized data to an xml file that can be
edited but has the ease of use of binary serialization. That to me is
really the best of both worldsas you have the ease of use of the
serialize and deserialize functions, but write the data to a plane
text xml file that can later be edited by hand.
On 11/20/11, Willem Venter <dwill...@gmail.com> wrote:
> Hi Thomas.
> While I hear what you say about ease of use of the built in functions
> of dot net for serializing and writing to the registry, sometimes
> reading a file gives valuable insight to a problem and altering
> something doesn't require a hex editor or custom loader for your file.
> In my opinion the registry has no functionality that you can't
> duplicate by using a file. Philip could even have emulated
> registry-like behavior by using a file. The larger the registry
> becomes, the longer it takes to find something in it.
Gamers mailing list __ Gamers@audyssey.org
If you want to leave the list, send E-mail to gamers-unsubscr...@audyssey.org.
You can make changes or update your subscription via the web, at
All messages are archived and can be searched and read at
If you have any questions or concerns regarding the management of the list,
please send E-mail to gamers-ow...@audyssey.org.