Probably deserves its own thread, but I had a constructuve comment regarding the config file issue and the autoupdater etc, and the original thread is now locked
I used to program for
Apple Macintosh MacOS systems a few years back (before I switched to PC, and ditched programming altogether for some other more lucrative business). When I stored the app's user 'Preferences' (the 'settings'), I stored them in a flat file in text format. It had very little structure, I did not use XML, and INI files as we know them on the PC where non-existent. I encountered the same issue you have where upgrades would require added/removed/altered settings on the saved preferences file.
My updaters/patches managed that seamlessly to the user: It would scan through the preference file, determine what needed to be changed, and did it all behind the scenes, preserving my user's settings.
Now with CF, you are
golden. Your settings are in a well structured format (XML), so you are already one step ahead in terms of having the ability to easily scan through the file, alter your user's settings, and adapt them to be compatible with new upgraded versions.
Now I know this is not totally trivial, and it will require effort on your part to code this, sometimes on a case-by-case basis for each upgrade. You might be thinking this is time better spent in other areas of CF, new features etc... but keep in mind that this
will come back and bite you in the cheeks (where the sun don't shine!). You see, even after your final release, you
will find that you need to add a setting here or there, and you really cannot expect your users to loose all their settings just to upgrade to a new point version/revision of CF. Those users will have paid, and thery are no longer in Beta mode, so they will be very upset.
In summary: CF is a fantastic app. Don't let this irritating upgrade issue take away from it. Thanks.
Bookmarks