Provides the base implementation for the INestedContainer interface, which enables containers to have an owning component.
Assembly: System (in System.dll)
Thetype exposes the following members.
|Add(IComponent)||Adds the specified Component to the Container. The component is unnamed. (Inherited from Container.)|
|Add(IComponent, String)||Adds the specified Component to the Container and assigns it a name. (Inherited from Container.)|
|CreateSite||Creates a site for the component within the container. (Overrides Container.CreateSite(IComponent, String).)|
|Dispose()||Releases all resources used by the Container. (Inherited from Container.)|
|Dispose(Boolean)||Releases the resources used by the nested container. (Overrides Container.Dispose(Boolean).)|
|Equals(Object)||Determines whether the specified object is equal to the current object. (Inherited from Object.)|
|Finalize||Releases unmanaged resources and performs other cleanup operations before the Container is reclaimed by garbage collection. (Inherited from Container.)|
|GetHashCode||Serves as the default hash function. (Inherited from Object.)|
|GetService||Gets the service object of the specified type, if it is available. (Overrides Container.GetService(Type).)|
|GetType||Gets the Type of the current instance. (Inherited from Object.)|
|MemberwiseClone||Creates a shallow copy of the current Object. (Inherited from Object.)|
|Remove||Removes a component from the Container. (Inherited from Container.)|
|RemoveWithoutUnsiting||Removes a component from the Container without setting Site to null. (Inherited from Container.)|
|ToString||Returns a string that represents the current object. (Inherited from Object.)|
|ValidateName||Determines whether the component name is unique for this container. (Inherited from Container.)|
The class is a simple implementation of the INestedContainer interface, which defines a component that logically contains zero or more other components and is owned by a parent component. The behavior of nested containers differs from a standard Container in a number of ways, including the following:
The site’s Name property is a qualified name that includes the owning component’s name followed by a period (.) and the child component’s name.
When the owning component is disposed, the container is disposed as well.
In addition, designers treat nested containers differently. A designer host is only interested in one container—the one associated with the host. Therefore, component add and remove events are not raised when a component is added to or removed from a nested container. However, because services flow through to the nested container, component change events are raised when a component in a nested container is changed.
This disparity in event tracking also impacts undo functionality, which is closely tied to serialization. The standard undo engine uses IReferenceService to track changes made to components. If the undo engine cannot identify a name for a component through the reference service, the engine will ignore any changes for that component. This service automatically recognizes changes to contained components only if they are exposed as public read-only properties of the same name in their owners. Otherwise, the developer must pass component change events up to the owner. For example, if a nested component’s Text property is resurfaced on its owning component as an Address property, when the Text property is changed, a property change must be programmatically made for the corresponding Address property or else that change will not be tracked by undo.
The HostProtectionAttribute attribute applied to this type or member has the following Resources property value: SharedState. The HostProtectionAttribute does not affect desktop applications (which are typically started by double-clicking an icon, typing a command, or entering a URL in a browser). For more information, see the HostProtectionAttribute class or SQL Server Programming and Host Protection Attributes.
Windows Phone 8.1, Windows Phone 8, Windows 8.1, Windows Server 2012 R2, Windows 8, Windows Server 2012, Windows 7, Windows Vista SP2, Windows Server 2008 (Server Core Role not supported), Windows Server 2008 R2 (Server Core Role supported with SP1 or later; Itanium not supported)
The .NET Framework does not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.