This is more a DESIGN question than a technical question!
Well, okay. Something new I have to work on. I have an application which has a lot of features. These features are set in the Registry and I happen to have several hundreds of them. Or not, in which case a default value for some setting is going to be used...
Limitation: I am NOT allowed to modify the storage of these features. I can't even modify the application which uses them.
Well, not I need to find a solution for the following... I will have two *.reg files (maybe more in the future) for two different scenarios. And I have to write an application which allowds the user to select one of these files and then installs the REG file. However, the user should be able to FLIP the settings too so when the user executes the application again then it should remove the settings from the old registry file and install the new registry file.
One nasty issue is that I just can't delete the whole registry tree of this application. There might be other keys in there which need to stay untouched. So basically, it's not as easy as it might appear at first glance.
Right now, I have two registry files to use as example and pen and paper (well, Word and Paint) to use for the DESIGN of this application. And no, I don't need any deep technical advise. I just want some good suggestions about where to start the design. What would be the best approach for this?
Right now, what I considered was just reading the REG file, parse the contents and walk through every key in it, keeping a log of keys so I can always remove them again. And I have about a week to think about this design before I have to start designing it so I have some time to discuss the design with fellow experts. :-)
So, any input?