You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This ensures the following components have the correct/consistent case
throughout the reference documentation:
Preference variable, PS environment variable, PS drive, PS provider,
PS command name, PS command argument, PS module, PS file extension,
PS host name/application, #Requires statement, parameter name,
about_* topic, member name, scope modifier, keyword, operator,
calculated property key/value, attribute, type accelerator,
type literal/name, WMI namespace/class, variable name,
special character, comment-based help keyword, product/company name,
Windows drive letter/directory, Windows/Unix environment variable
In addition, changes include fixes to incorrect terminology (e.g.,
referring to a keyword as a command) and formatting of PS syntax
elements (non-exhaustive).
Copy file name to clipboardExpand all lines: reference/docs-conceptual/developer/prog-guide/windows-powershell-sample-code.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,15 +34,15 @@ code that is contained in the Windows SDK samples.
34
34
|[StopProc01 Code Samples](./stopproc01-code-samples.md)| This is the `Stop-Process` cmdlet sample described in [Creating a Cmdlet That Modifies the System](../cmdlet/creating-a-cmdlet-that-modifies-the-system.md). |
35
35
|[StopProcessSample04 Code Samples](./stopprocesssample04-code-samples.md)| This is the `Stop-Process` cmdlet sample described in [Adding Parameter Sets to a Cmdlet](../cmdlet/adding-parameter-sets-to-a-cmdlet.md). |
36
36
|[Runspace01 Code Samples](./runspace01-code-samples.md)| These are the code samples for the runspace described in [Creating a Console Application That Runs a Specified Command](/dotnet/csharp/programming-guide/inside-a-program/hello-world-your-first-program). |
37
-
|[Runspace02 Code Samples](./runspace02-code-samples.md)| This sample uses the [System.Management.Automation.Runspaceinvoke](/dotnet/api/System.Management.Automation.RunspaceInvoke) class to execute the `Get-Process` cmdlet synchronously. |
37
+
|[Runspace02 Code Samples](./runspace02-code-samples.md)| This sample uses the [System.Management.Automation.RunspaceInvoke](/dotnet/api/System.Management.Automation.RunspaceInvoke) class to execute the `Get-Process` cmdlet synchronously. |
38
38
|[RunSpace03 Code Samples](./runspace03-code-samples.md)| These are the code samples for the runspace described in "Creating a Console Application That Runs a Specified Script". |
39
-
|[RunSpace04 Code Samples](./runspace04-code-samples.md)| This is a code sample for a runspace that uses the [System.Management.Automation.Runspaceinvoke](/dotnet/api/System.Management.Automation.RunspaceInvoke) class to execute a script that generates a terminating error. |
39
+
|[RunSpace04 Code Samples](./runspace04-code-samples.md)| This is a code sample for a runspace that uses the [System.Management.Automation.RunspaceInvoke](/dotnet/api/System.Management.Automation.RunspaceInvoke) class to execute a script that generates a terminating error. |
|[RunSpace10 Code Sample](./runspace10-code-sample.md)| This is the source code for the Runspace10 sample, which adds a cmdlet to [System.Management.Automation.Runspaces.Runspaceconfiguration](/dotnet/api/System.Management.Automation.Runspaces.RunspaceConfiguration) and then uses the modified configuration information to create the runspace. |
45
+
|[RunSpace10 Code Sample](./runspace10-code-sample.md)| This is the source code for the Runspace10 sample, which adds a cmdlet to [System.Management.Automation.Runspaces.RunspaceConfiguration](/dotnet/api/System.Management.Automation.Runspaces.RunspaceConfiguration) and then uses the modified configuration information to create the runspace. |
@@ -16,9 +16,9 @@ class. It is included here only for completeness.
16
16
> Your provider class will most likely derive from one of the following classes and possibly
17
17
> implement other provider interfaces:
18
18
>
19
-
> -[System.Management.Automation.Provider.Itemcmdletprovider](/dotnet/api/System.Management.Automation.Provider.ItemCmdletProvider) class. See [AccessDBProviderSample03](./accessdbprovidersample03.md).
20
-
> -[System.Management.Automation.Provider.Containercmdletprovider](/dotnet/api/System.Management.Automation.Provider.ContainerCmdletProvider) class. See [AccessDBProviderSample04](./accessdbprovidersample04.md).
21
-
> -[System.Management.Automation.Provider.Navigationcmdletprovider](/dotnet/api/System.Management.Automation.Provider.NavigationCmdletProvider) class. See [AccessDBProviderSample05](./accessdbprovidersample05.md).
19
+
> -[System.Management.Automation.Provider.ItemCmdletProvider](/dotnet/api/System.Management.Automation.Provider.ItemCmdletProvider) class. See [AccessDBProviderSample03](./accessdbprovidersample03.md).
20
+
> -[System.Management.Automation.Provider.ContainerCmdletProvider](/dotnet/api/System.Management.Automation.Provider.ContainerCmdletProvider) class. See [AccessDBProviderSample04](./accessdbprovidersample04.md).
21
+
> -[System.Management.Automation.Provider.NavigationCmdletProvider](/dotnet/api/System.Management.Automation.Provider.NavigationCmdletProvider) class. See [AccessDBProviderSample05](./accessdbprovidersample05.md).
22
22
>
23
23
> For more information about choosing which provider class to derive from based on provider
24
24
> features, see [Designing Your Windows PowerShell Provider](./provider-types.md).
@@ -28,7 +28,7 @@ This sample demonstrates the following:
28
28
- Declaring the `CmdletProvider` attribute.
29
29
30
30
- Defining a provider class that derives directly from the
> Your provider class will most likely derive from one of the following classes and possibly
22
22
> implement other provider interfaces:
23
23
>
24
-
> -[System.Management.Automation.Provider.Itemcmdletprovider](/dotnet/api/System.Management.Automation.Provider.ItemCmdletProvider) class. See [AccessDBProviderSample03](./accessdbprovidersample03.md).
25
-
> -[System.Management.Automation.Provider.Containercmdletprovider](/dotnet/api/System.Management.Automation.Provider.ContainerCmdletProvider) class. See [AccessDBProviderSample04](./accessdbprovidersample04.md).
26
-
> -[System.Management.Automation.Provider.Navigationcmdletprovider](/dotnet/api/System.Management.Automation.Provider.NavigationCmdletProvider) class. See [AccessDBProviderSample05](./accessdbprovidersample05.md).
24
+
> -[System.Management.Automation.Provider.ItemCmdletProvider](/dotnet/api/System.Management.Automation.Provider.ItemCmdletProvider) class. See [AccessDBProviderSample03](./accessdbprovidersample03.md).
25
+
> -[System.Management.Automation.Provider.ContainerCmdletProvider](/dotnet/api/System.Management.Automation.Provider.ContainerCmdletProvider) class. See [AccessDBProviderSample04](./accessdbprovidersample04.md).
26
+
> -[System.Management.Automation.Provider.NavigationCmdletProvider](/dotnet/api/System.Management.Automation.Provider.NavigationCmdletProvider) class. See [AccessDBProviderSample05](./accessdbprovidersample05.md).
27
27
>
28
28
> For more information about choosing which provider class to derive from based on provider
29
29
> features, see [Designing Your Windows PowerShell Provider](./provider-types.md).
@@ -33,35 +33,35 @@ This sample demonstrates the following:
0 commit comments