Scribd Logo
Upload

Welcome to Scribd!

  • Final Vs Despose

    Uploaded by

    dabcxyz1
    7 views1 page
    The Finalize() method deallocates memory for an object but the garbage collector determines when to call it. The Dispose() method allows explicitly deallocating an object's memory as soon as it is no longer needed. For COM objects in .NET, which use unmanaged code, the Marshal.ReleaseComObject() method must be used to deallocate memory instead of relying on the garbage collector.

    Original Description:

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    DOC, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    The Finalize() method deallocates memory for an object but the garbage collector determines when to call it. The Dispose() method allows explicitly deallocating an object's memory as soon as it is no longer needed. For COM objects in .NET, which use unmanaged code, the Marshal.ReleaseComObject() method must be used to deallocate memory instead of relying on the garbage collector.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOC, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as doc, pdf, or txt
    7 views1 page

    Final Vs Despose

    Uploaded by

    dabcxyz1
    The Finalize() method deallocates memory for an object but the garbage collector determines when to call it. The Dispose() method allows explicitly deallocating an object's memory as soon as it is no longer needed. For COM objects in .NET, which use unmanaged code, the Marshal.ReleaseComObject() method must be used to deallocate memory instead of relying on the garbage collector.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOC, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as doc, pdf, or txt
    of 1

    What is the difference between Dispose and Finalize method ?

    Finalize() method will be called by the runtime. i.e, Garbage collector will take the
    responsiblity to deallocate the memory for the specific object. But the problem is we can
    not assume when it will be deallocated. For that, .NET framework supports Dispose(), by
    using this when ever you think, the object no longer needed, as soon as possible you have
    to specify objname.dispose(). in u r code.
    One more question may be raised in this topic, how to destroy the object of com
    component in u r .NET application. because CLR does not take the responsiblity to
    deallocate the objects for unmanaged code. To do this, System.Runtime.InteropServices
    namespace provides one class named Marshal.ReleaseComObject(object name)
    By using this we can deallocate the memory for com componet in .NEt application.

    You might also like