Microsoft | patterns & practices | Developer Network | Enterprise Library | Acceptance Testing Guide | Personal Site
SQL Configuration Source for Enterprise Library 5.0 is now available. It allows storing configuration information in a database. It’s strengthened with encryption and change monitoring.
We are shipping this as source code here: http://entlib.codeplex.com/releases/view/56812
The project is set up to build against the signed binaries released with Enterprise Library 5.0. If you wish to compile against a different copy of Enterprise Library, please read the release notes for instructions on how to customize and deploy.
We also provide a batch file and SQL script to create the required database schema for you.
Do keep in mind that the SqlConfiguration source supports only a subset of the features the SystemConfigurationSource and FileConfigurationSource do.
I have a simple question. You say <appsettings> is stored still in the physical configuration file and not the database. Is this a limitation of this implementation of the SqlConfigurationSource you have created or a limitation of the technology?
Yes, Shumii, it's a limitation of our implementation.
There was a trade off there, with two conflicting expectations: that app settings edited with the configuration tool could be read using the framework's ConfigurationManager.AppSettings property (msdn.microsoft.com/.../system.configuration.configurationmanager.appsettings.aspx), and that the settings were stored in the configuration source. We decided that the first requirement was more important, hence the current implementation.