Controller.Dispose Method

 

Releases all resources that are used by the current instance of the Controller class.

Namespace:   System.Web.Mvc
Assembly:  System.Web.Mvc (in System.Web.Mvc.dll)

NameDescription
System_CAPS_pubmethodDispose()

Releases all resources that are used by the current instance of the Controller class.

System_CAPS_protmethodDispose(Boolean)

Releases unmanaged resources and optionally releases managed resources.

Return to top

Controller.Dispose Method ()

Releases all resources that are used by the current instance of the Controller class.

public void Dispose()

The ASP.NET MVC framework calls Dispose when the request has completed processing. Developers typically do not have to call Dispose. The Dispose(Boolean) method overload is the preferred method to override. If you derive a class from Controller and the derived class uses unmanaged memory, managed operating-system resources (such as files), or COM objects, you should implement Dispose to clean up these resources. You should also call the Dispose method of the base class. The Dispose method leaves the Controller instance in an unusable state. After you call Dispose, you must release all references to the Controller instance so that the garbage collector can reclaim the memory that the Controller instance was occupying.

For more information, see Cleaning Up Unmanaged Resources and Implementing a Dispose Method.

Return to top

Controller.Dispose Method (Boolean)

Releases unmanaged resources and optionally releases managed resources.

protected virtual void Dispose(
	bool disposing
)

Parameters

disposing
Type: System.Boolean

true to release both managed and unmanaged resources; false to release only unmanaged resources.

The ASP.NET MVC framework calls Dispose when the request has completed processing. Developers typically do not have to call Dispose. If you derive a class from Controller and the derived class uses unmanaged memory, managed operating-system resources (such as files), or COM objects, you should implement Dispose to clean up these resources. You should also call the Dispose method of the base class. The Dispose method leaves the Controller instance in an unusable state. After you call Dispose, you must release all references to the Controller instance so that the garbage collector can reclaim the memory that the Controller instance was occupying.

For more information, see Cleaning Up Unmanaged Resources and Implementing a Dispose Method.

Return to top
Show: