使用事务通过实体框架回滚更改

Question

I have this specific DAO that inherits methods from a generic DAO I would like to add a transaction to this code in order to roll back all changes that where made if an exception is found

        TDAO tDAO = new TDAO();
        TDAO2 tDAO2 = new TDAO2();


        //Get the DAO to delete from the database let's call them dDao and dDao2

        //Start the Transaction
        using (TransactionScope trans = new TransactionScope())
        {
            try
            {
                //Delete all SGC Associated switch
                TDAO2.Delete(dDao);

                //Delete switch
                TDAO.Delete(dDao2);

                //send notification
                base.SendChangeNotification();

                //Commit the Information Completing the Transaction
                trans.Complete();
            }
            catch (UpdateException ex)//SQL exception
            {
                //Log the error
                //Rollback the changes if there is an exception
                throw new Exception(Resources.ErrorMessages.OperationNotPermited);
            }
            catch (Exception ex) //Other exception
            {
                //Log the error
                throw new Exception(Resources.ErrorMessages.UndifenedError);
            }
        }

In Visual Studio, go to the References icon in your project. Right-click, Add Reference. Then search for System.Transactions.dll. Select it, click Ok. Then try rebuilding your project. Also make sure you have either a Using statement (C#) or Imports statement (VB) at the top, something like Using System.Transactions;

And the Changes are in the code . Thank You

Answer 1

You need to complete the transaction otherwise the transaction will be roll back. So, in your code you need to add Transaction.Complete() method, if you don't it will roll back itself.

Answer 2

Although you marked this as solved, still an answer.

If you work with Entity Framework you should not worry about transactions. The context manages the unit of work and sees to it that it is committed (or rolled back) in one transaction. Your code contains too much low-level data access stuff. Let EF do your CRUD actions.

Entity Framework allows you to be persistence ignorant in the most parts of your code. My opinion is: you don't need a DAO pattern. Worse: it only gets in the way. It first separates database actions and context instances and then you have to put it all together by transaction scopes. That means: you are managing the unit of work. Work with POCO's, not with DAO's. Let one context instance track changes and save them by one SaveChanges() call.