Thanks for the consideration. You might want to look at how EF does transactions. This appears to make this warning not valid if I read it right, since it says that EF is smart enough to take the highest transaction scope now. http://msdn.microsoft.com/en-us/data/dn456843.aspx
Also, TransactionScope isn't recommended anymore, but use the Async or Database.BeginTransaction() functions.
Thanks for the consideration. You might want to look at how EF does transactions. This appears to make this warning not valid if I read it right, since it says that EF is smart enough to take the highest transaction scope now. http://msdn.microsoft.com/en-us/data/dn456843.aspx
Also, TransactionScope isn't recommended anymore, but use the Async or Database.BeginTransaction() functions.