Re: Saving a configuration. Ideas needed.
"Paco" <paco_beams@gmail.com> wrote in message
news:dcPei.5691$bP5.4652@newssvr19.news.prodigy.net...
I've written a program that requires an extensive configuration setup. Its
more complex ( a bunch of choices) then it is lengthy. The operator must
create what is called a "Formatting Plan". The configuration will be setup
by the tech that sets up the hardware. The customer may rarely change it.
There will be groups of customers that can use the same configuration or
tweaked versions.
I want there to be a way for the tech to be able to save a configuration
to a file which he can take with him on his memory stick. The tech might
want to use it at a different customer in the future.
How should I do this. The data is stored in the registry, so I looked at
using a .reg files. I looked at using the private .ini functions. To
upload a reg file there is some programming permission stuff. The .ini
file function help pages talk about compatibility issues. I haven't read
everything on that topic yet.
Question: How should I save the data? What format? Registry, .ini or what.
Any ideas?
If your program that uses the configuration data reads it from the registry,
and there is no changing that, then I would avoid converting the data to XML
or .INI just for the purpose of transporting it. This requires reading the
registry data, saving to XML/INI, then reading the saved XML/INI and writing
the registry data on the new computer. Way too much work. The only way to
make this efficient is to change your program to read the configuration data
from XML/INI directly and avoid the registry (which wouldn't be a bad idea
either, since the data is natively portable at that point).
But anyway, if you're not willing to do that, I recommend you use
RegSaveKeyEx() to write a .reg file. Copy the .reg file to your memory key.
Then on the new computer, just double-click the .reg file (or else write a
program that uses RegLoadKey()) to import the .reg file into the registry.
-- David