It is fixed, sort of. At least we now pretty much know what we need to do. Basically...
1) The installer needs to be run from an admin account and install for all users, making sure that permissions are set for all users on any files/folders it creates. Usually, a little check-box that says "install for all users" is all that needs to be done, or a switch if it's a scripted installer. May vary slightly depending on the installer being used.
2) Any files/folders that are created by the program should have their permissions set to all users by using SetFileMode <file>,%110110110 after they have been written.
3) Although I've found this not to be necessary, the correct place to store your app's data is the ProgramData folder (which is hidden). User specific data can be stored in the user's own folder. There are API calls to retrieve the location of these folders (as discussed above and in the Win32 forum).
I've found that as long as the permissions are set up correctly, you can still store data in the program's own folder. This isn't the 'correct' way of doing things, according to MS, but everyone's been doing it for years and it was never the correct way! Probbably should do it right, and I may well change to do it this way at a later stage.
1) The installer needs to be run from an admin account and install for all users, making sure that permissions are set for all users on any files/folders it creates. Usually, a little check-box that says "install for all users" is all that needs to be done, or a switch if it's a scripted installer. May vary slightly depending on the installer being used.
2) Any files/folders that are created by the program should have their permissions set to all users by using SetFileMode <file>,%110110110 after they have been written.
3) Although I've found this not to be necessary, the correct place to store your app's data is the ProgramData folder (which is hidden). User specific data can be stored in the user's own folder. There are API calls to retrieve the location of these folders (as discussed above and in the Win32 forum).
I've found that as long as the permissions are set up correctly, you can still store data in the program's own folder. This isn't the 'correct' way of doing things, according to MS, but everyone's been doing it for years and it was never the correct way! Probbably should do it right, and I may well change to do it this way at a later stage.