Yaojian | 2 Apr 16:33 2009
Picon

When will the next version be released?

Hi

anyone know that?


Peter Drier | 2 Apr 17:20 2009
Picon

Re: When will the next version be released?

Maybe when someone comes up with a legit feature need that it doesn't  
already cover?

Seriously though, I've been using 1.2.10 for years now and log4net has  
been the most reliable 3rd party package I've used across many  
applications. The only things I've needed that it couldn't do fit  
easily in the appender and plugin frameworks.

Don't fix what isn't broken!

Peter

On Apr 2, 2009, at 10:33 AM, Yaojian <skyaoj <at> gmail.com> wrote:

> Hi
>
> anyone know that?
>
>

daniel.nitecki | 2 Apr 17:27 2009

Re: When will the next version be released?

Has anyone made efforts to add the Mutex file locking scheme for file appenders into the source?  Someone
posted code for it  a while ago and I've been making use of it.  This could be worthy of a minor rev...

                                                                                                         
             Peter Drier                                                                                 
             <peter.drier <at> gmail.com>                                                                     
                                                                                                      To 
             04/02/2009 11:20 AM                   Log4NET User <log4net-user <at> logging.apache.org>        
                                                                                                      cc 
                                                   "log4net-user <at> logging.apache.org"                     
                   Please respond to               <log4net-user <at> logging.apache.org>                     
                    "Log4NET User"                                                               Subject 
             <log4net-user <at> logging.apache.         Re: When will the next version be released?           
                         org>                                                                            

Maybe when someone comes up with a legit feature need that it doesn't
already cover?

Seriously though, I've been using 1.2.10 for years now and log4net has
been the most reliable 3rd party package I've used across many
applications. The only things I've needed that it couldn't do fit
easily in the appender and plugin frameworks.

Don't fix what isn't broken!

Peter

On Apr 2, 2009, at 10:33 AM, Yaojian <skyaoj <at> gmail.com> wrote:

> Hi
>
> anyone know that?
>
>

Yaojian | 2 Apr 17:35 2009
Picon

Re: When will the next version be released?

I am totally agree with the reliable of log4net.

I just want a bug-fix version, espically the UdpAppender issue https://issues.apache.org/jira/browse/LOG4NET-112

As lots of third-party components (for example, NHibernate) rely on log4net's public GA 1.2.10, I have to rebuild all these third-party components with my private build from the log4net svn :-(

On Thu, Apr 2, 2009 at 11:20 PM, Peter Drier <peter.drier <at> gmail.com> wrote:
Maybe when someone comes up with a legit feature need that it doesn't already cover?

Seriously though, I've been using 1.2.10 for years now and log4net has been the most reliable 3rd party package I've used across many applications. The only things I've needed that it couldn't do fit easily in the appender and plugin frameworks.

Don't fix what isn't broken!

Peter

On Apr 2, 2009, at 10:33 AM, Yaojian <skyaoj <at> gmail.com> wrote:

Hi

anyone know that?



steven higgan | 3 Apr 11:29 2009
Picon

Re: When will the next version be released?

are you serious ??

i wold have thought the brokenness of the udp appender and the patch
that is available would have been enough to push out a new release.

sure i _can_ patch it myself but in my corporate environment and a
requirement to only use official releases for clients means that I
simply cant.

doing a quick diff between trunk  <at>  head and the last release we can
see that a lot of files have been changed, doing a quick log we can
see that there are approximately three years worth of new features and
bug fixes, and to be honest if the churn is substantial enough the
shear volume of changes may mean real-world usage may turn up all
sorts of interesting stuff happening.

on the upside it compiles in VS2008 (dont have 2k5 installed), but at
least on my server 2k8 laptop with uac and visual studio running as a
normal user I get test failures (security exceptions) and two other
failures which look more intresting
(log4net.Tests.Util.LogLogTest.EmitInternalMessages() in
LogLogTest.cs: line 33  &
log4net.Tests.Util.LogLogTest.LogReceivedAdapter() in LogLogTest.cs:
line 54)

