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
12 matches
Mail list logo
