tags:

views:

13

answers:

0
Q: 

Debugger.Break() higher up the stacktrace

I wrote a simple MessageBoxAppender for log4net. I added an OK option to enable debugging (either to an attached debugger, or launching a new one).
The problem right now is that the debugger stops at the Debugger.Break() line (naturally). Is there a way to cause it to pause further up the stacktrace? Preferably at the location of the Logger call?

related questions

Setting a log file name to include current date in Log4j
log4net not logging ThreadContext
How fast is a log4net logging method (Debug, Info, etc)?
What is tracing and how should it be done?
How do I register a custom IObjectRenderer in log4net?
Log4Net "Could not find schema information" messages
Tracing versus Logging and how does log4net fit in?
Logging entry and exit of methods along with parameters automagically?
What would a Log4Net Wrapper class look like?
How do you log the machine name via log4net?
log4net Configuration Section for NUnit Test Project
How to log MethodName when wrapping Log4net?
Binsor and log4net
How do I use a common log4net reference in assemblies loaded at runtime?
How do I use a stored procedure in log4net ADONetAppender?
log4net/c# - Different layout based on the level
Log4Net/C# - Disable default logging
Delegates as parameters in VB.NET
Log4Net: set Max backup files on RollingFileAppender with rolling Date
Preferred logging infrastructure for .Net
Log4net with SyslogAppender, 1kb message limit
License guidelines for using log4net in a commercial application
What's your favorite (free) log viewer for EntLib or Log4Net?
Are there any issues with using log4net in a multi-threaded environment?
Log4Net configuring log level