Question

Here is a quote ” So, if you are working with only one object context then you have already built-in support for database transactions when using the ObjectContext.SaveChanges method.” I found here http://www.luisrocha.net/2011/08/managing-transactions-with-entity.html

So according to that, I don’t have to use TransactionScope in a code below, right?

if (isLastCallSuccess)
 {
   if (condition1) //it's clear, no transaction needed
    {
      product.Property1 = true;
      context.SaveChanges();
    }

    else if (condition2)
     {
      using (TransactionScope scope = new TransactionScope()) //do I need it?
      {
        context.DeleteObject(item);             //deleting
        context.AddObject("product", new product      //adding
                                {
                                    Id = oldObject.Id,
                                    Property1 = true
                                });
        context.SaveChanges(System.Data.Objects.SaveOptions.DetectChangesBeforeSave);
                                scope.Complete();
        context.AcceptAllChanges();

        }
      }

Answer 1

What the quote means is that a single call to SaveChanges is automatically wrapped in a transaction, so it’s atomic. You, however, are calling SaveChanges multiple times, so in order for the larger operation to be atomic you’ll need to use the transaction as you currently have it.

So yes, you need it.