You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4net-dev@logging.apache.org by "Scott Bilas (JIRA)" <ji...@apache.org> on 2007/10/18 20:23:50 UTC
[jira] Created: (LOG4NET-124) OutputDebugString appender should use
managed ODS not native
OutputDebugString appender should use managed ODS not native
------------------------------------------------------------
Key: LOG4NET-124
URL: https://issues.apache.org/jira/browse/LOG4NET-124
Project: Log4net
Issue Type: Improvement
Components: Appenders
Affects Versions: 1.2.10
Environment: .NET 2.0, Visual Studio 2005, Windows Vista
Reporter: Scott Bilas
Priority: Minor
The built-in OutputDebugString appender uses a native call via pinvoke to call the system's OutputDebugString(). Unfortunately the VS2005 debugger only pays attention to that output when you have unmanaged debugging enabled. When working on a pure .NET project it's convenient to leave that flag off (it's off by default as well, I think) because the debugger runs faster.
Suggestion: instead of using native OutputDebugString, use System.Diagnostics.Debug.Write( RenderLoggingEvent( inLoggingEvent ) ). That way it shows up in VS2005 whether or not unmanaged debugging is enabled.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (LOG4NET-124) OutputDebugString appender should
use managed ODS not native
Posted by "Ron Grabowski (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LOG4NET-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ron Grabowski resolved LOG4NET-124.
-----------------------------------
Resolution: Invalid
Use DebugAppender if you want to record messages using System.Diagnostics.Debug.Write.
> OutputDebugString appender should use managed ODS not native
> ------------------------------------------------------------
>
> Key: LOG4NET-124
> URL: https://issues.apache.org/jira/browse/LOG4NET-124
> Project: Log4net
> Issue Type: Improvement
> Components: Appenders
> Affects Versions: 1.2.10
> Environment: .NET 2.0, Visual Studio 2005, Windows Vista
> Reporter: Scott Bilas
> Priority: Minor
>
> The built-in OutputDebugString appender uses a native call via pinvoke to call the system's OutputDebugString(). Unfortunately the VS2005 debugger only pays attention to that output when you have unmanaged debugging enabled. When working on a pure .NET project it's convenient to leave that flag off (it's off by default as well, I think) because the debugger runs faster.
> Suggestion: instead of using native OutputDebugString, use System.Diagnostics.Debug.Write( RenderLoggingEvent( inLoggingEvent ) ). That way it shows up in VS2005 whether or not unmanaged debugging is enabled.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.