.Net Tips – using configSource or file attribute to externalize config sections

There’s a little known attribute which was introduced in the .Net framework 2.0 called configSource, which allows you to externalize sections of the configuration file.

It works just like the optional file attribute found on the appSettings element:

<appSettings file = “relative file name” />

but can be added to any configuration section to specify an external file for that section:

<CustomSection configSource=”relative file name” />

When it comes to WCF though, unfortunately the configSource attribute doesn’t work on the <system.serviceModel> section group, but luckily you can still apply it on the child config sections. See the reference link below for some examples.

Reference:

http://weblogs.asp.net/cibrax/archive/2007/07/24/configsource-attribute-on-system-servicemodel-section.aspx

Liked this article? Support me on Patreon and get direct help from me via a private Slack channel or 1-2-1 mentoring.
Subscribe to my newsletter


Hi, I’m Yan. I’m an AWS Serverless Hero and the author of Production-Ready Serverless.

I specialise in rapidly transitioning teams to serverless and building production-ready services on AWS.

Are you struggling with serverless or need guidance on best practices? Do you want someone to review your architecture and help you avoid costly mistakes down the line? Whatever the case, I’m here to help.

Hire me.


Check out my new course, Complete Guide to AWS Step Functions. In this course, we’ll cover everything you need to know to use AWS Step Functions service effectively. Including basic concepts, HTTP and event triggers, activities, callbacks, nested workflows, design patterns and best practices.

Get Your Copy