Looks like you are running an app with limited trust. See code access
security in the .net docs.
Cheers
Nicko
> -Original Message-
> From: Drew, Stephen [mailto:[EMAIL PROTECTED]
> Sent: 12 May 2006 11:24
> To: log4net-user@logging.apache.org
> Subject: Permissioning
>
> Hello,
>
> I
The appenders that derive from AppenderSkeleton are thread safe for
multithearded operation when used withing the log4net framework.
Cheers,
Nicko
> -Original Message-
> From: Bill Sorensen [mailto:[EMAIL PROTECTED]
> Sent: 12 May 2006 21:07
> To: log4net-user@logging.apache.org
> Subjec
You can implement a filter in your own assembly and reference it in the
configuration file. This should mean that you can make a filter that suites
your requirements.
Cheers,
Nicko
> -Original Message-
> From: Marco von Frieling [mailto:[EMAIL PROTECTED]
> Sent: 17 May 2006 12:35
> To
If you want to keep the db appender separate from the config file then
you will need to create and attach the db appenders programmatically.
If by "but I want to carry over the category/log level nodes" you just
mean the logger and levels then that should be fine they won't be
effected by you addi
To build the .NET Compact Framework 1.0 build you need to use the NETCF,
and NETCF_1_0 conditional compilation symbols. There is no conditional
compilation symbol for .NET Compact Framework 2.0 as we have not tested
support for this. There should be no breaking changes in the .NET
Compact Framework
If you define a custom level then you can log a message using a method
like:
private static void LogActivity(log4net.ILog log, object message,
Exception ex)
{
log4net.Core.Level activityLevel =
log.Logger.Repository.LevelMap["ACTIVITY"];
log.Logger.Log(this.GetType(), activityLevel, message,
Jon,
> 1. How would my startup screen class obtain a reference to
> the MemoryAppender such that it could read the logged events
You can create the MemoryAppender programmatically and attach it by
calling:
((log4net.Repository.Hierarchy.Hierarchy)log4net.LogManager.GetRepositor
y()).Root.AddA
