Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Logging frameworks should be de-coupled from the SIF Framework so that any logging framework can be supported #18

Open
kunalyadavdfe opened this issue Dec 14, 2016 · 1 comment

Comments

@kunalyadavdfe
Copy link

Environment - "open standards": Use of open standards - logging frameworks should be de-coupled from the SIF Framework so that any logging framework can be supported.
Log4Net – The current SIF framework is tightly coupled with log4Net rather than it being configurable. An end organisation who might not use this is then forced to use it rather than choosing whatever else they want to use. Logging frameworks should be generic and the framework should be able to support any number of logging frameworks as needed rather than embedding it within the framework

@rafidzal
Copy link
Contributor

Unlike Java with slf4j, there doesn't appear to be a universally accepted and supported logging facade for .NET. As such, an logging abstraction framework would need to be selected or a logging facade developed. This work would ideally be done once DI is incorporated into the SIF Framework.

joerghuber pushed a commit that referenced this issue Mar 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants