Remove invalid profiler method integrations #2349
Merged
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
stevejgordon
force-pushed
the
fix-profiler-integrations
branch
from
da3858d to
ad11508
Compare
stevejgordon
force-pushed
the
fix-profiler-integrations
branch
from
ad11508 to
20d49af
Compare
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.
In a default .NET Framework ASP.NET app, when adding the profiler auto-instrumentation, the profiler logs report:
On review, this is due to the instrumentation attempting to locate overloads of these methods accepting
CommandBehavior. The only library where these seem to apply isSystem.Data.SQLite.