7

My asp.net app has is using a web.config for common configuration. I also have a section that maps some data objects to connection strings, and that section is going to be couple thousand of lines. I want to move that section to another config file "dataMappings.config", so I don't bulk up web.config - is there a standard mechanism of accessing that config file?

Thank you, Andrey

Andrey
  • 20,487
  • 26
  • 108
  • 176

2 Answers2

12

In each section, you can define configSource, which can point to an external file path. Here's a simple example:

<connectionStrings configSource="myConnectionStrings.Config" />
<appSettings configSource="myAppSettings.Config" />

Just make sure not to use .xml file extension since it can be viewed in a browser. .config will not be served by the web server.

Because your config sections are still defined in the web.config (thus pointing to external files), you can access this information via the normal routes (WebConfigurationManager.AppSettings, WebConfigurationManager.GetSection, ConfigurationManager, or custom section handlers as needed)

KP.
  • 13,218
  • 3
  • 40
  • 60
  • Will it work if I am using a custom section? Or do I need to do something in that custom section code to support configSource attribute? – Andrey Feb 09 '10 at 20:01
  • @Andrey: this will work with **any** `ConfigurationSection` in the .NET 2.0 and up framework. – marc_s Feb 09 '10 at 20:14
  • It should work. Here's another discussion on that point: http://stackoverflow.com/questions/398607/how-to-enable-configsource-attribute-for-custom-configuration-section-in-net – KP. Feb 09 '10 at 20:14
2

I used a configuration helper in a shared DLL, and an app.config file in the DLL that uses the Settings.Properties.Default stuff by editing the project and setting the settings tab. It appears that value isn't read unless you recompile, and resync the app.config (in the dll) with the project settings.

This works for me. I don't remember where I got the inspiration. I just include this class in a shared project somewhere. allows any DLL to call its own settings, which allows you to change the dllFile.dll.config entries. I use this for connection strings. The caveat is that in this method, the connection string has to be a type string, and not the special connection string. 

using System;
using System.Configuration;

namespace Shared
{
    public static class ConfigurationHelper
    {
        public static string GetConfigValue(string keyName)
        {
            string codebase = System.Reflection.Assembly.GetCallingAssembly().CodeBase;  
            Uri p = new Uri(codebase);
            string localPath = p.LocalPath.ToLowerInvariant();
            string executingFilename = System.IO.Path.GetFileNameWithoutExtension(localPath);
            string sectionGroupName = "applicationSettings";
            string sectionName = executingFilename + ".Properties.Settings";
            string configName = localPath + ".config";
            ExeConfigurationFileMap fileMap = new ExeConfigurationFileMap();
            fileMap.ExeConfigFilename = configName;
            Configuration config = ConfigurationManager.OpenMappedExeConfiguration(fileMap, ConfigurationUserLevel.None);
            ConfigurationSectionGroup group = config.GetSectionGroup(sectionGroupName);
            ClientSettingsSection section = null;
            foreach (ClientSettingsSection sect in group.Sections)
            {
                if (sect.SectionInformation.Name.Equals(sectionName, StringComparison.InvariantCultureIgnoreCase))
                {
                    section = sect;
                    break;
                }
            }
            SettingElement elem = section.Settings.Get(keyName);
            if (elem == null)
                return "";
            else
                return elem.Value.ValueXml.InnerText.Trim();
        }
    }
}

//in DLL
void foo()
{
    var str = ConfigurationHelper.GetSetting("ConnectionStringProd");
}
realPT
  • 1,085
  • 9
  • 8