what will it take to get a release out the door ?

On Fri, Apr 3, 2009 at 4:20 AM, Peter Drier <peter.drier <at> gmail.com> wrote:
> Maybe when someone comes up with a legit feature need that it doesn't
> already cover?
>
> Seriously though, I've been using 1.2.10 for years now and log4net has been
> the most reliable 3rd party package I've used across many applications. The
> only things I've needed that it couldn't do fit easily in the appender and
> plugin frameworks.
>
> Don't fix what isn't broken!
>
> Peter
>
> On Apr 2, 2009, at 10:33 AM, Yaojian <skyaoj <at> gmail.com> wrote:
>
>> Hi
>>
>> anyone know that?
>>
>>
>

mhgms2 | 3 Apr 17:17 2009
Picon

Newbie help for programatically creating log without a config file

Hi:

I am trying to create a test program that configures a logger completely 
from code (I want to avoid a config/xml file for this exercise), but 
although I'm not getting any errors, no log file is created.

Can anyone help?

Regards,
Martin.

Here is my code:

using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Linq;
using System.Text;
using System.Windows.Forms;

namespace log4net
{
  public partial class FrmMainFormLog4Net : Form
  {
    private enum LogDestination { None, File, Access, MsSql }

    private static LogDestination logDestinationType = LogDestination.None;
    private static readonly log4net.ILog log = log4net.LogManager.GetLogger(
      System.Reflection.MethodBase.GetCurrentMethod().DeclaringType);

    public FrmMainFormLog4Net()
    {
      InitializeComponent();
      //log4net.Config.XmlConfigurator.Configure();  //--- Load from 
App.Config file
      //log4net.Config.BasicConfigurator.Configure(); //--- Use Console 
output
      setupLogDestino(LogDestination.File);
    }

