We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make LogFactory.Flush() synchrone without spinning up threads. Instead provide Task FlushAsync() if wanting parallel target-flush capability.
LogFactory.Flush()
Task FlushAsync()
Allow NLog to work out-of-the-box on platforms with limited thread-support. See also #4266
The text was updated successfully, but these errors were encountered:
Could be interesting to implement IAsyncDisposable.DisposeAsync so one could do this without explicit call to LogFactory.Shutdown():
IAsyncDisposable.DisposeAsync
LogFactory.Shutdown()
await using var nlogFactory = NLog.LogManager.Setup().LogFactory;
Then one could avoid try-finally and still get parallel flushing. Sadly enough this requires NET6 and not supported by NET48 / NetStandard2.
Sorry, something went wrong.
Maybe include IAsyncDisposable for LogFactory, that can perform async-flush and async-close. Thus also resolving #3958
No branches or pull requests
Make
LogFactory.Flush()
synchrone without spinning up threads. Instead provideTask FlushAsync()
if wanting parallel target-flush capability.Allow NLog to work out-of-the-box on platforms with limited thread-support. See also #4266
The text was updated successfully, but these errors were encountered: