[jira] [Commented] (LOG4NET-178) Log4Net stops logging after appdomain recycle of aps.net2.0 application

2012-10-26 Thread Dominik Psenner (JIRA)
[ https://issues.apache.org/jira/browse/LOG4NET-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13484745#comment-13484745 ] Dominik Psenner commented on LOG4NET-178: - I am no expert on IIS web

[jira] [Created] (LOG4NET-359) Best way to get the RenderedMessage?

2012-10-26 Thread R (JIRA)
R created LOG4NET-359: - Summary: Best way to get the RenderedMessage? Key: LOG4NET-359 URL: https://issues.apache.org/jira/browse/LOG4NET-359 Project: Log4net Issue Type: Bug Environment: C#

[jira] [Updated] (LOG4NET-359) Best way to get the RenderedMessage?

2012-10-26 Thread R (JIRA)
[ https://issues.apache.org/jira/browse/LOG4NET-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] R updated LOG4NET-359: -- Description: What's the best way to get the RenderedMessage of the logger? At the moment I have a thread

[jira] [Closed] (LOG4NET-359) Best way to get the RenderedMessage?

2012-10-26 Thread Dominik Psenner (JIRA)
[ https://issues.apache.org/jira/browse/LOG4NET-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominik Psenner closed LOG4NET-359. --- Resolution: Invalid Closing as an invalid bug report. Please ask questions to the

Re: [jira] [Commented] (LOG4NET-178) Log4Net stops logging after appdomain recycle of aps.net2.0 application

2012-10-26 Thread George Chung
I know I explicitly initialize some log4net setting in Application_Startup. Let me look it up. On Thu, Oct 25, 2012 at 11:45 PM, Dominik Psenner (JIRA) j...@apache.orgwrote: [

Re: [jira] [Commented] (LOG4NET-178) Log4Net stops logging after appdomain recycle of aps.net2.0 application

2012-10-26 Thread George Chung
OK, I don't do anything special that I do in my code except set the AppName. Here's what you'll want to do. Set this in your Web.Config appSettings add key=log4net.Internal.Debug value=true/ If this setting is false, which is the default, log4net will silently swallow any exceptions