    private void button_Click(object sender, EventArgs e)
    {
      if(sender == btnDebug)
        log.Debug("*Debug message");
      else if(sender == btnInfo)
        log.Info("**Information message");
      else if(sender == btnWarn)
        log.Warn("***Warning message");
      else if(sender == btnError)
        log.Error("****Error message");
      else if(sender == btnFatal)
        log.Fatal("*****Fatal message", new Exception("My exception 
message"));
    }

    private void destino_CheckedChanged(object sender, EventArgs e)
    {
      RadioButton rb = sender as RadioButton;
      if(rb != null)
      {
        if(rb == rbFile && rb.Checked)
          setupLogDestino(LogDestination.File);
        else if(rb == rbAccess && rb.Checked)
          setupLogDestino(LogDestination.Access);
        else if(rb == rbMsSql && rb.Checked)
          setupLogDestino(LogDestination.MsSql);
      }
    }

    private static void setupLogDestino(LogDestination destination)
    {
      if(destination != logDestinationType)
      {
        log4net.Layout.PatternLayout layout = new 
log4net.Layout.PatternLayout("%d [%t] %-5p %c [%x] &lt;%X{auth}&gt; - 
%m%n");
        switch(destination)
        {
          case LogDestination.File:
            {
              string logFileName = System.IO.Path.Combine(
                AppDomain.CurrentDomain.BaseDirectory,
                System.IO.Path.ChangeExtension(AppDomain.CurrentDomain.FriendlyName, 
".log"));
              log4net.Appender.FileAppender appender = new 
log4net.Appender.FileAppender
                {
                  AppendToFile = true,
                  File = logFileName,
                  Layout = layout,
                  Threshold = log4net.Core.Level.All
                };
              log4net.Config.BasicConfigurator.Configure(appender);
            }
            break;
          case LogDestination.Access:
            //--To do
            break;
          case LogDestination.MsSql:
            //--To do
            break;
        }
      }
    }
  }
}

Peter Drier | 4 Apr 20:23 2009
Picon

Re: When will the next version be released?

So the last time log4net upgraded from .9 to .10, that process was actually somewhat painful for me..  as you note a lot of components rely on log4net .10..  And dealing with different versions of log4net simultaneously wasn't fun (we weren't allowed to gac it for various reasons, nor do you want 2 copies of log4net loaded into a single process anyways). 

Now, given that most to all of the updates/bug fixes are in the appenders, it may make sense to split log4net into 2 packages..  one that's the core log4net bits + appender skeleton + interfaces..  and one that's the bundled appenders.. 

That way, the third party packages (nunit, nhibernate, ...) can depend on the core log4net bits without having to upgrade every time Nicko does a appender bug fix.. 

This may even be enough to warrant a 1.3 ?

Nicko?

-Peter


On Thu, Apr 2, 2009 at 11:35 AM, Yaojian <skyaoj <at> gmail.com> wrote:
I am totally agree with the reliable of log4net.

I just want a bug-fix version, espically the UdpAppender issue https://issues.apache.org/jira/browse/LOG4NET-112

As lots of third-party components (for example, NHibernate) rely on log4net's public GA 1.2.10, I have to rebuild all these third-party components with my private build from the log4net svn :-(


On Thu, Apr 2, 2009 at 11:20 PM, Peter Drier <peter.drier <at> gmail.com> wrote:
Maybe when someone comes up with a legit feature need that it doesn't already cover?

Seriously though, I've been using 1.2.10 for years now and log4net has been the most reliable 3rd party package I've used across many applications. The only things I've needed that it couldn't do fit easily in the appender and plugin frameworks.

Don't fix what isn't broken!

Peter

On Apr 2, 2009, at 10:33 AM, Yaojian <skyaoj <at> gmail.com> wrote:

Hi

anyone know that?




Radovan Raszka | 6 Apr 07:48 2009
Picon

RE: Newbie help for programatically creating log without a config file

Hello, read this:
http://mail-archives.apache.org/mod_mbox/logging-log4net-user/200805.mbox/%3c2AD7ECA75635F84A87792C0B2F8692487DDC03 <at> EXCH3.ads.bruker.de%3e
It should help you
Radovan 

-----Původní zpráva-----
Od: mhgms2 [mailto:mhgms2 <at> gmail.com] 
Odesláno: 3. dubna 2009 17:18
Komu: log4net-user <at> logging.apache.org
Předmět: Newbie help for programatically creating log without a config file

Hi:

I am trying to create a test program that configures a logger completely from code (I want to avoid a
config/xml file for this exercise), but although I'm not getting any errors, no log file is created.

Can anyone help?

Regards,
Martin.

Here is my code:

using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Linq;
using System.Text;
using System.Windows.Forms;

namespace log4net
{
  public partial class FrmMainFormLog4Net : Form
  {
    private enum LogDestination { None, File, Access, MsSql }

    private static LogDestination logDestinationType = LogDestination.None;
    private static readonly log4net.ILog log = log4net.LogManager.GetLogger(
      System.Reflection.MethodBase.GetCurrentMethod().DeclaringType);

    public FrmMainFormLog4Net()
    {
      InitializeComponent();
      //log4net.Config.XmlConfigurator.Configure();  //--- Load from App.Config file
      //log4net.Config.BasicConfigurator.Configure(); //--- Use Console output
      setupLogDestino(LogDestination.File);
    }

    private void button_Click(object sender, EventArgs e)
    {
      if(sender == btnDebug)
        log.Debug("*Debug message");
      else if(sender == btnInfo)
        log.Info("**Information message");
      else if(sender == btnWarn)
        log.Warn("***Warning message");
      else if(sender == btnError)
        log.Error("****Error message");
      else if(sender == btnFatal)
        log.Fatal("*****Fatal message", new Exception("My exception message"));
    }

