ScriptConfigurationEntry Class
[This topic is pre-release documentation and is subject to change in future releases. Blank topics are included as placeholders.]
Represents a script for a runspace configuration.
Namespace: System.Management.Automation.Runspaces
Assembly: System.Management.Automation (in System.Management.Automation)
System.Management.Automation.Runspaces.RunspaceConfigurationEntry
System.Management.Automation.Runspaces.ScriptConfigurationEntry
Namespace: System.Management.Automation.Runspaces
Assembly: System.Management.Automation (in System.Management.Automation)
Usage
Visual Basic
Dim instance As ScriptConfigurationEntry
Syntax
Visual Basic
Public NotInheritable Class ScriptConfigurationEntry Inherits RunspaceConfigurationEntry
C#
public sealed class ScriptConfigurationEntry : RunspaceConfigurationEntry
C++
public ref class ScriptConfigurationEntry sealed : public RunspaceConfigurationEntry
J#
public final class ScriptConfigurationEntry extends RunspaceConfigurationEntry
JScript
public final class ScriptConfigurationEntry extends RunspaceConfigurationEntry
Remarks
When configuring a runspace, a collection of ScriptConfigurationEntry objects is used to specify the scripts that are available in the runspace. The available scripts are specified by the Scripts property of the RunspaceConfiguration class.
Developers should not derive from this class.
Inheritance Hierarchy
System.Object
System.Management.Automation.Runspaces.RunspaceConfigurationEntry
System.Management.Automation.Runspaces.ScriptConfigurationEntry
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.