Log4net - 使用继承时的最佳策略

发布于 2024-09-29 07:48:21 字数 358 浏览 0 评论 0原文

我已将 log4net 集成到我的应用程序中。我有一些辅助方法来帮助记录调用 log4net 的日志。重构时，我计划将这些方法移至基类，以便代码不会在其他派生类中重复。

如果没有继承模型，则以下内容在每个类中都可以正常工作

private static readonly ILog Log = LogManager.GetLogger(MethodBase.GetCurrentMethod().DeclaringType);

将上述内容放入基类中将返回声明类型作为基类而不是派生类。

将此声明移动到基类的最佳方法是什么？

目前，我可以想到一些方法来实现这一目标，但发现它们不是最佳的。

原文

I have integrated log4net in my app. I have a few helper methods to assist in logging which call log4net. When refactoring, I plan to move these methods to base class so that the code is not repeated in other derived classes.

Without the inheritance model, following worked correctly in each class

private static readonly ILog Log = LogManager.GetLogger(MethodBase.GetCurrentMethod().DeclaringType);

Placing the above in the base class will return the declaring type as base class and not derived class.

What is an optimal way to move this declaration to the base class?

At present, I can think of a few ways to achieve this but don't find them optimal.

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

万劫不复 2024-10-06 07:48:21

我想我会这样做：

LogManager.GetLogger(this.GetType());

I think I would do this:

LogManager.GetLogger(this.GetType());

回复收藏 0 原文

亽野灬性zι浪 2024-10-06 07:48:21

根据 Sefan 的回答，这是我在基类中声明它的方式

/// <summary>
    /// This is delay loaded to allow us to capture the class type of the inherited class on request
    /// </summary>
    private ILog log = null;

    protected ILog Log
    {
        get
        {
            if (log == null)
            {
                log = LogManager.GetLogger(this.GetType());
            }

            return log;
        }
    }

Based on Sefan's answer here's how I declared it in the base class

/// <summary>
    /// This is delay loaded to allow us to capture the class type of the inherited class on request
    /// </summary>
    private ILog log = null;

    protected ILog Log
    {
        get
        {
            if (log == null)
            {
                log = LogManager.GetLogger(this.GetType());
            }

            return log;
        }
    }

回复收藏 0 原文

手长情犹 2024-10-06 07:48:21

我们只需在需要记录器的每个类中重新声明它（其要点是私有静态），并使用代码片段使其变得像键入 log一样简单; 如果你想要额外的花哨，你可以这样做：

public class Loggable<T> where T : Loggable<T>
{
    private static readonly ILog log = LogManager.GetLogger(typeof(T));

    protected static ILog Log
    {
        get
        {
            return log;
        }
    }
}

并通过你的继承层次结构打孔 T，使其成为最派生的类。
这里所有答案的问题是您丢失了有关日志消息来自何处的信息，因此尽管添加了样板，我个人仍会坚持使用原始代码。

We just redeclare it in each class that needs a logger (the point of it being a private static) and use a code snippet to make that as simple as typing log<tab><tab> if you wanted to get extra fancy though you could do something like:

public class Loggable<T> where T : Loggable<T>
{
    private static readonly ILog log = LogManager.GetLogger(typeof(T));

    protected static ILog Log
    {
        get
        {
            return log;
        }
    }
}

And punch T through your inheritance hierarchy so that it is the most derived class.
The problem with all of the answers here is that you lose information about where log messages are coming from, so I would personally stick to your original code despite the added boilerplate.

回复收藏 0 原文

~没有更多了~