{"id":511,"date":"2003-09-26T00:39:11","date_gmt":"2003-09-26T04:39:11","guid":{"rendered":"http:\/\/wordpress.cephas.net\/?p=511"},"modified":"2003-09-26T00:39:11","modified_gmt":"2003-09-26T04:39:11","slug":"extending-webconfig-in-aspnet","status":"publish","type":"post","link":"https:\/\/cephas.net\/blog\/2003\/09\/26\/extending-webconfig-in-aspnet\/","title":{"rendered":"Extending web.config in ASP.NET"},"content":{"rendered":"

Last March I wrote<\/a> about how handy it is that ASP.NET enables you to add your own custom settings to the web.config file using syntax like this:<\/p>\n

<appSettings>
\n<add key=”connString” value=”user id=sa;password=mypassword;” \/>
\n<\/appSettings><\/p>\n

This is nice, but can quickly get unwieldy if you have alot application settings to maintain. Back in March I failed to mentioned (because I didn’t know about it) that you can extend your web.config even further by creating your own custom configuration sections. You can read more about the ConfigurationSettingsSchema<\/a> on msdn, but here’s a quick example. First you define the custom application settings:<\/p>\n

<configSections>
\n   <sectionGroup name=”myapplication”>
\n      <section name=”types” type=”System.Configuration.NameValueSectionHandler”\/>
\n      <section name=”security” type=”System.Configuration.NameValueSectionHandler”\/>
\n    <\/sectionGroup>
\n<\/configSections><\/p>\n

and then you add the actual settings:<\/p>\n

<myapplication>
\n   <types>
\n      <add key=”section” value=”com.ignitionlabs.Section” \/>
\n      <add key=”template” value=”com.ignitionlabs.Template” \/>
\n   <\/types>
\n   <security>
\n      <add key=”\/controlpanel\/” value=”Systems Administrators,Project Managers” \/>
\n      <add key=”\/members\/” value=”members” \/>   
\n   <\/security>
\n<\/myapplication><\/p>\n

Finally, you can use the exact same XPATH syntax that you use when retrieving other application settings. In the above example, there are multiple ‘type’ elements, so I’d first get a NameValueCollection object:<\/p>\n

NameValueCollection config = (NameValueCollection)System.Configuration.ConfigurationSettings.GetConfig(“myapplication\/types”);<\/p>\n

and then retrieve the value of the “section” key using the name:<\/p>\n

string section = config[“section”];<\/p>\n

Enjoy!<\/p>\n","protected":false},"excerpt":{"rendered":"

Last March I wrote about how handy it is that ASP.NET enables you to add your own custom settings to the web.config file using syntax like this: <appSettings> <add key=”connString” value=”user id=sa;password=mypassword;” \/> <\/appSettings> This is nice, but can quickly get unwieldy if you have alot application settings to maintain. Back in March I failed … Continue reading Extending web.config in ASP.NET<\/span> →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[17],"tags":[],"_links":{"self":[{"href":"https:\/\/cephas.net\/blog\/wp-json\/wp\/v2\/posts\/511"}],"collection":[{"href":"https:\/\/cephas.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cephas.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cephas.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/cephas.net\/blog\/wp-json\/wp\/v2\/comments?post=511"}],"version-history":[{"count":0,"href":"https:\/\/cephas.net\/blog\/wp-json\/wp\/v2\/posts\/511\/revisions"}],"wp:attachment":[{"href":"https:\/\/cephas.net\/blog\/wp-json\/wp\/v2\/media?parent=511"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cephas.net\/blog\/wp-json\/wp\/v2\/categories?post=511"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cephas.net\/blog\/wp-json\/wp\/v2\/tags?post=511"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}