the changes to the XMLFileStorage SP required to add file-redirection (i.e. do not store settings within the app.config file), "rooting" of the final file path at one of the directories available through GetFolderPath from the Environment.SpecialFolder enum (e.g. ApplicationData), and default settings (i.e. copy a known settings file to the generated path) are pretty minimal (422 loc, most of which is by editor inheritance from the XMLFileStorage.cs file).

The benefit's been that paths like "C:\Documents and Settings\NonAdminUser\Application Data\Company\RootedXmlFileStorageTest\1.0.1.1\user.xml" aren't security restricted when dealing with user privilaged users who don't have permissions to write to paths like "C:\Program Files\Company\RootedXmlFileStorageTest\RootedXmlFileStorageTest.exe.config"

Sorry to kvetch, I liked the presentation, especially the app.config setup portion, it would've saved me at least a day of my life; but the ending segment suggesting key-valuing username to data for multiple user configs really felt like you punted, and it will bite devs as soon as they get handed to a brutal tester who actually doesn't run as root.

Good point. I tried to convey that it was a gross workaround to simulate per-user settings, but I probably shouldn't have shown it at all. I'll strike that demo from the next session.