Search This Blog

Thursday, September 2, 2010

Suppressing TransactionScope enlistment of a readonly EF context?

Programmer Question

I have a scenario where I need to open multiple datacontexts which point to different databases. I am only writing to one of the databases though and reading from the others ... so technically the transaction should only be against one of the databases.



I'd like to avoid having the TransactionScope upgrade into a distributed transaction so I don't have to worry about MSDTC ... is there any way to have only one context enlist in the transaction?



Find the answer here

No comments:

Post a Comment

Related Posts with Thumbnails