It looks like provider 8.1.55.0 has bugs. Trial 8.4.303 works as 8.1.55.0.
This is an example of pseudo code
...
var conn = (EntityConnection)context.Connection;
conn.Open();
using (var scope = new TransactionScope()
{
// inserts successfully data to table A
// here I can see the result in table A via another connection
// run invalid sql query
scope.Complete();
}
// here I can see the result in table A via another connection
How can it be???
Please, help investigate & solve this problem.
P.S. I have found similar problem, but "Enlist" parameter in connection string did not help me...
EntityFramework + TransactionScope + rollback problem
Re: EntityFramework + TransactionScope + rollback problem
Thank you for your report. I cannot reproduce the described problem in our environment at the moment. Please send us a small test project with the corresponding DDL/DML script for reproducing.