> > Random question, but is the "+" in "FileAppender+MinimalLock" some
> > sort of special notation? Haven't seen this before...
>
> The + notation is used to specify an inner class:
This is standard .NET behaviour as supported by the Type.GetType(String)
method.
--- Meera Rajaram <[EMAIL PROTECTED]> wrote:
> I am using version 1.2.9 of log4Net. I tried working with this and
> found
> that with Minimal Locking the FileShare mode is FileShare.Read. So
> any
> other process which even tries to open the file for writing will get
> an
> exception. But if the F
The + notation is used to specify an inner class:
public class FileAppender
{
public class MinimalLock
{
// inner class: FileAppender+MinimalLock
}
public class ExclusiveLock
{
// inner class: FileAppender+ExclusiveLock
}
}
The default behavior when there is no locki
Random question, but is the "+" in "FileAppender+MinimalLock" some
sort of special notation? Haven't seen this before...
And I wish I had realized there was an ExclusiveLock lockingtype I
could use back when I was working on an application in which we
noticed it was slowing down considerably becau
at needs to be specified that can overcome this
issue?
With rollover based on date - I think it should work fine, though I have
not tried it.
Thanks,
Meera.
-Original Message-
From: Ron Grabowski [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 19, 2006 4:15 PM
To: Log4NET Use
Starting with version 1.2.9, you can define the locking model for a
FileAppender. The default value is an ExclusiveLock which means the
FileAppender has a lock on the file for the duration of the
application. The MinimalLock opens and closes the file on each write.
Here an example showing how to se
Does the RollingFileAppender (or the FileAppender) have the ability to have
several processes all log to the same log file? This would really be helpful,
so if we have some bug that involves more than one process. I guess it would
have to open the file and prevent others from opening it in rea
