RunspaceConfigurationEntryCollection Generic Class
[This topic is pre-release documentation and is subject to change in future releases. Blank topics are included as placeholders.]
Represents a collection of runspace configuration entries.
Namespace: System.Management.Automation.Runspaces
Assembly: System.Management.Automation (in System.Management.Automation)
System.Management.Automation.Runspaces.RunspaceConfigurationEntryCollection
Namespace: System.Management.Automation.Runspaces
Assembly: System.Management.Automation (in System.Management.Automation)
Usage
Visual Basic
Dim instance As RunspaceConfigurationEntryCollection(Of T)
Syntax
Visual Basic
<DefaultMemberAttribute("Item")> _ Public NotInheritable Class RunspaceConfigurationEntryCollection(Of T As RunspaceConfigurationEntry) Implements IEnumerable(Of T), IEnumerable
C#
[DefaultMemberAttribute("Item")] public sealed class RunspaceConfigurationEntryCollection<T> : IEnumerable<T>, IEnumerable where T : RunspaceConfigurationEntry
C++
[DefaultMemberAttribute(L"Item")] generic<typename T> where T : RunspaceConfigurationEntry public ref class RunspaceConfigurationEntryCollection sealed : IEnumerable<T>, IEnumerable
J#
JScript
Remarks
This collection provides the following features for managing multiple runspaces.
-
Synchronization. Since multiple runspaces may be sharing the same runspace configuration, it is essential that all the configuration entry collections (for cmdlets, providers, assemblies, types, formats) are thread-safe.
-
Updating the Collection. The data for types and formats are order sensitive. It is required for supporting adding and removing from the beginning and the ending of the list.
-
Updating Components. Updated data needs to be communicated to other Windows PowerShell components. For example, if the configuration list for cmdlets and providers is updated, the change has to be communicated to the Windows PowerShell runtime.
Inheritance Hierarchy
System.Object
System.Management.Automation.Runspaces.RunspaceConfigurationEntryCollection
Thread Safety
Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.
Platforms
Target Platforms
Windows 98, Windows 2000, Windows 2000 Server, Windows CE, Windows Server 2008, Windows 98 Second Edition, Pocket PC, Smart Phone, Windows Server 2003, Windows XP Professional, Windows Vista, Windows Server 2003 R2, Windows XP, Windows 7, Windows 2008 R2, Windows Developer Preview, Windows Server Developer PreviewSee Also
Send comments about this topic to Microsoft.