The easiest way to add some control would be through app settings and have the application configuration itself appropriately. If you wanted full XML integration you could
create a custom configuration section.

Forgive me if this has already been answered before, but what is the reasoning of the team to NOT enable xml config like other Entlib blocks do and even ENCOURAGE we to do the config programmatically which kind of contra the common wisdom?

Is that because the SLAB is still too new or the team is too busy on other important things?

Programmatic vs. declarative (XML) configuration is a topic where you could probably dredge up a good argument (not quite at the level of tabs vs. spaces or bracket placement, though ;) ).

In my experience the trend these days is leaning towards programmatic configuration which is why the preferred
configuration approach for Enterprise Library 6 is a "flexible programmatic approach". I think it was for that reason that there is no in-process configuration for the new Semantic Logging Application Block.

Thanks again for updating me this, I've no idea at all that this is a trend now, would you mind to point me to somewhere showing this kind of heated debate? I really don't understand how will configuration-by-code could handle after-deployment-changes?