App.Config File.

When working with the app.config file in a .NET application, it's important to understand how the configuration system works. The app.config file is used as a template to generate an XML configuration file during the build process. This XML file is then used at runtime to provide configuration settings to the application.

The reason why changes made to the app.config file at runtime are not reflected in the XML app.config file is because the XML file is only read once, during the application startup. Any modifications made to the app.config file during runtime will not be automatically written back to the XML file.

To ensure that changes made to the app.config file are reflected in the XML app.config file, you can use the ConfigurationManager class provided by the .NET framework. This class provides methods to read and write configuration settings at runtime.

Here's an example of how you can update a configuration setting and save it back to the XML app.config file:

// Get the configuration file path
string configFilePath = ConfigurationManager.OpenExeConfiguration(ConfigurationUserLevel.None).FilePath;

// Open the configuration file
Configuration config = ConfigurationManager.OpenExeConfiguration(configFilePath);

// Update the configuration setting
config.AppSettings.Settings["SettingKey"].Value = "NewValue";

// Save the changes back to the XML app.config file
config.Save(ConfigurationSaveMode.Modified);

// Refresh the configuration
ConfigurationManager.RefreshSection("appSettings");

By using the ConfigurationManager class and saving the changes back to the XML app.config file, you can ensure that modifications made at runtime are persisted and reflected in the XML file.

The behavior you’re observing is expected. When you change values in the app.config file at runtime, they are not reflected in the YourApplicationName.exe.config file. This is because the app.config file is designed to store configuration values that are not supposed to change during runtime .

When you compile your application, the app.config file is copied and renamed to YourApplicationName.exe.config in the output directory . Therefore, if you want your changes to be taken into account, you should modify the YourApplicationName.exe.config file, not the app.config file  .

If you need to change configuration values dynamically, you might want to use a different storage mechanism like a file or a database . If you still want to use the app.config file, you can use the ConfigurationManager.RefreshSection("appSettings") method after modifying the YourApplicationName.exe.config file. Then, refetch the value you need using ConfigurationManager.AppSettings["someKey"], which should return the new value.

ConfigurationManager.RefreshSection("appSettings");
string value = ConfigurationManager.AppSettings["someKey"];

Any changes made to the app.config file at runtime will not persist after the application is closed . If you need to save these changes permanently, consider writing them to a separate user-specific configuration file or another form of persistent storage.

Make Copy always true in the property of config file

The behavior you’re observing is expected. When you change values in the app.config file at runtime, they are not reflected in the YourApplicationName.exe.config file. This is because the app.config file is designed to store configuration values that are not supposed to change during runtime123.

When you compile your application, the app.config file is copied and renamed to YourApplicationName.exe.config in the output directory12. Therefore, if you want your changes to be taken into account, you should modify the YourApplicationName.exe.config file, not the app.config file12.

If you need to change configuration values dynamically, you might want to use a different storage mechanism like a file or a database2. However, if you still want to use the app.config file, you can use the ConfigurationManager.RefreshSection("appSettings") method after modifying the YourApplicationName.exe.config file. Then, refetch the value you need using ConfigurationManager.AppSettings["someKey"], which should return the new value24.

Here’s an example of how you can do this:

ConfigurationManager.RefreshSection("appSettings");
string value = ConfigurationManager.AppSettings["someKey"];

Remember, any changes made to the app.config file at runtime will not persist after the application is closed3. If you need to save these changes permanently, consider writing them to a separate user-specific configuration file or another form of persistent storage.

Thanks

We can't see the code mate 

i already did that but still not working .please look at whole code.

Try this

ConfigurationManager.RefreshSection("appSettings");

Hello, 

 

The reason behind why the app.config file is not getting reflected during update in Run time is as follows:

• When you add a new app.config file it actually creates a file in the local system.
• When you compile it, actually it creates the necessary files including .Exe files in Debug/Release folder; depending upon the Build mode.
• After successful build it also generates a .config file which looks like YourApplicationName.exe.config which holds the same entries in original app.config file. And the .Exe always refers to this file.
• So whenever you edit the app.config at Runtime it actually updates the file but changes are not updated in YourApplicationName.exe.config file as it has not re-build yet.

So every time you need to re-build to your app to reflect the changes.

Regards,
BENCHAABAN Ali