-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
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
Using inside a TransactionScope throws "Specified method is not supported" #16
Comments
This can be fixed by including the System.Transactions reference and overriding the EnlistTransaction method in ReliableSqlDbConnection as below
Transactions inside a TransactionScope then function perfectly. |
Nice! Do you mind submitting a pull request along with a test?
|
Is it possible to get the NuGet package update with this fix? I've installed the package that has the transient fault handling library ILMerged into it, and I'm getting this same exception as above. |
More than happy for anyone to submit a PR |
Hi Rob
Not sure this is about a PR, but rather than a PR was created back in 2016 but the Nuget package doesn't reflect that change.
Cheers
Paul (also in Perth!)
…________________________________
From: Rob Moore [[email protected]]
Sent: Tuesday, 5 September 2017 11:27 AM
To: MRCollective/ReliableDbProvider
Cc: Paul Sheldon; Comment
Subject: Re: [MRCollective/ReliableDbProvider] Using inside a TransactionScope throws "Specified method is not supported" (#16)
More than happy for anyone to submit a PR
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#16 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AEHciRM-pgBcUfIYEp1hhNi9ScnS8UErks5sfL-YgaJpZM4Hgfg1>.
|
AH, so it was - sorry. Looks like tests are failing on that. Not sure if it's the build server or the code itself. |
When using a DataContext inside a TransactionScope a "Specified Method is not supported" exception is thrown at the System.Data.Common.DbConnection.EnlistTransaction stage.
The text was updated successfully, but these errors were encountered: