Prevent logging data from being affected by transactions. #392
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.
The sink now adds ";Enlist=False" to the connection string which avoids that logging SQL commands take part in ambient transactions (e.g. by TransactionScopes in the caller's program).
This is done by default but it can be turned off by setting the new sink option
EnlistInTransaction
to true.Additionally all tests are now also executed for .NET Framework 4.7.2. With that the test run for all target frameworks of the sink.
Original input and implementation came from @Daniel-Svensson in pr #379 but had to be changed a bit and therefore commited with this pr.