IDisposable.Dispose IDisposable.Dispose IDisposable.Dispose IDisposable.Dispose Method

定義

アンマネージ リソースの解放またはリセットに関連付けられているアプリケーション定義のタスクを実行します。Performs application-defined tasks associated with freeing, releasing, or resetting unmanaged resources.

public:
 void Dispose();
public void Dispose ();
abstract member Dispose : unit -> unit
Public Sub Dispose ()

次の例は、実装する方法を示しています、Disposeメソッド。The following example shows how you can implement the Dispose method.

#using <System.dll>
#using <System.Windows.Forms.dll>

using namespace System;
using namespace System::ComponentModel;
using namespace System::Windows::Forms;

// The following example demonstrates how to create a class that 
// implements the IDisposable interface and the IDisposable.Dispose
// method with finalization to clean up unmanaged resources. 
//
public ref class MyResource: public IDisposable
{
private:

   // Pointer to an external unmanaged resource.
   IntPtr handle;

   // A managed resource this class uses.
   Component^ component;

   // Track whether Dispose has been called.
   bool disposed;

public:
   // The class constructor.
   MyResource( IntPtr handle, Component^ component )
   {
      this->handle = handle;
      this->component = component;
      disposed = false;
   }

   // This method is called if the user explicitly disposes of the
   // object (by calling the Dispose method in other managed languages, 
   // or the destructor in C++). The compiler emits as a call to 
   // GC::SuppressFinalize( this ) for you, so there is no need to 
   // call it here.
   ~MyResource() 
   {
      // Dispose of managed resources.
      component->~Component();

      // Call C++ finalizer to clean up unmanaged resources.
      this->!MyResource();

      // Mark the class as disposed. This flag allows you to throw an
      // exception if a disposed object is accessed.
      disposed = true;
   }

   // Use interop to call the method necessary to clean up the 
   // unmanaged resource.
   //
   [System::Runtime::InteropServices::DllImport("Kernel32")]
   static Boolean CloseHandle( IntPtr handle );

   // The C++ finalizer destructor ensures that unmanaged resources get
   // released if the user releases the object without explicitly 
   // disposing of it.
   //
   !MyResource()
   {      
      // Call the appropriate methods to clean up unmanaged 
      // resources here. If disposing is false when Dispose(bool,
      // disposing) is called, only the following code is executed.
      CloseHandle( handle );
      handle = IntPtr::Zero;
   }

};

void main()
{
   // Insert code here to create and use the MyResource object.
   MyResource^ mr = gcnew MyResource((IntPtr) 42, (Component^) gcnew Button());
   mr->~MyResource();
}
using System;
using System.ComponentModel;

// The following example demonstrates how to create
// a resource class that implements the IDisposable interface
// and the IDisposable.Dispose method.

public class DisposeExample
{
    // A base class that implements IDisposable.
    // By implementing IDisposable, you are announcing that
    // instances of this type allocate scarce resources.
    public class MyResource: IDisposable
    {
        // Pointer to an external unmanaged resource.
        private IntPtr handle;
        // Other managed resource this class uses.
        private Component component = new Component();
        // Track whether Dispose has been called.
        private bool disposed = false;

        // The class constructor.
        public MyResource(IntPtr handle)
        {
            this.handle = handle;
        }

        // Implement IDisposable.
        // Do not make this method virtual.
        // A derived class should not be able to override this method.
        public void Dispose()
        {
            Dispose(true);
            // This object will be cleaned up by the Dispose method.
            // Therefore, you should call GC.SupressFinalize to
            // take this object off the finalization queue
            // and prevent finalization code for this object
            // from executing a second time.
            GC.SuppressFinalize(this);
        }

        // Dispose(bool disposing) executes in two distinct scenarios.
        // If disposing equals true, the method has been called directly
        // or indirectly by a user's code. Managed and unmanaged resources
        // can be disposed.
        // If disposing equals false, the method has been called by the
        // runtime from inside the finalizer and you should not reference
        // other objects. Only unmanaged resources can be disposed.
        protected virtual void Dispose(bool disposing)
        {
            // Check to see if Dispose has already been called.
            if(!this.disposed)
            {
                // If disposing equals true, dispose all managed
                // and unmanaged resources.
                if(disposing)
                {
                    // Dispose managed resources.
                    component.Dispose();
                }

                // Call the appropriate methods to clean up
                // unmanaged resources here.
                // If disposing is false,
                // only the following code is executed.
                CloseHandle(handle);
                handle = IntPtr.Zero;

                // Note disposing has been done.
                disposed = true;

            }
        }

        // Use interop to call the method necessary
        // to clean up the unmanaged resource.
        [System.Runtime.InteropServices.DllImport("Kernel32")]
        private extern static Boolean CloseHandle(IntPtr handle);

