Problems saving values in the configuration file

Question

Hello,
I'm upgrading one of my projects from VS2005 (with .NET 2.0) to VS2013 (with .NET 4.5). I have a setup project in my solution, but this is no longer supported and I have to change to InstallShield
deployment project. With the old setup project my app runs fine, but now with InstallShield I have a problem. I install the application in this folder: C:\Program Files (x86)\CompanyName\AppName. I use .config file to read and write some parameters.
Reading parameters goes well, but when I write new values in the .config file a get one error. When I used the old setup project, at writing time the system created new .config file in C:\Users\me\AppData\Local\VirtualStore\Program Files (x86)\CompanyName\AppName
(this is named isolated storage, isn't it? :S).
These are all changes I made in the solution:
When I opened the solution with VS 2013 the migration process went well (some warnings and messages) except setup project (of course).
I upgrade all projects to .NET Framework 4.5 (Project properties -> Application -> Target framework).
I have intalled InstallShielld Limited Edition and added and configured the new deployment project.
I think that these are all changes. And this is the source code where I get the exception:
public void SetXParamValue(string value)
try
Configuration conf = ConfigurationManager.OpenExeConfiguration(Application.ExecutablePath);
conf.AppSettings.Settings["XParam"].Value = value;
conf.Save();
catch (Exception e)
MessageBox.Show("Error setting X param.");
And this is the exception:
Exception messsage:
An error occurred loading a configuration file: Access to the path 'C:\Program Files (x86)\CompanyName\AppName\oy25i1se.tmp' is denied. (C:\Program Files (x86)\CompanyName\AppName\ExeFile 1.0.192b.exe.config)
Stack trace:
at System.Configuration.MgmtConfigurationRecord.SaveAs(String filename, ConfigurationSaveMode saveMode, Boolean forceUpdateAll)
at System.Configuration.Configuration.SaveAsImpl(String filename, ConfigurationSaveMode saveMode, Boolean forceSaveAll)
at System.Configuration.Configuration.Save()
at VisualizadorCabecera.FormPrincipal.EstablecerIdioma(CultureInfo idioma)
Inner exception messsage:
Access to the path 'C:\Program Files (x86)\CompanyName\AppName\oy25i1se.tmp' is denied.
Stack trace:
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean
checkHost)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access)
at System.CodeDom.Compiler.TempFileCollection.EnsureTempNameCreated()
at System.CodeDom.Compiler.TempFileCollection.AddExtension(String fileExtension, Boolean keepFile)
at System.CodeDom.Compiler.TempFileCollection.AddExtension(String fileExtension)
at System.Configuration.Internal.WriteFileContext..ctor(String filename, String templateFilename)
at System.Configuration.Internal.InternalConfigHost.StaticOpenStreamForWrite(String streamName, String templateStreamName, Object& writeContext, Boolean assertPermissions)
at System.Configuration.Internal.InternalConfigHost.System.Configuration.Internal.IInternalConfigHost.OpenStreamForWrite(String streamName, String templateStreamName, Object& writeContext, Boolean assertPermissions)
at System.Configuration.Internal.InternalConfigHost.System.Configuration.Internal.IInternalConfigHost.OpenStreamForWrite(String streamName, String templateStreamName, Object& writeContext)
at System.Configuration.ClientConfigurationHost.OpenStreamForWrite(String streamName, String templateStreamName, Object& writeContext)
at System.Configuration.UpdateConfigHost.OpenStreamForWrite(String streamName, String templateStreamName, Object& writeContext)
at System.Configuration.MgmtConfigurationRecord.SaveAs(String filename, ConfigurationSaveMode saveMode, Boolean forceUpdateAll)
Any suggestions? I have to configure something else?
Thank you,
Jon.

Answer 1

> "With the old setup project my app runs fine"
Actually, I disagree.  Your configuration file is sitting alongside your application, in a directory that
should be protected from changes by "regular" users and it's
only running because Windows is intercepting your attempt to write under C:\Program Files* and rerouting those attempts to a "Virtual Store" location.  By the sounds of it, something your new installer is doing is [quite rightly]
stopping this from happening (IIRC, virtualisation can be turned off for a program and, IMHO,
should be).  
You need to move the configuration file to a location that the user can write to (somewhere under C:\Users\username), even if you have to copy it the very first time it's needed. 
Regards, Phill W.