I have read through a few posts on this forum regarding the fluent api configuration and it's compatibility with file based ent lib configuration. Apparently, if you utilize the fluent api to setup during runtime logging, exception handling, database
connections the 'update' operation completely replaces any file based ent lib configuration.
While there appear to be a couple attempts to make these compatible, they do come with some limitations or complexities themselves.
That being said, is it possible to perform both fluent api configuration for ent lib AND file based configuration in an additive manner? (anyway?)
Our scenario.. we need to decrypt the connectionstring and pass it into any database operations with ent lib (i.e logging to the db). I have been able to do this entirely with fluent api, but I do not want to limit my developers from using file based
configuration in any manner for say exception management options.
Can you provide insight on the the limitations of using fluent api? What are developers doing to work around the fact that any fluent api operation completely wipes away and file based configuration?