        // Use C# destructor syntax for finalization code.
        // This destructor will run only if the Dispose method
        // does not get called.
        // It gives your base class the opportunity to finalize.
        // Do not provide destructors in types derived from this class.
        ~MyResource()
        {
            // Do not re-create Dispose clean-up code here.
            // Calling Dispose(false) is optimal in terms of
            // readability and maintainability.
            Dispose(false);
        }
    }
    public static void Main()
    {
        // Insert code here to create
        // and use the MyResource object.
    }
}
Imports System
Imports System.ComponentModel

' The following example demonstrates how to create
' a resource class that implements the IDisposable interface
' and the IDisposable.Dispose method.
Public Class DisposeExample

   ' A class that implements IDisposable.
   ' By implementing IDisposable, you are announcing that 
   ' instances of this type allocate scarce resources.
   Public Class MyResource
      Implements IDisposable
      ' Pointer to an external unmanaged resource.
      Private handle As IntPtr
      ' Other managed resource this class uses.
      Private component As component
      ' Track whether Dispose has been called.
      Private disposed As Boolean = False

      ' The class constructor.
      Public Sub New(ByVal handle As IntPtr)
         Me.handle = handle
      End Sub

      ' Implement IDisposable.
      ' Do not make this method virtual.
      ' A derived class should not be able to override this method.
      Public Overloads Sub Dispose() Implements IDisposable.Dispose
         Dispose(True)
         ' This object will be cleaned up by the Dispose method.
         ' Therefore, you should call GC.SupressFinalize to
         ' take this object off the finalization queue 
         ' and prevent finalization code for this object
         ' from executing a second time.
         GC.SuppressFinalize(Me)
      End Sub

      ' Dispose(bool disposing) executes in two distinct scenarios.
      ' If disposing equals true, the method has been called directly
      ' or indirectly by a user's code. Managed and unmanaged resources
      ' can be disposed.
      ' If disposing equals false, the method has been called by the 
      ' runtime from inside the finalizer and you should not reference 
      ' other objects. Only unmanaged resources can be disposed.
      Protected Overridable Overloads Sub Dispose(ByVal disposing As Boolean)
         ' Check to see if Dispose has already been called.
         If Not Me.disposed Then
            ' If disposing equals true, dispose all managed 
            ' and unmanaged resources.
            If disposing Then
               ' Dispose managed resources.
               component.Dispose()
            End If

            ' Call the appropriate methods to clean up 
            ' unmanaged resources here.
            ' If disposing is false, 
            ' only the following code is executed.
            CloseHandle(handle)
            handle = IntPtr.Zero

            ' Note disposing has been done.
            disposed = True

         End If
      End Sub

      ' Use interop to call the method necessary  
      ' to clean up the unmanaged resource.
      <System.Runtime.InteropServices.DllImport("Kernel32")> _
      Private Shared Function CloseHandle(ByVal handle As IntPtr) As [Boolean]
      End Function

      ' This finalizer will run only if the Dispose method 
      ' does not get called.
      ' It gives your base class the opportunity to finalize.
      ' Do not provide finalize methods in types derived from this class.
      Protected Overrides Sub Finalize()
         ' Do not re-create Dispose clean-up code here.
         ' Calling Dispose(false) is optimal in terms of
         ' readability and maintainability.
         Dispose(False)
         MyBase.Finalize()
      End Sub
   End Class

   Public Shared Sub Main()
      ' Insert code here to create
      ' and use the MyResource object.
   End Sub

End Class

注釈

閉じるか、ファイル、ストリーム、およびこのインターフェイスを実装するクラスのインスタンスによって保持されているハンドルなどのアンマネージ リソースを解放するには、このメソッドを使用します。Use this method to close or release unmanaged resources such as files, streams, and handles held by an instance of the class that implements this interface. 慣例により、このメソッドはオブジェクトによって保持されているリソースを解放することに関連付けられているすべてのタスクの使用や、再利用するためのオブジェクトを準備します。By convention, this method is used for all tasks associated with freeing resources held by an object, or preparing an object for reuse.

警告

実装するクラスを使用している場合、IDisposableインターフェイスを呼び出す必要があります、Dispose実装クラスの使用が終了するときにします。If you are using a class that implements the IDisposable interface, you should call its Dispose implementation when you are finished using the class. 詳細については、「IDisposable を実装するオブジェクトを使用して」」セクションを参照してください、IDisposableトピック。For more information, see the "Using an object that implements IDisposable" section in the IDisposable topic.

