NLog和Prism的正确实现
在我的 Prism / CAL WPF 应用程序中实现 NLog 的最佳方法是什么？这可能是一个业余问题，我对整个 Prism 框架有点陌生:)
我考虑将对 NLog dll 的引用放在基础设施模块中，并制作一个包装单例类，例如 MyLogger。我的想法是能够在所有内容都引用的中心位置的某个地方引用 1 个记录器实现，而我在 Prism 中唯一知道的是您的基础设施模块。
另一种明显的方法是向每个模块添加对 NLog 的引用，但我认为这会破坏解耦的目的以及所有这些。
任何想法都会是最有帮助的
问候
What would be the best way to implement NLog in my Prism / CAL WPF application. This might be an amateur question, I am a bit new to the whole Prism framework :)
I thought about putting the reference to the NLog dll in the Infrastructure module and make a wrapper singleton class e.g. MyLogger. My thinking was to be able to have the reference to 1 logger implementation somewhere in a central place that everything has reference to, and the only thing that I know of in Prism would be your Infrastructure module.
The obvious other way is to add a reference to NLog to each module but I think that would defeat the purpose of decoupling and all of that.
Any ideas would be most helpful
Regards
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我会推荐与您的第一个想法类似的东西，尽管它利用了 Prism 中已有的界面。
虽然我不确定 NLog 中可用的确切方法签名，但您可能需要考虑使用 Prism 的 ILoggerFacade 接口，通常在 Bootstrapper 中定义（请参阅 StockTraderRI 应用程序，了解如何设置的示例）。通常，这充当 Microsoft 的复合日志记录界面的传递，但是您没有理由不能使用它来连接您自己的记录器。
考虑这种方法的几个原因：
另一种方法是按照您的建议进行操作：在基础结构 DLL 中创建一个定义 NLog 服务的接口（或公开现有的 NLog 接口），并在引导程序中注册该服务的实现。然后，您可以使用依赖项注入容器来获取对模块中记录器服务的引用。但请注意，这实际上只是重现了 ILoggerFacade 接口已经为您提供的内容。
I would recommend something similar to your first idea, although it leverages an already existing interface in Prism.
While I'm not sure the exact method signatures available to you in NLog, you may want to consider using Prism's ILoggerFacade interface, which is typically defined in your Bootstrapper (see the StockTraderRI application for an example of how this is set up). Typically, this acts as a pass through to Microsoft's Composite Logging interface, but there's no reason why you can't use this to hook into your own logger.
A few reasons to consider this approach:
The other approach would be to do as you suggest: create an interface that defines a service to NLog (or expose an existing NLog interface) in your infrastructure DLL and register the implementation of that service in your bootstrapper. You can then you your dependency injection container to get a reference to the logger service in your modules. Note, however, that this really just reproduces what the ILoggerFacade interface already gives you.