Hello Friedrich and all others,
over the weekend I am playing with Windows 8 Preview 8400 a bit.
We install the binary files (all EXE/DLL/OCX code-signed and EXE manifested) of
our programs by default under "C:\Program Files\Our Folder",
the data go by default to "C:\Users\Public\Documents\Our Folder\Data".
If I am not completely wrong, we compile the installer with SB 7.5.3378.
That works fine so far.
We use some INI-files which gets stored in "C:\Program Files\Our
Folder\Settings" - which is a violation of the rules MS set up years ago, I
know.
During the install we set the R/W access-privileges to All Users, so that
settings can be modified from within our Admin.EXE, no matter if called from an
Admin or User account. That might be considered dirty..... it worked all years
- and now we get bitten ;-)
All files in that Settings folder are not editable. I can set the privileges
manually, thenit works again, but have to modify each file separately. Altering
the folder and therefore all subsequent files inside in one rush does not
work.
Do you have another, ever more dirty trick to overcome that lack? <eg>
The reason why we store the INI in a Settings folder just beyond the EXE-folder
is, that now an andmin can move the entire folder somewhere else, without
loosing anything. Often they also place the data folder below that EXE folder.
They are happy with this.
Plan B would be to check at program start, if INI exist. If not, store them in
%CSIDL_APP_DATA% or where ever and fill them with the necessary default values,
then let the Admin do set the values again.
Or you may come up with a complete different suggestion......
Thanks for reading,
Wolfgang