Skip to main content

Quick Log4net setup

Log4net has lots of options and different ways it could be configured - these are notes written to myself so that I can get it working quickly.

1. Download log4net

Download from here.

2. Drop DLL in Bin folder

In the download package, there are various DLLs, usually you'll want the .net 2.0 release version at:
incubating-log4net-1.2.10\log4net-1.2.10\bin\net\2.0\release
If you have an ASP.NET Web Application Project (as opposed to an ASP.NET Web Site) then you'll also need to add a reference to the DLL.

3. Add a Configurator line in the Global.asax

There are various ways of telling Log4net to pick up its config. We're going to use the Xml Configurator that pulls config from a separate config file. Add this line of code to Application_Start in the Global.asax:
void Application_Start(object sender, EventArgs e) 
{
    log4net.Config.XmlConfigurator.Configure();
}
4. Add an AppSetting to the web.config

The XmlConfigurator.Configure() call above, tells Log4net to look for a certain key in appSettings. The key gives the name of the config file. So we add the correct appSetting entry to web.config, like this:
<appSettings>
    ...
    <add key="log4net.Config" value="logging.config" />
    ...
5. Add a logging.config file

In the root folder (same folder as web.config), add the following logging.config file:
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
  <log4net>
    <appender name="LogFileAppender" type="log4net.Appender.FileAppender">
      <param name="File" value="App_Data/Log.txt" />
      <param name="AppendToFile" value="true" />
      <layout type="log4net.Layout.PatternLayout">
        <param name="ConversionPattern" value="%d thread%-2t %-5p src:%-25c - %m%n" />
      </layout>
    </appender>

    <root>
      <level value="ALL" />
      <appender-ref ref="LogFileAppender" />
    </root>
  </log4net>
</configuration>
This has basic options for logging to a text file in the App_Data folder (make sure you have an App_Data folder). Its set to log everything, because during development thats what you'll want to do, right?

6. Add logging statements

One good pattern for this is to have a static logger for each page:
public partial class MyWebPage : System.Web.UI.Page
{
    private static readonly ILog logger = LogManager.GetLogger(typeof(MyWebPage));
    
    protected void Page_Load(object sender, EventArgs e)
    {
        logger.Debug("page load");
    }
    ...


So ... thats one way of doing it. There are, of course, millions of other ways.

Comments

Popular posts from this blog

Copying data to Salesforce Sandboxes using TalenD

A common problem with Salesforce Developer Sandboxes is that they are blank. Really you're going to want some data in there, so there are various strategies for copying data from your live instance to the Sandbox. There are some paid-for solutions - SFXOrgData , Salesforce Partial Data Sandboxes - but if you've got a decent ETL tool you can build your own. There are a bunch of free ETL tools for Salesforce: JitterBit Data Loader is good for quick ad-hoc tasks but the free version makes it difficult to manage specific ETL projects or share projects with other users Pentaho Community Edition - an open source edition of the enterprise version Apatar was a free open source Salesforce ETL which still works but development seems to have stopped since 2011 TalenD Open Studio is an open source ETL tool For the task of copying data from live to a Sandbox, either Pentaho or TalenD Open Studio could be used, depending on preference. Here's a good comparison of the dif

SSRS multi-value parameters with less fail

SSRS supports multi-value parameters, which is nice, but there are a few issues with them. This is how I deal with them. Two of the problems with SSRS multi-value parameters are: You have to jump through a few hoops to get them to work with stored procedures The (Select All) option, as shown above The reason the (Select All) option is a problem is that it is a really inelegant way of saying 'this parameter does not matter to me'. If you have a list with hundreds of values, passing all of them as a default option just seems wrong. Also, if your report shows the user which items they selected, printing the whole list when they choose (Select All) is excessive. So in this post I'm going to show my particular way of: Jumping through the hoops to get Multi-Value params in a stored procedure Adding a single '--All--' value that the report interprets as meaning all the options. Getting Multi-Value params to work with Stored Procedures This is

Remote Desktop on High DPI screens

Scott Hanselman wrote a nice blog post back in January about some of the issues you might face running Windows on a High DPI screen like that of a Surface Pro or Lenova Yoga. I'm kindof mystified that he didn't mention Remote Desktop though because thats been the number one problem for me on High DPI screens. That said, if you remote into very recent Server OS's like Windows Server 2012 R2, then apparently Remote Desktop will sort out the DPI scaling automatically. Perhaps Scott hadn't noticed the Remote Desktop issue because he only remotes into Server 2012 R2. Certainly if I was Scott, I wouldn't remote into anything less than that. But, in practice, I regularly have to remote into Server 2008 machines and yes even Server 2003. If you do that from a high DPI screen, the remote desktop is rendered at regular pixel size, which makes everything tiny. Its hard to show screenshots of High DPI screens that correctly convey the pixel size, so I've photoshoppe