Assembly: System.Management.Automation (in System.Management.Automation.dll)
Although it is possible to derive from this class, in most cases, developers should derive from one of the following classes to implement their own providers:ItemCmdletProvider
Serves as a base class for providers that expose an item as a Windows PowerShell path.ContainerCmdletProvider
Serves as a base class for providers that perform operations such as rename, remove, copy, and check existence against items that are appropriate for containers.NavigationCmdletProvider
Serves as the base class for providers that perform operations against items in a multilevel data store.
For more information about providers, see Windows PowerShell Providers.
Windows PowerShell provides a template file that you can use as a starting point for writing your own providers. The TemplateProvider.cs file is available on the Windows SDK, and it defines the basic functionality required to create any type of provider. Copy this file to create a new provider, and remove any functionality that you do not need. For more information about other provider implementations, see Designing Your Windows PowerShell Provider.
Target PlatformsWindows 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 Preview
Send comments about this topic to Microsoft.