Do I need to Create A Deconstructor in C# When The Class Uses Entity Framework?

Question

May be a dumb question, but is it prudent to create a deconstructor class on a called class that is using Entity Framework under asp.net framework 4.x? Does it provide faster release of memory elements in the class concerning entity?

I know that it's recommended to create a dispose method when calling entity directly in the mvc controller class.

Here's a sample of what I mean...

    public class DepartmentServices
    {
        private MyDB _db = new MyDB();

        //Deconstructor class
        ~DepartmentServices()
        {
            _db.Dispose();
        }

Answer 1

That's the finalizer method. Your class should implement IDisposable instead. Take a look at the IDisposable pattern: https://docs.microsoft.com/en-us/dotnet/standard/garbage-collection/implementing-dispose