ASP.NET - Have settings in the Web.config (and access them using ConfigurationSection) or in a separate XML file?

From performance standpoint putting custom settings in web. Config and creating a configuration handler will be OK because the config values are cached and read only once when the application starts. Putting the values in a separate XML file you will need to handle the caching your self if you want to avoid parsing it every time you need to access those values.

3 One more benefit of keeping everything in web. Config is that future developers will probably be more comfertable with it, since its likely a system they will have previous experience with. – Nate Sep 20 '10 at 6:22 +1 I would absolutely agree.

– ydobonmai Sep 20 '10 at 6:25 Darin, what would be the difference If the application is a Windows service and If I have those settings in the App. Config or the custom config handler? For me, the additional file problem remains.

– ydobonmai Sep 20 '10 at 6:33 1 The configuration system works the same no matter the type of application. – Darin Dimitrov Sep 20 '10 at 6:35.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.