Encapsulates zero or more components.
Assembly: System (in System.dll)
Adds the specified Component to the . The component is unnamed.
Adds the specified Component to the and assigns it a name.
Releases all resources used by the.
Releases the unmanaged resources used by the, and optionally releases the managed resources.
Determines whether the specified object is equal to the current object.(Inherited from Object.)
Releases unmanaged resources and performs other cleanup operations before the Object.Finalize().)is reclaimed by garbage collection.(Overrides
Serves as the default hash function. (Inherited from Object.)
Gets the service object of the specified type, if it is available.
Removes a component from the.
Removes a component from the Site to null.without setting
Returns a string that represents the current object.(Inherited from Object.)
Determines whether the component name is unique for this container.
The IContainer interface.class is the default implementation for the
Containers are objects that encapsulate and track zero or more components. In this context, containment refers to logical containment, not visual containment. You can use components and containers in a variety of scenarios, including scenarios that are both visual and not visual.
The components in a container are tracked in a first-in, first-out list, which also defines the order of the components within the container. Added components are appended to the end of the list.
Available since 1.1
Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.