Although you solved you problem by parsing the exception I'll give you an alternative to do such a job.
You can implement a Renderer (a class which implements the interface
IObjectRenderer) for your exception and put the information you want about the exception. Then, you just have to add a <renderer renderingClass="MyClass.MyRenderer" renderedClass="Exception" /> element to the config file.
regards,
Fred
On Wed, Jul 30, 2008 at 12:25 PM, Hsalim
<hsalim@...> wrote:
Yann,
Thanks for the reply.
I guess I could do
catch (Exception ex)
{
if (log.IsWarnEnabled)
log.Warn(string.Format("Error blah {0}:{1}\n{2}\n{3}", key1, key2,
ex.Message, ex.InnerException));
}
Instead, I would prefer to pass in the exception
log.Warn(string.Format("error blah {0}:{1}", key1,key2 ), ex);
I want to use an exception layout to selectively log parts of the exception.
I'll use a text file appender to log the stack trace and every gory detail
and use an SMTP appender to semd me just the exception message and
InnerException. And I can change what gets logged at any time.
I see from the SDK that there is an exception layout but I just cant figure
out what I need to do.
regards
Habib
--
View this message in context: http://www.nabble.com/Excluding-stack-trace-from-Layout-tp18734170p18737810.html
Sent from the Log4net - Users mailing list archive at Nabble.com.
