Christian Froeschlin <chr### [at] chrfrde> wrote:
> This is actually a form of installer functionality. The part of
> the installer that creates per-user files could be "advertised" so
> it runs when the user first attempts to start the application.
Huh. I learn something new everyday. :)
> According to this thread,
> that was at least intended to be in the final release.
(Interestingly, I couldn't see the link until I replied.) There is another,
more elegant, (though likely complex to implement) solution too... use a sort of
settings "layering". Have the default settings in .INIs under the install
(Program Files) directory, and if the user has any .INIs with settings in their
profile (in an installer-created folder structure), allow them to override. An
additional layer could be put in place to have enforced settings that
won't/can't be overridden. This would allow administrators to force some
settings, set others to default and give users the ability to set their own.
Apps like PowerShell and Privoxy do this.
> Note that Vista or higher seems to support symbolic
> links, so it might be possible to avoid the copying into user
> profiles and redirect to a shared location.
NTFS junctions may be a good solution. I'll have to read up and do some
Post a reply to this message