Tag Info

New answers tagged

2

My experience in this sort of thing is to prefer to stay consistent within my program. In other words, you feel you can't do without a database, then your program would likely be more robust if it depended only on that database rather than also on the file system. The more components your program depends on, the more problematic it becomes in terms of ...


0

Have you thought about breaking up your config file into several files? Look into configsource, which allows you to refer to a separate file for a section in your config. <pages configSource="pages.config"/> http://msdn.microsoft.com/en-us/library/system.configuration.sectioninformation.configsource%28v=vs.110%29.aspx You can use that to put ...


0

In our applications, we only use the app.config to point to the related servers (web, db, license). Any other kind of configuration data is either stored as a local user config file (assumed it is configuration data only important for look-and-feel of the application of the local machine, thus dispensable) or stored in the database (if it is more ...


1

I think part of the issues you're facing is in the premise: Upgrading an application with a modified app.config is hard. Either it overwrites the existing configuration file or the upgraded app.config isn't installed at all. Don't do that, basically. Configuration is a software artefact, and it should be versioned and go through the same lifecycle ...



Top 50 recent answers are included