    private void destino_CheckedChanged(object sender, EventArgs e)
    {
      RadioButton rb = sender as RadioButton;
      if(rb != null)
      {
        if(rb == rbFile && rb.Checked)
          setupLogDestino(LogDestination.File);
        else if(rb == rbAccess && rb.Checked)
          setupLogDestino(LogDestination.Access);
        else if(rb == rbMsSql && rb.Checked)
          setupLogDestino(LogDestination.MsSql);
      }
    }

    private static void setupLogDestino(LogDestination destination)
    {
      if(destination != logDestinationType)
      {
        log4net.Layout.PatternLayout layout = new log4net.Layout.PatternLayout("%d [%t] %-5p %c [%x]
&lt;%X{auth}&gt; - %m%n");
        switch(destination)
        {
          case LogDestination.File:
            {
              string logFileName = System.IO.Path.Combine(
                AppDomain.CurrentDomain.BaseDirectory,
                System.IO.Path.ChangeExtension(AppDomain.CurrentDomain.FriendlyName,
".log"));
              log4net.Appender.FileAppender appender = new log4net.Appender.FileAppender
                {
                  AppendToFile = true,
                  File = logFileName,
                  Layout = layout,
                  Threshold = log4net.Core.Level.All
                };
              log4net.Config.BasicConfigurator.Configure(appender);
            }
            break;
          case LogDestination.Access:
            //--To do
            break;
          case LogDestination.MsSql:
            //--To do
            break;
        }
      }
    }
  }
}

Walden H. Leverich | 6 Apr 16:15 2009

RE: When will the next version be released?

I forget, is the "official" release strongly named? And if so, did those other components reference it by strong name? I tend to hate strong naming! It's a logging component, if there's an upgrade I should be able to use it, why should I be tied to an older version just because you built against the older version?

 

-Walden

 

--

Walden H Leverich III

Tech Software

(516) 627-3800 x3051

WaldenL <at> TechSoftInc.com

http://www.TechSoftInc.com

 

Quiquid latine dictum sit altum viditur.

(Whatever is said in Latin seems profound.)

 

From: Peter Drier [mailto:peter.drier <at> gmail.com]
Sent: Saturday, April 04, 2009 2:24 PM
To: Log4NET User
Subject: Re: When will the next version be released?

 

So the last time log4net upgraded from .9 to .10, that process was actually somewhat painful for me..  as you note a lot of components rely on log4net .10..  And dealing with different versions of log4net simultaneously wasn't fun (we weren't allowed to gac it for various reasons, nor do you want 2 copies of log4net loaded into a single process anyways). 

Now, given that most to all of the updates/bug fixes are in the appenders, it may make sense to split log4net into 2 packages..  one that's the core log4net bits + appender skeleton + interfaces..  and one that's the bundled appenders.. 

That way, the third party packages (nunit, nhibernate, ...) can depend on the core log4net bits without having to upgrade every time Nicko does a appender bug fix.. 

This may even be enough to warrant a 1.3 ?

Nicko?

-Peter

On Thu, Apr 2, 2009 at 11:35 AM, Yaojian <skyaoj <at> gmail.com> wrote:

I am totally agree with the reliable of log4net.

I just want a bug-fix version, espically the UdpAppender issue https://issues.apache.org/jira/browse/LOG4NET-112

As lots of third-party components (for example, NHibernate) rely on log4net's public GA 1.2.10, I have to rebuild all these third-party components with my private build from the log4net svn :-(

 

On Thu, Apr 2, 2009 at 11:20 PM, Peter Drier <peter.drier <at> gmail.com> wrote:

Maybe when someone comes up with a legit feature need that it doesn't already cover?

Seriously though, I've been using 1.2.10 for years now and log4net has been the most reliable 3rd party package I've used across many applications. The only things I've needed that it couldn't do fit easily in the appender and plugin frameworks.

Don't fix what isn't broken!

Peter

On Apr 2, 2009, at 10:33 AM, Yaojian <skyaoj <at> gmail.com> wrote:

Hi

anyone know that?

 

 

Neil Haughton | 6 Apr 16:27 2009
Picon

RE: When will the next version be released?

Because if you don’t, surely you risk breaking existing applications when you upgrade log4net?

 

Regards,

 

Neil Haughton BSc MIET IEng(CEI)
Development Manager

 

Autoscribe Limited
Wellington House
Riseley Business Park
Basingstoke Road, Riseley
Berkshire RG7 1NW

 

Office: +44 (0) 118 984 0610
Fax:   +44 (0) 118 984 0611

 

Visit our website at: www.autoscribe.co.uk

 

Registered in Wales No: 1539748

 

**********************************************************DISCLAIMER*****************************************************

 

The contents of this email are confidential and are intended solely for the use of the individual or company to
whom it is addressed. If you have received this email in error then please accept our apology. If this is the case
we would be obliged if you would contact the sender and then delete this email. Opinions expressed in this email
are those of the individual and do not necessarily represent the opinions of Autoscribe Ltd. Although this email
and any attachments are believed to be free of any virus no responsibility is accepted by Autoscribe Ltd for any
loss or damage arising in any way from the receipt or use of this email or attachments.
*********************************************************************************************************************************

 

From: Walden H. Leverich [mailto:WaldenL <at> TechSoftInc.com]
Sent: 06 April 2009 15:16
To: Log4NET User
Subject: RE: When will the next version be released?

 

I forget, is the "official" release strongly named? And if so, did those other components reference it by strong name? I tend to hate strong naming! It's a logging component, if there's an upgrade I should be able to use it, why should I be tied to an older version just because you built against the older version?

 

-Walden

 

--

Walden H Leverich III

Tech Software

(516) 627-3800 x3051

WaldenL <at> TechSoftInc.com

http://www.TechSoftInc.com

 

Quiquid latine dictum sit altum viditur.

(Whatever is said in Latin seems profound.)

 

From: Peter Drier [mailto:peter.drier <at> gmail.com]
Sent: Saturday, April 04, 2009 2:24 PM
To: Log4NET User
Subject: Re: When will the next version be released?

 

So the last time log4net upgraded from .9 to .10, that process was actually somewhat painful for me..  as you note a lot of components rely on log4net .10..  And dealing with different versions of log4net simultaneously wasn't fun (we weren't allowed to gac it for various reasons, nor do you want 2 copies of log4net loaded into a single process anyways). 

Now, given that most to all of the updates/bug fixes are in the appenders, it may make sense to split log4net into 2 packages..  one that's the core log4net bits + appender skeleton + interfaces..  and one that's the bundled appenders.. 

That way, the third party packages (nunit, nhibernate, ...) can depend on the core log4net bits without having to upgrade every time Nicko does a appender bug fix.. 

This may even be enough to warrant a 1.3 ?

Nicko?

-Peter

On Thu, Apr 2, 2009 at 11:35 AM, Yaojian <skyaoj <at> gmail.com> wrote:

I am totally agree with the reliable of log4net.

I just want a bug-fix version, espically the UdpAppender issue https://issues.apache.org/jira/browse/LOG4NET-112

As lots of third-party components (for example, NHibernate) rely on log4net's public GA 1.2.10, I have to rebuild all these third-party components with my private build from the log4net svn :-(

 

On Thu, Apr 2, 2009 at 11:20 PM, Peter Drier <peter.drier <at> gmail.com> wrote:

Maybe when someone comes up with a legit feature need that it doesn't already cover?

Seriously though, I've been using 1.2.10 for years now and log4net has been the most reliable 3rd party package I've used across many applications. The only things I've needed that it couldn't do fit easily in the appender and plugin frameworks.

Don't fix what isn't broken!

Peter

On Apr 2, 2009, at 10:33 AM, Yaojian <skyaoj <at> gmail.com> wrote:

Hi

anyone know that?

 

 


Gmane