Should UnitOfWork implement IDisposable in EF Core？

Question

I have read a Q&A written 9 years ago, here is the link: entity framework - Unit of Work, Repositories and IDisposable - Stack Overflow

which showed it should implement IDisposable. But other videos posted on YouTube don't. Should it implement IDisposable interface now?

How can it roll back when there is no transaction that the entities have a foreign key association?

public class Employee
{
    public long Id { get; set; }
    public string Name { get; set; }
    public long DepartmentId { get; set; }
}

public class Department
{
    public long Id { get; set; }
    public string Name { get; set; }
}

public void AddDepartmentAndEmployees()
{
    var department = new Department { Name = "Dev" };

    var employees = new List<Employee> 
    { 
       new Employee { Name = "Jack" },
       new Employee { Name = "Tim" },
    }

    _departmentRepository.Add(department);
    _departmentRepository.SaveChange();

    employees.All(e => e.DepartmentId = department.Id );
    // if there throw a unknown exception
    // and how can i roll back?
    _employeeRespository.AddRange(employees);
    _departmentRepository.SaveChange();
}

Solve the above two problems.

Sorry about my poor English, but I have try my best.

score 1 · Accepted Answer · answered Dec 18 '22 at 12:08

1

this may help you Transactions in unit of work design pattern

It's a best practice to have the UnitOfWork being disposable according to Microsoft article about UnitOfWork Design Pattern

you can use TransactionScope to create transactions and commit or roll it back if you have any problem

answered Dec 18 '22 at 12:08

Montero_Dev

34
1

You solved a problem that has been plaguing me for a long time! @Montero_Dev – Vincent Dec 18 '22 at 14:39
Is there another way to guarantee transactions using repository mode？@Montero_Dev – Vincent Dec 18 '22 at 14:43

Should UnitOfWork implement IDisposable in EF Core？

1 Answers1