Select from following answers:- Use the TransactionScopeOption with RequiresNew or continue stepping through code until the Complete method is called on a root ambient transaction.

- Replace the call to the SubmitChanges method with a call to the DataContext's Refresh method.
- Call Complete before calling the SubmitChanges method.
- All Above
If the scope is instantiated within an ambient transaction, updates will not occur until Complete is called on the root ambient transaction. Setting the method's transaction scope to RequiresNew will create a new transaction scope. The operations will not be part of an ambient transaction, and the Complete call will cause the transaction to commit.
Reversing the order of the Complete and SubmitChanges method calls will not solve the problem.
Show Correct Answer
Source: MeasureUp.Com | |
Alert Moderator