.NET (Core and Framework)

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>

OpenSilver[^]:

OpenSilver is a modern, plugin-free, open-source reimplementation of Silverlight. It uses WebAssembly to bring back the power of C#, XAML, and .NET to client-side Web development.

dataminers wrote:

what you mean by this sentence. --> "concurrently executing tasks"

dataminers wrote:

What does "3" do in the code block below;

await Task.Run(() =>
{
    CalculateSomething(5);
});

await Task.Run(() =>
{
    CalculateSomething(8);
});

List<int> myList = new() { 5, 8 };

myList.AsParallel().WithDegreeOfParallelism(2).ForAll(x =>
{
    CalculateSomething(x);
});

|+++++++ Tasks +++++++|
  |++++ Threads ++++|
    |+++ Cores +++|
      |+ CPUs + |

dataminers wrote:

the two code blocks below are the same

// Start both tasks in parallel:
Task t1 = Task.Run(() => CalculateSomething(5));
Task t2 = Task.Run(() => CalculateSomething(8));

// Wait for both tasks to complete:
await Task.WhenAll(t1, t2);
// Or: await t1; await t2;