ConfigurationManager.AppSettings["SettingName"] vs Properties.Settings.Default.SettingName when should I use each?

.net configuration appsettings
Sam Holder picture Sam Holder · Dec 16, 2009 · Viewed 10.8k times · Source

What should dictate when I should use the configurationManager.AppSettings or the strongly typed settings that visual studio generates? The strongly typed ones seem much more appropriate in most cases, but I suppose that it would be possible to add settings dynamically to a deployed application using the ConfigurationManager approach, but are there any guidelines under which circumstances each is designed to be used?

Answer

ram picture ram · Dec 16, 2009

From what I read, looks like AppSettings is the older way of doing things. MSDN docs states that user settings can be written at run time if you are using settings.

I always prefer strongly typed settings, which can be implemented with ConfigSection handlers.

Pros and cons of appSettings vs applicationSettings (.NET app.config)

Related questions

Reading settings from app.config or web.config in .NET

I'm working on a C# class library that needs to be able to read settings from the web.config or app.config file (depending on whether the DLL is referenced from an ASP.NET web application or a Windows Forms …

Read More
Multiple AppSettings files, is it possible?

I want to create 3 AppSettings config files: Database.config Messages.config Global.config And after add in my App.config: <appSettings file="Database.config" /> <appSettings file="Messages.config" /> <appSettings file="Global.config" /> But when …

Read More
What is the difference between app.config file and XYZ.settings file?

I am actually in the learning phase of .NET related stuff and I was exploring how to save the application. I ended up writing my own class which saves the settings in an XML file and then I found that .…

Read More