UI web.config references to Infrastructure

Apr 24, 2013 at 5:53 PM
Hello, I another question!

One of the 'side effects' of the Onion architecture is abstracting the UI layer away from the infrastructure, no? The UI is supposed to work with infrastructure interfaces, defined in Core and injected by the Dependency Resolution.

Although this is clearly achieved, in the web.config we can still see (configuration) references to log4net, Entity Framework, WCF bindings and etc.

What do you think about that? Isn't it a problem that the UI actually KNOWS what the concrete interface implementations are and even further - KNOWS what kind of configuration they expect.

My first thought was putting this kind of configuration in the SomeDllName.dll.config file. Then we should basically have self-configuring DLLs. But then I thought - if we split all the configuration among the different dll config files - who owns the configuration? It should be centralized, as it currently is. But if it is centralized, then the UI layer has knowledge of the implementations. Paradox.

What is your opinion on this?

Best regards,