Two words... dependency injection.
More likely than not, your Logging
assembly has absolutely no business knowing about the Settings
assembly. It should probably either:
- Expect some environment variable to be set in the app domain telling it where to log, with a sensible default if not provided
- Expect something to tell it where to log (perhaps by setting a property on the logger)
In either option, the entry-point to your app is a good place to do this. Maybe in your first few lines of code you'd do something like:
Logger.LogFilePath = Settings.Manager.GetCurrentErrorFileName();