TraceTarget no longer blocks on error messages#3
Merged
1 commit merged intomasterfrom Sep 19, 2012
unknown repository
Merged
Conversation
When using TraceTarget to log error events, it would cause the application to block because of the default behaviour of Trace.Fail (described on the MSDN page). Changed to only use Trace.Fail when receiving an event Fatal or above. Also started to use TraceInformation, TraceWarning and TraceError for the correspondig log levels.
ghost
pushed a commit
that referenced
this pull request
Sep 19, 2012
TraceTarget no longer blocks on error messages. Fixes Codeplex bug 2599
|
When are you planning to publish the fixed items as Nuget package? |
UgurAldanmaz
pushed a commit
that referenced
this pull request
Dec 13, 2015
This pull request was closed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When using TraceTarget to log error events, it would cause the application
to block because of the default behaviour of Trace.Fail (described on the
MSDN page).
Changed to only use Trace.Fail when receiving an event Fatal or above.
Also started to use TraceInformation, TraceWarning and TraceError for the
correspondig log levels.