.NET (Core and Framework)

Gerry Schmitz wrote:

What's the footprint? Debug versus release?

using (var context = new AppDbContext())
{
    using (var transaction = context.Database.BeginTransaction())
    {
        try
        {
            var myObjectOne = new MyObjectOne() { Name = "Book" };
            context.MyObjectOnes.Add(myObjectOne);
            context.SaveChanges();
 
            var myVal = myObjectOne.Id * 3.14;

            //Suppose an error occurs here

            var myObjectTwo = new MyObjectTwo() { Name = "Notebook", Price = 100, ReferenceId = myVal };
            context.MyObjectTwos.Add(myObjectTwo);
            context.SaveChanges();
 
            transaction.Commit();
        }
        catch (Exception ex)
        {
            transaction.Rollback();
        }
    }
}

using (var context = new AppDbContext())
{
    using (var transaction = context.Database.BeginTransaction())
    {
        try
        {
            var myObjectOne = new MyObjectOne() { Name = "Book" };
            context.MyObjectOnes.Add(myObjectOne);
            context.SaveChanges();
 
            var myVal = myObjectOne.Id * 3.14;

            //Suppose an error occurs here

            var myObjectTwo = new MyObjectTwo() { Name = "Notebook", Price = 100, ReferenceId = myVal };
            context.MyObjectTwos.Add(myObjectTwo);
            context.SaveChanges();
 
            transaction.Commit();
        }
        catch (Exception ex)
        {
            //Nothing
        }
    }
}

DbTransaction.Dispose Method (System.Data.Common) | Microsoft Learn[^]:

Dispose should rollback the transaction. However, the behavior of Dispose is provider specific, and should not replace calling Rollback.

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <system.webServer>
    <aspNetCore requestTimeout="00:02:00" .../>
  </system.webServer>
</configuration>