-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Workaround for apps dependent on DTC in respect to porting to NetCore 3.0 #589
Comments
We are also wanting to port from .NET Framework to .NET Core and have ran into the fact that DTC is not supported with TransactionScope which feels like a deal breaker in terms of us being able to port to .NET Core. Our specific use cases are:
Since distributed transactions are not currently supported right now in .NET Core, what is the recommendation from Microsoft as a workaround? |
We are investigating the feasibility of bringing this feature to Core, please continue to track dotnet/corefx#13532 , that issue will be getting moved to this repo shortly. |
Issue moved to dotnet/runtime #715 |
All,
If your netcore app wraps multiple connections in a transactionscope, you will get a runtime error:
"This platform does not support distributed transactions."
I am wondering what's the best workaround for web apps that are being ported to netcore3, which used DTC. Is it to refactor to use UnitOfWork pattern?
I don't want to manage connections in my business layer, which is what TransactionScope helped with.
Thanks!
Related:
Open Issue: https://github.com/dotnet/corefx/issues/13532
Stack Overflow: https://stackoverflow.com/questions/56328832/transactionscope-throwing-exception-this-platform-does-not-support-distributed-t
The text was updated successfully, but these errors were encountered: