Avoid assembly lookup on static class initialization #283
Conversation
This file contains 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
…bly lookup on static class initialization)
Codecov Report
@@ Coverage Diff @@
## master #283 +/- ##
=====================================
Coverage 57% 57%
=====================================
Files 31 31
Lines 407 407
Branches 92 92
=====================================
Hits 233 233
Misses 138 138
Partials 36 36Continue to review full report at Codecov.
|
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Guessing that Assembly lookup during startup is not welcome. Trying to resolve #281
Another example of assembly lookup during startup is failing for ServiceFabric: quartznet/quartznet#619 (Though here the bug is in
SerilogLogProvider.IsLoggerAvailable)