0

I am busy working on a piece of software which stores a .config file within the installation folder (C:/Program Files/...). This config file needs to be updated when the software is used which currently works fine when the user has Admin rights, however when a non-admin user attempts to use the software exceptions occur since they don't have permission to update files within C:/Program Files/.

The code used to update the config file is as follows:

Configuration config = ConfigurationManager.OpenExeConfiguration(fileName);
config.AppSettings.Settings.Add("New Setting");
config.Save();

Is there anyway to allow a non-admin user to update this config file? Maybe by changing something in the actual config file or changing the way in which I update it?

Ideally I would move the file to the App Data folder but this could be a fair bit of work so I would prefer to avoid having to do this.

Any help would be greatly appreciated.

Thanks in advance

dante671
  • 117
  • 1
  • 10
  • Use Visual Studio project Settings with User scope: http://stackoverflow.com/questions/453161/best-practice-to-save-application-settings-in-a-windows-application – 79E09796 May 10 '12 at 09:50

1 Answers1

1

Your installer (or even the app, when it detects it's run as an admin) could set the ACLs on the configuration file to allow normal users to read and write that particular file.

However the right way to do this - as you said yourself - is to use the application data folder.

AKX
  • 152,115
  • 15
  • 115
  • 172
  • +1 for 'do it properly now'. 'common' config data can go in 'Public'. I usually create a subfolder there with the app name and, underneath, a different subfolder for each version num. – Martin James May 07 '12 at 10:43
  • Thanks for the replies, think I will be moving the file to App Data providing I'm allowed enough time to get it done. – dante671 May 07 '12 at 13:17