このメソッドを実装する場合は、リソースが解放呼び出し包含階層を伝達することで保持されているすべてを確認します。When implementing this method, ensure that all held resources are freed by propagating the call through the containment hierarchy. たとえば、オブジェクト B オブジェクト C、A、の割り当てし、オブジェクト A がオブジェクト B を割り当てDispose実装を呼び出す必要がありますDisposeb でを呼び出す必要があります順番DisposecFor example, if an object A allocates an object B, and object B allocates an object C, then A's Dispose implementation must call Dispose on B, which must in turn call Dispose on C.

重要

C++ コンパイラは、リソースの確定的な破棄をサポートし、直接実装ではできません、Disposeメソッド。The C++ compiler supports deterministic disposal of resources and does not allow direct implementation of the Dispose method.

オブジェクトが呼び出す必要がありますも、Dispose基底クラスを実装する場合は、基底クラスのメソッドIDisposableします。An object must also call the Dispose method of its base class if the base class implements IDisposable. 実装の詳細についてはIDisposable基底クラスとそのサブクラスでは、「IDisposable と継承階層」セクションを参照して、IDisposableトピック。For more information about implementing IDisposable on a base class and its subclasses, see the "IDisposable and the inheritance hierarchy" section in the IDisposable topic.

オブジェクトの場合、Disposeメソッドを複数回呼び出すと、オブジェクトは、1 つ目の後のすべての呼び出しを無視する必要があります。If an object's Dispose method is called more than once, the object must ignore all calls after the first one. 場合、オブジェクトが例外をスローする必要があります、Disposeメソッドは複数回呼び出されました。The object must not throw an exception if its Dispose method is called multiple times. インスタンス メソッド以外のDisposeスローすることができます、ObjectDisposedExceptionリソースは既に破棄されています。Instance methods other than Dispose can throw an ObjectDisposedException when resources are already disposed.

ユーザーが期待を割り当て済みの状態と解放された状態を示すために、特定の規則を使用するリソースの種類。Users might expect a resource type to use a particular convention to denote an allocated state versus a freed state. この例では、従来から開くと考えるまたは閉じられたストリーム クラスです。An example of this is stream classes, which are traditionally thought of as open or closed. など、カスタマイズされた名前のパブリック メソッドを実装するために、このような規則を持つクラスの実装者を選択Close、その呼び出し、Disposeメソッド。The implementer of a class that has such a convention might choose to implement a public method with a customized name, such as Close, that calls the Dispose method.

Disposeメソッドを明示的に呼び出す必要があります、常に、アンマネージ リソースを許可しない危険性があるオブジェクトのコンシューマーは、呼び出しが失敗したため、解放、Disposeメソッド。Because the Dispose method must be called explicitly, there is always a danger that the unmanaged resources will not be released, because the consumer of an object fails to call its Dispose method. これを回避する 2 つの方法はあります。There are two ways to avoid this:

  • 派生したオブジェクトでマネージ リソースをラップSystem.Runtime.InteropServices.SafeHandleします。Wrap the managed resource in an object derived from System.Runtime.InteropServices.SafeHandle. Dispose実装し、Disposeのメソッド、System.Runtime.InteropServices.SafeHandleインスタンス。Your Dispose implementation then calls the Dispose method of the System.Runtime.InteropServices.SafeHandle instances. 詳細については、「SafeHandle 代わりに、」セクションを参照して、Object.Finalizeトピック。For more information, see "The SafeHandle alternative" section in the Object.Finalize topic.

  • リソースを解放するファイナライザーを実装するときにDisposeは呼び出されません。Implement a finalizer to free resources when Dispose is not called. 既定では、ガベージ コレクターによって、そのメモリを解放する前に、オブジェクトのファイナライザーが自動的に呼び出します。By default, the garbage collector automatically calls an object's finalizer before reclaiming its memory. ただし場合、Disposeメソッドがされた呼び出されると、必要はありません通常のガベージ コレクターが破棄されたオブジェクトのファイナライザーを呼び出します。However, if the Dispose method has been called, it is typically unnecessary for the garbage collector to call the disposed object's finalizer. 自動終了処理を防ぐためにDispose実装を呼び出すことができます、GC.SuppressFinalizeメソッド。To prevent automatic finalization, Dispose implementations can call the GC.SuppressFinalize method.

などの非管理対象のリソースにアクセスするオブジェクトを使用すると、StreamWriterを使用して、インスタンスを作成するをお勧め、usingステートメント。When you use an object that accesses unmanaged resources, such as a StreamWriter, a good practice is to create the instance with a using statement. usingストリームと呼び出しステートメントを自動的に閉じますDisposeそれを使用するコードが完了したときのオブジェクト。The using statement automatically closes the stream and calls Dispose on the object when the code that is using it has completed. 例については、次を参照してください。、StreamWriterクラス。For an example, see the StreamWriter class.

適用対象

こちらもご覧ください