So are you saying you feel it is ok to use log4net directly to configure
this in the installer before the facility is added?
Thanks for looking at this btw, much appreciated.
On Thursday, May 9, 2013 6:51:11 PM UTC-5, Krzysztof Koźmic wrote:
OK, so I had a stab at it this morning.
It
I imagine you'd do it in the application root not in the installer, no?
--
Krzysztof Kozmic
On Wednesday, 15 May 2013 at 11:57 PM, OutOfTouch wrote:
So are you saying you feel it is ok to use log4net directly to configure this
in the installer before the facility is added?
Thanks for
Well right now I am convinced that I can't add an appender file path at
runtime without using Log4net directly which to me makes it seem a little
pointless to use Castle's Logging Facility for the abstraction since I have
to use Log4net directly to do this. I still like castle, I am just
I'm fairly certain it should be working.
I'll have a look into that over the weekend, unless somebody else wants to do
it
--
Krzysztof Kozmic
On Thursday, 9 May 2013 at 11:55 PM, OutOfTouch wrote:
Well right now I am convinced that I can't add an appender file path at
runtime
OK, so I had a stab at it this morning.
It seems you're right. In this context the global property has to be set before
configure is called (which by default happens when you add the facility.
You never said why you're doing it that way and at which point in your
applications lifecycle you
Hi Krzysztof,
I know you are a busy guy, I tried what you suggested in your answer to my
question on stack over
flow
http://stackoverflow.com/questions/16343145/how-to-use-extendedlog4netlogger-cs-to-set-logfile-path-for-appender-at-runtime
the problem is the log file is never created and I
does it work if you use log4net directly?
--
Krzysztof Kozmic
On Wednesday, 8 May 2013 at 11:34 PM, OutOfTouch wrote:
Hi Krzysztof,
I know you are a busy guy, I tried what you suggested in your answer to my
question on stack over flow
Yes it does work if I just use the config file and set the path there.
On Wednesday, May 8, 2013 4:09:19 PM UTC-5, Krzysztof Koźmic wrote:
does it work if you use log4net directly?
--
Krzysztof Kozmic
On Wednesday, 8 May 2013 at 11:34 PM, OutOfTouch wrote:
Hi Krzysztof,
I know you are
I am wondering if it is not working because it reads the config file before
setting the global variable?
On Wednesday, May 8, 2013 4:09:19 PM UTC-5, Krzysztof Koźmic wrote:
does it work if you use log4net directly?
--
Krzysztof Kozmic
On Wednesday, 8 May 2013 at 11:34 PM, OutOfTouch
dunno,
try it with just l4n first in exactly the same order and see if it works or not
--
Krzysztof Kozmic
On Thursday, 9 May 2013 at 7:31 AM, OutOfTouch wrote:
I am wondering if it is not working because it reads the config file before
setting the global variable?
On Wednesday,
With log4net and the normal ILogger it worked when doing this:
log4net.GlobalContext.Properties[propertyName] = propertyValue;
log4net.Appender.RollingFileAppender rFileAppender = new
log4net.Appender.RollingFileAppender();
log4net.Config.BasicConfigurator.Configure(rFileAppender);
But I
with Windsor you rely on the config file. Can you make it work with l4n and
config file?
--
Krzysztof Kozmic
On Thursday, 9 May 2013 at 7:57 AM, OutOfTouch wrote:
With log4net and the normal ILogger it worked when doing this:
log4net.GlobalContext.Properties[propertyName] =
I don't understand your question I had it working by using the Windsor
ILogger(Not the extended logger) and using the code I posted above.
On Wednesday, May 8, 2013 4:58:43 PM UTC-5, Krzysztof Koźmic wrote:
with Windsor you rely on the config file. Can you make it work with l4n
and config
I should add though that the code I posted that worked with the windsor
ILogger was ran before actually adding my logger installer to the
container.
On Wednesday, May 8, 2013 4:58:43 PM UTC-5, Krzysztof Koźmic wrote:
with Windsor you rely on the config file. Can you make it work with l4n
Even with Flips code in this thread he added the global property before
adding the logger to the container
On Wednesday, May 8, 2013 4:58:43 PM UTC-5, Krzysztof Koźmic wrote:
with Windsor you rely on the config file. Can you make it work with l4n
and config file?
--
Krzysztof Kozmic
On
Ok so you're saying what used to work with normal logger stopped working
when you switched to extended?
Krzysztof Kozmic
sent from my phone
On 9 May 2013 08:16, OutOfTouch outoftouch6...@gmail.com wrote:
I should add though that the code I posted that worked with the windsor
ILogger was ran
No that is not what I am saying, what I am saying is if I wanted to use
log4net directly to add thehe global property the code I I just posted
works when using the windsor ILogger, if you look at Filips code he also
added the global property using log4net directly and did it before adding
the
I think I found where these tests are at but I am still confused as to how
to do the registration. I am looking at ExtendedLog4NetFacilityTestCase.cs
On Thursday, May 2, 2013 5:01:41 PM UTC-5, Krzysztof Koźmic wrote:
there should be some tests that demonstrate that, no?
--
Krzysztof Kozmic
Do you or anyone else know how I can do this using the
ExtendedLog4NetLogger.cs?
On Tuesday, October 27, 2009 10:39:05 AM UTC-5, Filip Kinsky wrote:
I just solve the problem fortunately. The only mistake I made is in
the log4net.config file - the definition of file name parameter of
there should be some tests that demonstrate that, no?
--
Krzysztof Kozmic
On Friday, 3 May 2013 at 2:20 AM, OutOfTouch wrote:
Do you or anyone else know how I can do this using the
ExtendedLog4NetLogger.cs?
On Tuesday, October 27, 2009 10:39:05 AM UTC-5, Filip Kinsky wrote:
I
Hi, I'd don't remember it clearly, but I think it was just about
correct RollingFileAppender
configuration. Did you try to use the configuration element I mentioned: file
type=log4net.Util.PatternString value=%property{LogName} / ?
On Mon, Apr 29, 2013 at 5:41 PM, OutOfTouch
Hi Filip,
I know this is an old thread but I need to do the same thing that you were
trying to do here and I can't not find any examples of using the E
xtendedLog4netLogger .cs class
Did you use this class to do this? Even if you didn't do you have any
examples of using this class? All the
Not Yet, I am wondering how you set this value using Castle?
On Monday, April 29, 2013 11:05:33 AM UTC-5, Filip Kinsky wrote:
Hi, I'd don't remember it clearly, but I think it was just about correct
RollingFileAppender
configuration. Did you try to use the configuration element I mentioned:
The Reason I ask is I don't like the idea of having to use log4net directly
in my windsor installer to do this
log4net.GlobalContext.Properties[LogName] = logName;
On Monday, April 29, 2013 1:32:46 PM UTC-5, OutOfTouch wrote:
Not Yet, I am wondering how you set this value using Castle?
On
strange thing is that this works when using LogName as a parameter in
log message pattern, but not for file name so I guess it's rather
log4net related problem and nothing windsor-specific...
log4net.GlobalContext.Properties[LogName] = logName;
container.AddFacility(logging, new LoggingFacility
What you should do is create your own appender derived from RollingFileAppender
Cheers John
On 27/10/2009, at 11:00 PM, Filip Kinsky fi...@filovo.net wrote:
RollingFileAppender
__
Get more done like never
I just solve the problem fortunately. The only mistake I made is in
the log4net.config file - the definition of file name parameter of
appender should not be done using param name=File ..., but it
should look like this:
file type=log4net.Util.PatternString value=%property{LogName} /
It just
27 matches
Mail list logo
