diff --git a/reference/6/Microsoft.PowerShell.Utility/Add-Member.md b/reference/6/Microsoft.PowerShell.Utility/Add-Member.md index 166c3141c506..932c2da8c396 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Add-Member.md +++ b/reference/6/Microsoft.PowerShell.Utility/Add-Member.md @@ -11,7 +11,7 @@ title: Add-Member # Add-Member ## SYNOPSIS -Adds custom properties and methods to an instance of a Windows PowerShell object. +Adds custom properties and methods to an instance of a PowerShell object. ## SYNTAX @@ -44,7 +44,7 @@ Add-Member [-NotePropertyMembers] ``` ## DESCRIPTION -The **Add-Member** cmdlet lets you add members (properties and methods) to an instance of a Windows PowerShell object. +The **Add-Member** cmdlet lets you add members (properties and methods) to an instance of a PowerShell object. For instance, you can add a NoteProperty member that contains a description of the object or a ScriptMethod member that runs a script to change the object. To use **Add-Member**, pipe the object to **Add-Member**, or use the **InputObject** parameter to specify the object. @@ -285,7 +285,7 @@ The acceptable values for this parameter are: For information about these values, see [PSMemberTypes Enumeration](https://msdn.microsoft.com/library/system.management.automation.psmembertypes) in the MSDN library. Not all objects have every type of member. -If you specify a member type that the object does not have, Windows PowerShell returns an error. +If you specify a member type that the object does not have, PowerShell returns an error. ```yaml Type: PSMemberTypes @@ -380,7 +380,7 @@ Accept wildcard characters: False Specifies a hash table or ordered dictionary of note property names and values. Type a hash table or dictionary in which the keys are note property names and the values are note property values. -For more information about hash tables and ordered dictionaries in Windows PowerShell, see about_Hash_Tables. +For more information about hash tables and ordered dictionaries in PowerShell, see about_Hash_Tables. This parameter was introduced in Windows PowerShell 3.0. diff --git a/reference/6/Microsoft.PowerShell.Utility/ConvertFrom-Csv.md b/reference/6/Microsoft.PowerShell.Utility/ConvertFrom-Csv.md index 506589332ecf..870f2f38d103 100644 --- a/reference/6/Microsoft.PowerShell.Utility/ConvertFrom-Csv.md +++ b/reference/6/Microsoft.PowerShell.Utility/ConvertFrom-Csv.md @@ -226,7 +226,7 @@ You can pipe CSV strings to this cmdlet. This cmdlet returns the objects described by the properties in the CSV strings. ## NOTES -* Because the imported objects are CSV versions of the object type, they are not recognized and formatted by the Windows PowerShell type formatting entries that format the non-CSV versions of the object type. +* Because the imported objects are CSV versions of the object type, they are not recognized and formatted by the PowerShell type formatting entries that format the non-CSV versions of the object type. In CSV format, each object is represented by a comma-separated list of the property values of the object. The property values are converted to strings (by using the ToString() method of the object), so they are generally represented by the name of the property value. diff --git a/reference/6/Microsoft.PowerShell.Utility/ConvertFrom-StringData.md b/reference/6/Microsoft.PowerShell.Utility/ConvertFrom-StringData.md index d0e502c4e7e0..a98b49afb24d 100644 --- a/reference/6/Microsoft.PowerShell.Utility/ConvertFrom-StringData.md +++ b/reference/6/Microsoft.PowerShell.Utility/ConvertFrom-StringData.md @@ -28,7 +28,7 @@ When used in a DATA section, the contents of the string must conform to the rule For more information, see about_Data_Sections. **ConvertFrom-StringData** supports escape character sequences that are allowed by conventional machine translation tools. -That is, the cmdlet can interpret backslashes (\\) as escape characters in the string data by using the [Regex.Unescape Method](https://msdn.microsoft.com/library/system.text.regularexpressions.regex.unescape), instead of the Windows PowerShell backtick character (\`) that would normally signal the end of a line in a script. +That is, the cmdlet can interpret backslashes (\\) as escape characters in the string data by using the [Regex.Unescape Method](https://msdn.microsoft.com/library/system.text.regularexpressions.regex.unescape), instead of the PowerShell backtick character (\`) that would normally signal the end of a line in a script. Inside the here-string, the backtick character does not work. You can also preserve a literal backslash in your results by escaping it with a preceding backslash, like this: \\\\. Unescaped backslash characters, such as those that are commonly used in file paths, can render as illegal escape sequences in your results. @@ -127,7 +127,7 @@ Bottom = Blue This example converts a regular double-quoted string (not a here-string) into a hash table and saves it in the $A variable. -To satisfy the condition that each key/value pair must be on a separate line, it uses the Windows PowerShell newline character (\`n) to separate the pairs. +To satisfy the condition that each key/value pair must be on a separate line, it uses the PowerShell newline character (\`n) to separate the pairs. The result is a hash table of the input. The remaining commands display the output. diff --git a/reference/6/Microsoft.PowerShell.Utility/ConvertTo-Html.md b/reference/6/Microsoft.PowerShell.Utility/ConvertTo-Html.md index d9644bef3e8f..296f0699fe85 100644 --- a/reference/6/Microsoft.PowerShell.Utility/ConvertTo-Html.md +++ b/reference/6/Microsoft.PowerShell.Utility/ConvertTo-Html.md @@ -33,7 +33,7 @@ You can use this cmdlet to display the output of a command in a Web page. You can use the parameters of **ConvertTo-Html** to select object properties, to specify a table or list format, to specify the HTML page title, to add text before and after the object, and to return only the table or list fragment, instead of a strict DTD page. -When you submit multiple objects to **ConvertTo-Html**, Windows PowerShell creates the table (or list) based on the properties of the first object that you submit. +When you submit multiple objects to **ConvertTo-Html**, PowerShell creates the table (or list) based on the properties of the first object that you submit. If the remaining objects do not have one of the specified properties, the property value of that object is an empty cell. If the remaining objects have additional properties, those property values are not included in the file. @@ -53,7 +53,7 @@ PS C:\> Get-Alias | ConvertTo-Html > aliases.htm PS C:\> Invoke-Item aliases.htm ``` -This command creates an HTML page that lists the Windows PowerShell aliases in the current console. +This command creates an HTML page that lists the PowerShell aliases in the current console. The command uses the Get-Alias cmdlet to get the aliases. It uses the pipeline operator (|) to send the aliases to the **ConvertTo-Html** cmdlet, which creates the HTML page. @@ -179,11 +179,11 @@ Determines whether the object is formatted as a table or a list. Valid values are Table and List. The default value is Table. -The Table value generates an HTML table that resembles the Windows PowerShell table format. +The Table value generates an HTML table that resembles the PowerShell table format. The header row displays the property names. Each table row represents an object and displays the object's values for each property. -The List value generates a two-column HTML table for each object that resembles the Windows PowerShell list format. +The List value generates a two-column HTML table for each object that resembles the PowerShell list format. The first column displays the property name; the second column displays the property value. ```yaml @@ -415,7 +415,7 @@ You can pipe any .NET object to **ConvertTo-Html**. ## NOTES * To use this cmdlet, pipe one or more objects to the cmdlet or use the InputObject parameter to specify the object. When the input consists of multiple objects, the output of these two methods is quite different. - - When you pipe multiple objects to a cmdlet, Windows PowerShell sends the objects to the cmdlet one at a time. + - When you pipe multiple objects to a cmdlet, PowerShell sends the objects to the cmdlet one at a time. As a result, **ConvertTo-Html** creates a table that displays the individual objects. For example, if you pipe the processes on a computer to **ConvertTo-Html**, the resulting table displays all of the processes. diff --git a/reference/6/Microsoft.PowerShell.Utility/ConvertTo-Json.md b/reference/6/Microsoft.PowerShell.Utility/ConvertTo-Json.md index 92bf7df68586..6be3a7b84905 100644 --- a/reference/6/Microsoft.PowerShell.Utility/ConvertTo-Json.md +++ b/reference/6/Microsoft.PowerShell.Utility/ConvertTo-Json.md @@ -23,7 +23,7 @@ ConvertTo-Json [-InputObject] [-Depth ] [-Compress] [ $JsonSecurityHelp = Get-Content $Pshome\Modules\Microsoft.PowerShell.Security\en-US\Microsoft.PowerShell.Security.dll-Help.xml | ConvertTo-Json ``` -This command uses the **ConvertTo-Json** cmdlet to convert a Windows PowerShell Help file from XML format to JSON format. +This command uses the **ConvertTo-Json** cmdlet to convert a PowerShell Help file from XML format to JSON format. You can use a command like this to use the Help topic content in a web service application. ## PARAMETERS diff --git a/reference/6/Microsoft.PowerShell.Utility/Debug-Runspace.md b/reference/6/Microsoft.PowerShell.Utility/Debug-Runspace.md index f8f2e14551f1..ac987a977e91 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Debug-Runspace.md +++ b/reference/6/Microsoft.PowerShell.Utility/Debug-Runspace.md @@ -37,13 +37,13 @@ Debug-Runspace [-InstanceId] [-WhatIf] [-Confirm] [] ## DESCRIPTION The **Debug-Runspace** cmdlet starts an interactive debugging session with a local or remote active runspace. -You can find a runspace that you want to debug by first running Get-Process to find processes associated with Windows PowerShell, then Enter-PSHostProcess with the process ID specified in the *Id* parameter to attach to the process, and then Get-Runspace to list runspaces within the Windows PowerShell host process. +You can find a runspace that you want to debug by first running Get-Process to find processes associated with PowerShell, then Enter-PSHostProcess with the process ID specified in the *Id* parameter to attach to the process, and then Get-Runspace to list runspaces within the PowerShell host process. -After you have selected a runspace to debug, if the runspace is currently running a command or script, or if the script has stopped at a breakpoint, Windows PowerShell opens a remote debugger session for the runspace. +After you have selected a runspace to debug, if the runspace is currently running a command or script, or if the script has stopped at a breakpoint, PowerShell opens a remote debugger session for the runspace. You can debug the runspace script in the same way remote session scripts are debugged. -You can only attach to a Windows PowerShell host process if you are an administrator on the computer that is running the process, or you are running the script that you want to debug. -Also, you cannot enter the host process that is running the current Windows PowerShell session; you can only enter a host process that is running a different Windows PowerShell session. +You can only attach to a PowerShell host process if you are an administrator on the computer that is running the process, or you are running the script that you want to debug. +Also, you cannot enter the host process that is running the current PowerShell session; you can only enter a host process that is running a different PowerShell session. For example, if you are working in a PowerShell.exe session, you can't enter the host process for that session, but you can enter the host process of a running Windows PowerShell ISE session. ## EXAMPLES diff --git a/reference/6/Microsoft.PowerShell.Utility/Disable-PSBreakpoint.md b/reference/6/Microsoft.PowerShell.Utility/Disable-PSBreakpoint.md index b7ef0bc5cce2..497138cabfe0 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Disable-PSBreakpoint.md +++ b/reference/6/Microsoft.PowerShell.Utility/Disable-PSBreakpoint.md @@ -34,8 +34,8 @@ To re-enable a breakpoint, use the Enable-PSBreakpoint cmdlet. Breakpoints are enabled by default when you create them by using the Set-PSBreakpoint cmdlet. A breakpoint is a point in a script where execution stops temporarily so that you can examine the instructions in the script. -**Disable-PSBreakpoint** is one of several cmdlets designed for debugging Windows PowerShell scripts. -For more information about the Windows PowerShell debugger, see about_Debuggers. +**Disable-PSBreakpoint** is one of several cmdlets designed for debugging PowerShell scripts. +For more information about the PowerShell debugger, see about_Debuggers. ## EXAMPLES diff --git a/reference/6/Microsoft.PowerShell.Utility/Enable-PSBreakpoint.md b/reference/6/Microsoft.PowerShell.Utility/Enable-PSBreakpoint.md index 68b2aa386c80..20598ac68e04 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Enable-PSBreakpoint.md +++ b/reference/6/Microsoft.PowerShell.Utility/Enable-PSBreakpoint.md @@ -34,8 +34,8 @@ Newly created breakpoints are automatically enabled, but you can disable them by Technically, this cmdlet changes the value of the Enabled property of a breakpoint object to True. -**Enable-PSBreakpoint** is one of several cmdlets designed for debugging Windows PowerShell scripts. -For more information about the Windows PowerShell debugger, see about_Debuggers. +**Enable-PSBreakpoint** is one of several cmdlets designed for debugging PowerShell scripts. +For more information about the PowerShell debugger, see about_Debuggers. ## EXAMPLES diff --git a/reference/6/Microsoft.PowerShell.Utility/Export-Alias.md b/reference/6/Microsoft.PowerShell.Utility/Export-Alias.md index d9933a730be6..efe54500031c 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Export-Alias.md +++ b/reference/6/Microsoft.PowerShell.Utility/Export-Alias.md @@ -31,7 +31,7 @@ Export-Alias -LiteralPath [[-Name] ] [-PassThru] [-As -LiteralPath ``` ## DESCRIPTION -The **Export-FormatData** cmdlet creates Windows PowerShell formatting files (format.ps1xml) from the formatting objects in the current session. +The **Export-FormatData** cmdlet creates PowerShell formatting files (format.ps1xml) from the formatting objects in the current session. It takes the **ExtendedTypeDefinition** objects that Get-FormatData returns and saves them in a file in XML format. -Windows PowerShell uses the data in formatting files (format.ps1xml) to generate the default display of Microsoft .NET Framework objects in the session. +PowerShell uses the data in formatting files (format.ps1xml) to generate the default display of Microsoft .NET Framework objects in the session. You can view and edit the formatting files and use the Update-FormatData cmdlet to add the formatting data to a session. -For more information about formatting files in Windows PowerShell, see about_Format.ps1xml. +For more information about formatting files in PowerShell, see about_Format.ps1xml. ## EXAMPLES @@ -188,7 +188,7 @@ Specifies a location for the output file. Unlike the *Path* parameter, the value of *LiteralPath* is used exactly as it is typed. No characters are interpreted as wildcards. If the path includes escape characters, enclose it in single quotation marks. -Single quotation marks tell Windows PowerShell not to interpret any characters as escape sequences. +Single quotation marks tell PowerShell not to interpret any characters as escape sequences. ```yaml Type: String diff --git a/reference/6/Microsoft.PowerShell.Utility/Export-PSSession.md b/reference/6/Microsoft.PowerShell.Utility/Export-PSSession.md index f15c3df58778..aaea8d431d28 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Export-PSSession.md +++ b/reference/6/Microsoft.PowerShell.Utility/Export-PSSession.md @@ -11,7 +11,7 @@ title: Export-PSSession # Export-PSSession ## SYNOPSIS -Imports commands from another session and saves them in a Windows PowerShell module. +Imports commands from another session and saves them in a PowerShell module. ## SYNTAX @@ -23,7 +23,7 @@ Export-PSSession [-OutputModule] [-Force] [-Encoding ] [[-Comma ``` ## DESCRIPTION -The **Export-PSSession** cmdlet gets cmdlets, functions, aliases, and other command types from another PSSession on a local or remote computer and saves them in a Windows PowerShell module. +The **Export-PSSession** cmdlet gets cmdlets, functions, aliases, and other command types from another PSSession on a local or remote computer and saves them in a PowerShell module. To add the commands from the module to the current session, use the Import-Module cmdlet. Unlike Import-PSSession, which imports commands from another PSSession into the current session, **Export-PSSession** saves the commands in a module. @@ -33,7 +33,7 @@ To export commands, first use the New-PSSession cmdlet to create a PSSession tha Then use the **Export-PSSession** cmdlet to export the commands. By default, **Export-PSSession** exports all commands, except for commands that exist in the current session, but you can use the *CommandName* parameter to specify the commands to export. -The **Export-PSSession** cmdlet uses the implicit remoting feature of Windows PowerShell. +The **Export-PSSession** cmdlet uses the implicit remoting feature of PowerShell. When you import commands into the current session, they run implicitly in the original session or in a similar session on the originating computer. ## EXAMPLES @@ -88,7 +88,7 @@ After the commands in a module are added to the current session, you can use the The sixth command uses the **Test-Files** cmdlet, which was exported from the Server01 computer and added to the session. Although it is not evident, the **Test-Files** command actually runs in a remote session on the computer from which the command was imported. -Windows PowerShell creates a session from information that is stored in the module. +PowerShell creates a session from information that is stored in the module. ### Example 4: Import and clobber commands in the current session ``` @@ -204,18 +204,18 @@ Use *CommandType* or its alias, *Type*. The acceptable values for this parameter are: -- Alias: All Windows PowerShell aliases in the current session. +- Alias: All PowerShell aliases in the current session. - All: All command types. It is the equivalent of "get-command *". - Application. -All files other than Windows PowerShell files in paths listed in the Path environment variable ($env:path), including .txt, .exe, and .dll files. +All files other than PowerShell files in paths listed in the Path environment variable ($env:path), including .txt, .exe, and .dll files. - Cmdlet. The cmdlets in the current session. "Cmdlet" is the default. - ExternalScript. All .ps1 files in the paths listed in the Path environment variable ($env:path). - Filter and Function. -All Windows PowerShell functions. +All PowerShell functions. - Script. Script blocks in the current session. @@ -319,7 +319,7 @@ Accept wildcard characters: False ``` ### -Module -Exports only the commands in the specified Windows PowerShell snap-ins and modules. +Exports only the commands in the specified PowerShell snap-ins and modules. Enter the snap-in and module names. Wildcards are not permitted. @@ -407,12 +407,12 @@ You cannot pipe objects to **Export-PSSession**. **Export-PSSession** returns a list of files that comprise the module that it created. ## NOTES -* **Export-PSSession** relies on the Windows PowerShell remoting infrastructure. To use this cmdlet, the computer must be configured for remoting. For more information, see about_Remote_Requirements. +* **Export-PSSession** relies on the PowerShell remoting infrastructure. To use this cmdlet, the computer must be configured for remoting. For more information, see about_Remote_Requirements. - You cannot use **Export-PSSession** to export a Windows PowerShell provider. + You cannot use **Export-PSSession** to export a PowerShell provider. Exported commands run implicitly in the PSSession from which they were exported. -However, the details of running the commands remotely are handled entirely by Windows PowerShell. +However, the details of running the commands remotely are handled entirely by PowerShell. You can run the exported commands just as you would run local commands. **Export-Module** captures and saves information about the PSSession in the module that it exports. @@ -433,7 +433,7 @@ You might see the progress bar while the command is running. Exported commands have the same limitations as other remote commands, including the inability to start a program with a user interface, such as Notepad. - Because Windows PowerShell profiles are not run in PSSessions, the commands that a profile adds to a session are not available to **Export-PSSession**. + Because PowerShell profiles are not run in PSSessions, the commands that a profile adds to a session are not available to **Export-PSSession**. To export commands from a profile, use an Invoke-Command command to run the profile in the PSSession manually before exporting commands. The module that **Export-PSSession** creates might include a formatting file, even if the command does not import formatting data. diff --git a/reference/6/Microsoft.PowerShell.Utility/Format-Custom.md b/reference/6/Microsoft.PowerShell.Utility/Format-Custom.md index 0412e03a0832..4b9223828c1a 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Format-Custom.md +++ b/reference/6/Microsoft.PowerShell.Utility/Format-Custom.md @@ -23,7 +23,7 @@ Format-Custom [[-Property] ] [-Depth ] [-GroupBy ] [-Vi ## DESCRIPTION The `Format-Custom` cmdlet formats the output of a command as defined in an alternate view. `Format-Custom` is designed to display views that are not just tables or just lists. -You can use the views defined in the *format.PS1XML files in the Windows PowerShell directory, or you can create your own views in new PS1XML files and use the Update-FormatData cmdlet to add them to Windows PowerShell. +You can use the views defined in the *format.PS1XML files in the PowerShell directory, or you can create your own views in new PS1XML files and use the Update-FormatData cmdlet to add them to PowerShell. ## EXAMPLES @@ -33,7 +33,7 @@ PS C:\> Get-Command Start-Transcript | Format-Custom -View MyView ``` This command formats information about the `Start-Transcript` cmdlet in the format defined by the MyView view, a custom view created by the user. -To run this command successfully, you must first create a new PS1XML file, define the MyView view, and then use the Update-FormatData command to add the PS1XML file to Windows PowerShell. +To run this command successfully, you must first create a new PS1XML file, define the MyView view, and then use the Update-FormatData command to add the PS1XML file to PowerShell. ### Example 2: Format output with the default view ```powershell diff --git a/reference/6/Microsoft.PowerShell.Utility/Format-Hex.md b/reference/6/Microsoft.PowerShell.Utility/Format-Hex.md index eaefc10af0a8..ad873c5885c7 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Format-Hex.md +++ b/reference/6/Microsoft.PowerShell.Utility/Format-Hex.md @@ -113,7 +113,7 @@ This parameter does not accept wildcard characters. To use wildcard characters, specify the *Path* parameter instead. If this parameter includes escape characters, enclose the path in single quotation marks. -Windows PowerShell does not interpret any characters in a single quoted string as escape sequences. +PowerShell does not interpret any characters in a single quoted string as escape sequences. For more information, type `Get-Help about_Quoting_Rules`. ```yaml diff --git a/reference/6/Microsoft.PowerShell.Utility/Format-List.md b/reference/6/Microsoft.PowerShell.Utility/Format-List.md index 2b1425fcc919..6cd3deb477df 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Format-List.md +++ b/reference/6/Microsoft.PowerShell.Utility/Format-List.md @@ -24,7 +24,7 @@ Format-List [[-Property] ] [-GroupBy ] [-View ] [-Show The **Format-List** cmdlet formats the output of a command as a list of properties in which each property is displayed on a separate line. You can use **Format-List** to format and display all or selected properties of an object as a list (format-list *). -Because more space is available for each item in a list than in a table, Windows PowerShell displays more properties of the object in the list, and the property values are less likely to be truncated. +Because more space is available for each item in a list than in a table, PowerShell displays more properties of the object in the list, and the property values are less likely to be truncated. ## EXAMPLES @@ -45,7 +45,7 @@ PS C:\> $A = Get-ChildItem $pshome\*.ps1xml PS C:\> Format-List -InputObject $A ``` -These commands display information about the PS1XML files in the Windows PowerShell directory as a list. +These commands display information about the PS1XML files in the PowerShell directory as a list. The first command gets the objects representing the files and stores them in the $a variable. @@ -271,15 +271,15 @@ You can pipe any object to **Format-List**. * You can also refer to Format-List by its built-in alias, FL. For more information, see about_Aliases. The format cmdlets, such as **Format-List**, arrange the data to be displayed but do not display it. -The data is displayed by the output features of Windows PowerShell and by the cmdlets that contain the Out verb (the Out cmdlets), such as Out-Host, Out-File, and Out-Printer. +The data is displayed by the output features of PowerShell and by the cmdlets that contain the Out verb (the Out cmdlets), such as Out-Host, Out-File, and Out-Printer. - If you do not use a format cmdlet, Windows PowerShell applies that default format for each object that it displays. + If you do not use a format cmdlet, PowerShell applies that default format for each object that it displays. The *GroupBy* parameter assumes that the objects are sorted. Before using Format-Custom to group the objects, use Sort-Object to sort them. The *View* parameter lets you specify an alternate format for the table. -You can use the views defined in the *.format.PS1XML files in the Windows PowerShell directory, or you can create your own views in new PS1XML files and use the Update-FormatData cmdlet to include them in Windows PowerShell. +You can use the views defined in the *.format.PS1XML files in the PowerShell directory, or you can create your own views in new PS1XML files and use the Update-FormatData cmdlet to include them in PowerShell. The alternate view for the View parameter must use the list format; if not, the command fails. If the alternate view is a table, use Format-Table. diff --git a/reference/6/Microsoft.PowerShell.Utility/Format-Table.md b/reference/6/Microsoft.PowerShell.Utility/Format-Table.md index 2eaec3058b23..1e3a36ad1dde 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Format-Table.md +++ b/reference/6/Microsoft.PowerShell.Utility/Format-Table.md @@ -369,7 +369,7 @@ You can pipe any object to `Format-Table`. ## NOTES The **GroupBy** parameter assumes that the objects are sorted. Before using `Format-Table` to group the objects, use the Sort-Object cmdlet to sort them. -The **View** parameter lets you specify an alternate format for the table. You can use the views defined in the *.format.PS1XML files in the Windows PowerShell directory or you can create your own views in new PS1XML files and then use the Update-FormatData cmdlet to include them in Windows PowerShell. +The **View** parameter lets you specify an alternate format for the table. You can use the views defined in the *.format.PS1XML files in the PowerShell directory or you can create your own views in new PS1XML files and then use the Update-FormatData cmdlet to include them in PowerShell. The alternate views for the **View** parameter must use the table format. If it does not, the command fails. If the alternate view is a list, use the Format-List cmdlet. If the alternate view is neither a list nor a table, use the Format-Custom cmdlet. ## RELATED LINKS diff --git a/reference/6/Microsoft.PowerShell.Utility/Format-Wide.md b/reference/6/Microsoft.PowerShell.Utility/Format-Wide.md index a34457cb0edf..a549d0515cbe 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Format-Wide.md +++ b/reference/6/Microsoft.PowerShell.Utility/Format-Wide.md @@ -43,7 +43,7 @@ PS C:\> Get-ChildItem HKCU:\software\microsoft | Format-Wide -Property pschildna This command displays the names of registry keys in the HKEY_CURRENT_USER\Software\Microsoft key. The Get-ChildItem cmdlet gets objects representing the keys. -The path is specified as HKCU:, one of the drives exposed by the Windows PowerShell Registry provider, followed by the key path. +The path is specified as HKCU:, one of the drives exposed by the PowerShell Registry provider, followed by the key path. The pipeline operator (|) passes the registry key objects through the pipeline to `Format-Wide`, which formats them for output. The **Property** parameter specifies the name of the property, and the **AutoSize** parameter adjusts the columns for readability. @@ -277,7 +277,7 @@ The **GroupBy** parameter assumes that the objects are sorted. Before using Format-Custom to group the objects, use `Sort-Object` to sort them. The **View** parameter lets you specify an alternate format for the table. -You can use the views defined in the **.format.PS1XML files in the Windows PowerShell directory or you can create your own views in new PS1XML files and use the `Update-FormatData` cmdlet to include them in Windows PowerShell. +You can use the views defined in the **.format.PS1XML files in the PowerShell directory or you can create your own views in new PS1XML files and use the `Update-FormatData` cmdlet to include them in PowerShell. The alternate view for the **View** parameter must use table format; if it does not, the command fails. If the alternate view is a list, use `Format-List`. diff --git a/reference/6/Microsoft.PowerShell.Utility/Get-Alias.md b/reference/6/Microsoft.PowerShell.Utility/Get-Alias.md index c5d78db35cbb..df51bf33ed5d 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Get-Alias.md +++ b/reference/6/Microsoft.PowerShell.Utility/Get-Alias.md @@ -29,7 +29,7 @@ Get-Alias [-Exclude ] [-Scope ] [-Definition ] ## DESCRIPTION The **Get-Alias** cmdlet gets the aliases in the current session. -This includes built-in aliases, aliases that you have set or imported, and aliases that you have added to your Windows PowerShell profile. +This includes built-in aliases, aliases that you have set or imported, and aliases that you have added to your PowerShell profile. By default, **Get-Alias** takes an alias and returns the command name. When you use the *Definition* parameter, **Get-Alias** takes a command name and returns its aliases. @@ -83,7 +83,7 @@ PS C:\> Get-Alias | Where-Object {$_.Options -Match "ReadOnly"} ``` This command gets all aliases in which the value of the Options property is ReadOnly. -This command provides a quick way to find the aliases that are built into Windows PowerShell, because they have the ReadOnly option. +This command provides a quick way to find the aliases that are built into PowerShell, because they have the ReadOnly option. Options is just one property of the AliasInfo objects that **Get-Alias** gets. To find all properties and methods of AliasInfo objects, type `Get-Alias | get-member`. @@ -191,7 +191,7 @@ You can pipe alias names to **Get-Alias**. ### System.Management.Automation.AliasInfo **Get-Alias** returns an object that represents each alias. -**Get-Alias** returns the same object for every alias, but Windows PowerShell uses an arrow-based format to display the names of non-hyphenated aliases. +**Get-Alias** returns the same object for every alias, but PowerShell uses an arrow-based format to display the names of non-hyphenated aliases. ## NOTES * To create a new alias, use Set-Alias or New-Alias. To delete an alias, use Remove-Item. diff --git a/reference/6/Microsoft.PowerShell.Utility/Get-Date.md b/reference/6/Microsoft.PowerShell.Utility/Get-Date.md index 911cb46ceae8..68580d394869 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Get-Date.md +++ b/reference/6/Microsoft.PowerShell.Utility/Get-Date.md @@ -147,7 +147,7 @@ The table includes the **Label** key, which specifies the name of the property, The expression uses the **ConvertToDateTime** method to convert each instance of ReleaseDate to a .NET Framework DateTime object. Then, the value is subtracted from the value of the `Get-Date` cmdlet, which, without parameters, gets the current date. -The backtick character (`` ` ``) is the line continuation character in Windows PowerShell. +The backtick character (`` ` ``) is the line continuation character in PowerShell. ### Example 8 @@ -260,7 +260,7 @@ Specifies the day of the month that is displayed. Enter a value from 1 to 31. The default is the current day. -If you specify a value that is greater than the number of days in the month, Windows PowerShell adds the number of days to the month and displays the result. +If you specify a value that is greater than the number of days in the month, PowerShell adds the number of days to the month and displays the result. For example, "`Get-Date -Month 2 -Day 31`" displays "March 3", not "February 31". ```yaml @@ -305,7 +305,7 @@ Displays the date and time in the Microsoft .NET Framework format indicated by t Enter a format specifier. For a list of available format specifiers, see [DateTimeFormatInfo Class](http://go.microsoft.com/fwlink/?LinkId=143638) in the MSDN (Microsoft Developer Network) library. -When you use the `-Format` parameter, Windows PowerShell gets only the properties of the **DateTime** object that it needs to display the date in the format that you specify. +When you use the `-Format` parameter, PowerShell gets only the properties of the **DateTime** object that it needs to display the date in the format that you specify. As a result, some of the properties and methods of **DateTime** objects might not be available. Starting in Windows PowerShell 5.0, you can use the following additional formats as values for the `-Format` parameter. @@ -452,7 +452,7 @@ Accept wildcard characters: False Displays the date and time in UNIX format. For a list of the format specifiers, see the Notes section. -When you use the `-UFormat` parameter, Windows PowerShell gets only the properties of the **DateTime** object that it needs to display the date in the format that you specify. +When you use the `-UFormat` parameter, PowerShell gets only the properties of the **DateTime** object that it needs to display the date in the format that you specify. As a result, some of the properties and methods of **DateTime** objects might not be available. ```yaml @@ -501,7 +501,7 @@ Otherwise, it returns a **DateTime** object. ## NOTES * By default, the date-time is displayed in long-date and long-time formats for the system locale. - When you pipe a date to cmdlets that expect string input, such as the Add-Content cmdlet, Windows PowerShell converts the **DateTime** object to a string before adding it to the file. The default `ToString()` format is short date and long time. To specify an alternate format, use the `-Format` or `-UFormat` parameters of `Get-Date`. + When you pipe a date to cmdlets that expect string input, such as the Add-Content cmdlet, PowerShell converts the **DateTime** object to a string before adding it to the file. The default `ToString()` format is short date and long time. To specify an alternate format, use the `-Format` or `-UFormat` parameters of `Get-Date`. * Uformat Values: diff --git a/reference/6/Microsoft.PowerShell.Utility/Get-Event.md b/reference/6/Microsoft.PowerShell.Utility/Get-Event.md index 9a4b3a578e41..cbae88b32df9 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Get-Event.md +++ b/reference/6/Microsoft.PowerShell.Utility/Get-Event.md @@ -26,11 +26,11 @@ Get-Event [-EventIdentifier] [] ``` ## DESCRIPTION -The **Get-Event** cmdlet gets events in the Windows PowerShell event queue for the current session. +The **Get-Event** cmdlet gets events in the PowerShell event queue for the current session. You can get all events or use the *EventIdentifier* or *SourceIdentifier* parameter to specify the events. When an event occurs, it is added to the event queue. -The event queue includes events for which you have registered, events created by using the New-Event cmdlet, and the event that is raised when Windows PowerShell exits. +The event queue includes events for which you have registered, events created by using the New-Event cmdlet, and the event that is raised when PowerShell exits. You can use **Get-Event** or Wait-Event to get the events. This cmdlet does not get events from the Event Viewer logs. diff --git a/reference/6/Microsoft.PowerShell.Utility/Get-EventSubscriber.md b/reference/6/Microsoft.PowerShell.Utility/Get-EventSubscriber.md index c040c65dc9f7..d7b46e16dfb6 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Get-EventSubscriber.md +++ b/reference/6/Microsoft.PowerShell.Utility/Get-EventSubscriber.md @@ -28,7 +28,7 @@ Get-EventSubscriber [-SubscriptionId] [-Force] [] ## DESCRIPTION The **Get-EventSubscriber** cmdlet gets the event subscribers in the current session. -When you subscribe to an event by using a Register event cmdlet, an event subscriber is added to your Windows PowerShell session, and the events to which you subscribed are added to your event queue whenever they are raised. +When you subscribe to an event by using a Register event cmdlet, an event subscriber is added to your PowerShell session, and the events to which you subscribed are added to your event queue whenever they are raised. To cancel an event subscription, delete the event subscriber by using the Unregister-Event cmdlet. ## EXAMPLES diff --git a/reference/6/Microsoft.PowerShell.Utility/Get-FileHash.md b/reference/6/Microsoft.PowerShell.Utility/Get-FileHash.md index 26b4fbb7e560..5d28714a4ca0 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Get-FileHash.md +++ b/reference/6/Microsoft.PowerShell.Utility/Get-FileHash.md @@ -165,7 +165,7 @@ Specifies the path to a file. Unlike the *Path* parameter, the value of the *LiteralPath* parameter is used exactly as it is typed. No characters are interpreted as wildcard characters. If the path includes escape characters, enclose the path in single quotation marks. -Single quotation marks instruct Windows PowerShell not to interpret characters as escape sequences. +Single quotation marks instruct PowerShell not to interpret characters as escape sequences. ```yaml Type: String[] diff --git a/reference/6/Microsoft.PowerShell.Utility/Get-FormatData.md b/reference/6/Microsoft.PowerShell.Utility/Get-FormatData.md index 9b90b2e0aee2..fb6fd694f57f 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Get-FormatData.md +++ b/reference/6/Microsoft.PowerShell.Utility/Get-FormatData.md @@ -27,7 +27,7 @@ The formatting data in the session includes formatting data from Format.ps1xml f You can use this cmdlet to examine the formatting data. Then, you can use the Export-FormatData cmdlet to serialize the objects, convert them to XML, and save them in Format.ps1xml files. -For more information about formatting files in Windows PowerShell, see about_Format.ps1xml. +For more information about formatting files in PowerShell, see about_Format.ps1xml. ## EXAMPLES diff --git a/reference/6/Microsoft.PowerShell.Utility/Get-Host.md b/reference/6/Microsoft.PowerShell.Utility/Get-Host.md index 752295acf292..5be1dc851c03 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Get-Host.md +++ b/reference/6/Microsoft.PowerShell.Utility/Get-Host.md @@ -20,9 +20,9 @@ Get-Host [] ``` ## DESCRIPTION -The **Get-Host** cmdlet gets an object that represents the program that is hosting Windows PowerShell. +The **Get-Host** cmdlet gets an object that represents the program that is hosting PowerShell. -The default display includes the Windows PowerShell version number and the current region and language settings that the host is using, but the host object contains a wealth of information, including detailed information about the version of Windows PowerShell that is currently running and the current culture and UI culture of Windows PowerShell. +The default display includes the PowerShell version number and the current region and language settings that the host is using, but the host object contains a wealth of information, including detailed information about the version of PowerShell that is currently running and the current culture and UI culture of PowerShell. You can also use this cmdlet to customize features of the host program user interface, such as the text and background colors. ## EXAMPLES @@ -41,8 +41,8 @@ IsRunspacePushed : False Runspace : System.Management.Automation.Runspaces.LocalRunspace ``` -This command displays information about the Windows PowerShell console, which is the current host program for Windows PowerShell in this example. -It includes the name of the host, the version of Windows PowerShell that is running in the host, and current culture and UI culture. +This command displays information about the PowerShell console, which is the current host program for PowerShell in this example. +It includes the name of the host, the version of PowerShell that is running in the host, and current culture and UI culture. The Version, UI, CurrentCulture, CurrentUICulture, PrivateData, and Runspace properties each contain an object with very useful properties. Later examples examine these properties. @@ -56,7 +56,7 @@ PS C:\> $Win.Width = 10 PS C:\> $H.UI.RawUI.Set_WindowSize($Win) ``` -This command resizes the Windows PowerShell window to 10 pixels by 10 pixels. +This command resizes the PowerShell window to 10 pixels by 10 pixels. ### Example 3: Get the PowerShell version for the host ``` @@ -69,7 +69,7 @@ MajorRevision : -1 MinorRevision : -1 ``` -This command gets detailed information about the version of Windows PowerShell running in the host. +This command gets detailed information about the version of PowerShell running in the host. You can view, but not change, these values. The Version property of **Get-Host** contains a **System.Version** object. @@ -102,7 +102,7 @@ UseUserOverride : True IsReadOnly : False ``` -This command gets detailed information about the current culture set for Windows PowerShell running in the host. +This command gets detailed information about the current culture set for PowerShell running in the host. This is the same information that is returned by the Get-Culture cmdlet. Similarly, the **CurrentUICulture** property returns the same object that Get-UICulture returns. @@ -142,7 +142,7 @@ AbbreviatedMonthGenitiveNames : {Jan, Feb, Mar, Apr...} MonthGenitiveNames : {January, February, March, April...} ``` -This command returns detailed information about the DateTimeFormat of the current culture that is being used for Windows PowerShell. +This command returns detailed information about the DateTimeFormat of the current culture that is being used for PowerShell. The **CurrentCulture** property of the host object contains a **CultureInfo** object that, in turn, has many useful properties. Among them, the **DateTimeFormat** property contains a **DateTimeFormatInfo** object with many useful properties. @@ -175,11 +175,11 @@ PS C:\> (Get-Host).UI.RawUI.BackgroundColor = "Black" PS C:\> cls ``` -These commands change the background color of the Windows PowerShell console to black. +These commands change the background color of the PowerShell console to black. The **cls** command is an alias for the Clear-Host function, which clears the screen and changes the whole screen to the new color. This change is effective only in the current session. -To change the background color of the console for all sessions, add the command to your Windows PowerShell profile. +To change the background color of the console for all sessions, add the command to your PowerShell profile. ### Example 8: Set the background color for error messages ``` diff --git a/reference/6/Microsoft.PowerShell.Utility/Get-Member.md b/reference/6/Microsoft.PowerShell.Utility/Get-Member.md index 5956d105f5bd..dd37bf02ec9a 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Get-Member.md +++ b/reference/6/Microsoft.PowerShell.Utility/Get-Member.md @@ -191,13 +191,13 @@ Attributes PS C:\> [appdomain]::CurrentDomain.GetAssemblies() | ForEach-Object { ``` This example shows how to determine which properties of an object can be changed. -The example uses a file, but you can use this command format to find the changeable properties of any object in Windows PowerShell. +The example uses a file, but you can use this command format to find the changeable properties of any object in PowerShell. The first command uses the Get-Item cmdlet to get a text file, and then it saves the file object in the $File variable. The second command gets all of the changeable properties of the file object in the $File variable and displays the names of the properties in a table. -The third command gets the changeable properties of all objects in your Windows PowerShell session. +The third command gets the changeable properties of all objects in your PowerShell session. ### Example 8: Get members of each item in a collection ``` @@ -250,10 +250,10 @@ By default, **Get-Member** gets these properties in all views other than Base an The following list describes the properties that are added when you use the *Force* parameter: - PSBase: The original properties of the .NET Framework object without extension or adaptation. These are the properties defined for the object class and listed in MSDN. -- PSAdapted. The properties and methods defined in the Windows PowerShell extended type system. +- PSAdapted. The properties and methods defined in the PowerShell extended type system. - PSExtended. The properties and methods that were added in the Types.ps1xml files or by using the Add-Member cmdlet. -- PSObject. The adapter that converts the base object to a Windows PowerShell**PSObject** object. -- PSTypeNames. A list of object types that describe the object, in order of specificity. When formatting the object, Windows PowerShell searches for the types in the Format.ps1xml files in the Windows PowerShell installation directory ($pshome). It uses the formatting definition for the first type that it finds. +- PSObject. The adapter that converts the base object to a PowerShell**PSObject** object. +- PSTypeNames. A list of object types that describe the object, in order of specificity. When formatting the object, PowerShell searches for the types in the Format.ps1xml files in the PowerShell installation directory ($pshome). It uses the formatting definition for the first type that it finds. ```yaml Type: SwitchParameter @@ -314,7 +314,7 @@ The acceptable values for this parameter are: For information about these values, see [PSMemberTypes Enumeration](https://msdn.microsoft.com/library/system.management.automation.psmembertypes) in the MSDN library. Not all objects have every type of member. -If you specify a member type that the object does not have, Windows PowerShell returns a null value. +If you specify a member type that the object does not have, PowerShell returns a null value. To get related types of members, such as all extended members, use the *View* parameter. If you use the *MemberType* parameter with the *Static* or *View* parameters, **Get-Member** gets the members that belong to both sets. @@ -380,7 +380,7 @@ The default is Adapted, Extended. The acceptable values for this parameter are: - Base. Gets only the original properties and methods of the .NET Framework object (without extension or adaptation). -- Adapted. Gets only the properties and methods defined in the Windows PowerShell extended type system. +- Adapted. Gets only the properties and methods defined in the PowerShell extended type system. - Extended. Gets only the properties and methods that were added in the Types.ps1xml files or by using the Add-Member cmdlet. - All. Gets the members in the Base, Adapted, and Extended views. diff --git a/reference/6/Microsoft.PowerShell.Utility/Get-PSBreakpoint.md b/reference/6/Microsoft.PowerShell.Utility/Get-PSBreakpoint.md index 56e70302de89..650bc79a5c6a 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Get-PSBreakpoint.md +++ b/reference/6/Microsoft.PowerShell.Utility/Get-PSBreakpoint.md @@ -45,8 +45,8 @@ The **Get-PSBreakPoint** cmdlet gets the breakpoints that are set in the current You can use the cmdlet parameters to get particular breakpoints. A breakpoint is a point in a command or script where execution stops temporarily so that you can examine the instructions. -**Get-PSBreakpoint** is one of several cmdlets designed for debugging Windows PowerShell scripts and commands. -For more information about the Windows PowerShell debugger, see about_Debuggers. +**Get-PSBreakpoint** is one of several cmdlets designed for debugging PowerShell scripts and commands. +For more information about the PowerShell debugger, see about_Debuggers. ## EXAMPLES diff --git a/reference/6/Microsoft.PowerShell.Utility/Get-PSCallStack.md b/reference/6/Microsoft.PowerShell.Utility/Get-PSCallStack.md index ceca98ae288b..475d4320af8b 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Get-PSCallStack.md +++ b/reference/6/Microsoft.PowerShell.Utility/Get-PSCallStack.md @@ -22,7 +22,7 @@ Get-PSCallStack [] ## DESCRIPTION The **Get-PSCallStack** cmdlet displays the current call stack. -Although it is designed to be used with the Windows PowerShell debugger, you can use this cmdlet to display the call stack in a script or function outside of the debugger. +Although it is designed to be used with the PowerShell debugger, you can use this cmdlet to display the call stack in a script or function outside of the debugger. To run a **Get-PSCallStack** command while in the debugger, type `k` or `Get-PSCallStack`. @@ -66,7 +66,7 @@ Get-Content type This command uses the **Get-PSCallStack** cmdlet to display the call stack for My-Alias, a simple function that gets the aliases for a cmdlet name. -The first command enters the function at the Windows PowerShell prompt. +The first command enters the function at the PowerShell prompt. The second command uses the Set-PSBreakpoint cmdlet to set a breakpoint on the My-Alias function. The third command uses the My-Alias function to get all of the aliases in the current session for the Get-Content cmdlet. diff --git a/reference/6/Microsoft.PowerShell.Utility/Get-Runspace.md b/reference/6/Microsoft.PowerShell.Utility/Get-Runspace.md index 7fcfb5ef9674..b86e8783a74f 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Get-Runspace.md +++ b/reference/6/Microsoft.PowerShell.Utility/Get-Runspace.md @@ -11,7 +11,7 @@ title: Get-Runspace # Get-Runspace ## SYNOPSIS -Gets active runspaces within a Windows PowerShellhost process. +Gets active runspaces within a PowerShellhost process. ## SYNTAX @@ -31,7 +31,7 @@ Get-Runspace [-InstanceId] [] ``` ## DESCRIPTION -The **Get-Runspace** cmdlet gets active runspaces in a Windows PowerShell host process. +The **Get-Runspace** cmdlet gets active runspaces in a PowerShell host process. ## EXAMPLES diff --git a/reference/6/Microsoft.PowerShell.Utility/Get-TraceSource.md b/reference/6/Microsoft.PowerShell.Utility/Get-TraceSource.md index e23cf8a2bf91..23fd04d8b674 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Get-TraceSource.md +++ b/reference/6/Microsoft.PowerShell.Utility/Get-TraceSource.md @@ -11,7 +11,7 @@ title: Get-TraceSource # Get-TraceSource ## SYNOPSIS -Gets Windows PowerShell components that are instrumented for tracing. +Gets PowerShell components that are instrumented for tracing. ## SYNTAX @@ -20,12 +20,12 @@ Get-TraceSource [[-Name] ] [] ``` ## DESCRIPTION -The **Get-TraceSource** cmdlet gets the trace sources for Windows PowerShell components that are currently in use. -You can use the data to determine which Windows PowerShell components you can trace. +The **Get-TraceSource** cmdlet gets the trace sources for PowerShell components that are currently in use. +You can use the data to determine which PowerShell components you can trace. When tracing, the component generates detailed messages about each step in its internal processing. Developers use the trace data to monitor data flow, program execution, and errors. -The tracing cmdlets were designed for Windows PowerShell developers, but they are available to all users. +The tracing cmdlets were designed for PowerShell developers, but they are available to all users. ## EXAMPLES @@ -41,7 +41,7 @@ This command gets all of the trace sources that have names that include provider PS C:\> Get-TraceSource ``` -This command gets all of the Windows PowerShell components that can be traced. +This command gets all of the PowerShell components that can be traced. ## PARAMETERS diff --git a/reference/6/Microsoft.PowerShell.Utility/Get-TypeData.md b/reference/6/Microsoft.PowerShell.Utility/Get-TypeData.md index 06d4e3ec0eac..a1eb66974015 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Get-TypeData.md +++ b/reference/6/Microsoft.PowerShell.Utility/Get-TypeData.md @@ -25,9 +25,9 @@ This includes type data that was added to the session by Types.ps1xml file and d You can use the extended type data that **Get-TypeData** returns to examine the type data in the session and send it to the **Update-TypeData** and **Remove-TypeData** cmdlets. -Extended type data adds properties and methods to objects in Windows PowerShell. +Extended type data adds properties and methods to objects in PowerShell. You can use the added properties and methods in the same ways that you would use the properties and methods that are defined in the object type. -However, when writing scripts, be aware that the added properties and methods might not be present in every Windows PowerShell session. +However, when writing scripts, be aware that the added properties and methods might not be present in every PowerShell session. For more information about Types.ps1xml files, see about_Types.ps1xml (http://go.microsoft.com/fwlink/?LinkID=113274). For more information about dynamic type data that the **Update-TypeData** cmdlet adds, see Update-TypeData. @@ -83,7 +83,7 @@ else } ``` -This command gets the script block that defines the **DateTime** property of **System.DateTime** objects in Windows PowerShell. +This command gets the script block that defines the **DateTime** property of **System.DateTime** objects in PowerShell. The command uses the **Get-TypeData** cmdlet to get the extended type data for the **System.DataTime** type. The command gets the Members property of the **TypeData** object. @@ -93,7 +93,7 @@ Each key in the Members hash table is a property or method name and each value i The command gets the **DateTime** key in Members and its GetScriptBlock property value. -The output shows the script block that creates the value of the DateTime property of every **System.DateTime** object in Windows PowerShell. +The output shows the script block that creates the value of the DateTime property of every **System.DateTime** object in PowerShell. ### Example 5: Find the file that adds extended data types to the session ``` @@ -111,7 +111,7 @@ C:\WINDOWS\System32\WindowsPowerShell\v1.0\types.ps1xml:433: ``` This command finds the Types.ps1xml file that added extended type data for the **EventLogEntry** type to the session. -This command uses the Get-ChildItem cmdlet (alias = "dir") to perform a recursive search for Types.ps1xml files in the Windows PowerShell installation directory ($pshome) and its subdirectories. +This command uses the Get-ChildItem cmdlet (alias = "dir") to perform a recursive search for Types.ps1xml files in the PowerShell installation directory ($pshome) and its subdirectories. The command sends the Types.ps1xml files to the Select-String cmdlet, which does a full-text search for the "**EventLogEntry**" type name in the files and returns the matches. ## PARAMETERS diff --git a/reference/6/Microsoft.PowerShell.Utility/Get-Variable.md b/reference/6/Microsoft.PowerShell.Utility/Get-Variable.md index 5f88ca7ccfa4..e97c2bf60bd9 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Get-Variable.md +++ b/reference/6/Microsoft.PowerShell.Utility/Get-Variable.md @@ -21,7 +21,7 @@ Get-Variable [[-Name] ] [-ValueOnly] [-Include ] [-Exclude < ``` ## DESCRIPTION -The **Get-Variable** cmdlet gets the Windows PowerShell variables in the current console. +The **Get-Variable** cmdlet gets the PowerShell variables in the current console. You can retrieve just the values of the variables by specifying the *ValueOnly* parameter, and you can filter the variables returned by name. ## EXAMPLES diff --git a/reference/6/Microsoft.PowerShell.Utility/Get-Verb.md b/reference/6/Microsoft.PowerShell.Utility/Get-Verb.md index 645926b109e6..77d205e49a6c 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Get-Verb.md +++ b/reference/6/Microsoft.PowerShell.Utility/Get-Verb.md @@ -10,7 +10,7 @@ external help file: Microsoft.PowerShell.Commands.Utility.dll-Help.xml # Get-Verb ## SYNOPSIS -Gets approved Windows PowerShell verbs. +Gets approved PowerShell verbs. ## SYNTAX @@ -19,16 +19,16 @@ Get-Verb [[-Verb] ] [[-Group] ] [] ``` ## DESCRIPTION -The Get-Verb function gets verbs that are approved for use in Windows PowerShell commands. +The Get-Verb function gets verbs that are approved for use in PowerShell commands. -Windows PowerShell recommends that cmdlet and function names have the Verb-Noun format and include an approved verb. +PowerShell recommends that cmdlet and function names have the Verb-Noun format and include an approved verb. This practice makes command names more consistent and predictable, and easier to use, especially for users who do not speak English as a first language. -Commands that use unapproved verbs run in Windows PowerShell. +Commands that use unapproved verbs run in PowerShell. However, when you import a module that includes a command with an unapproved verb in its name, the Import-Module command displays a warning message. NOTE: The verb list that Get-Verb returns might not be complete. -For an updated list of approved Windows PowerShell verbs with descriptions, see "Cmdlet Verbs" in MSDN at http://go.microsoft.com/fwlink/?LinkID=160773. +For an updated list of approved PowerShell verbs with descriptions, see "Cmdlet Verbs" in MSDN at http://go.microsoft.com/fwlink/?LinkID=160773. ## EXAMPLES @@ -137,11 +137,11 @@ Accept wildcard characters: False ### System.Management.Automation.VerbInfo ## NOTES -Windows PowerShell verbs are assigned to a group based on their most common use. +PowerShell verbs are assigned to a group based on their most common use. The groups are designed to make the verbs easy to find and compare, not to restrict their use. You can use any approved verb for any type of command. -Each Windows PowerShell verb is assigned to one of the following groups. +Each PowerShell verb is assigned to one of the following groups. -- Common: Define generic actions that can apply to almost any cmdlet, such as Add. -- Communications: Define actions that apply to communications, such as Connect. @@ -151,7 +151,7 @@ Each Windows PowerShell verb is assigned to one of the following groups. -- Security: Define actions that apply to security, such as Revoke. -- Other: Define other types of actions. -Some of the cmdlets that are installed with Windows PowerShell, such as Tee-Object and Where-Object, use unapproved verbs. +Some of the cmdlets that are installed with PowerShell, such as Tee-Object and Where-Object, use unapproved verbs. These cmdlets are considered to be historic exceptions and their verbs are classified as "reserved." ## RELATED LINKS diff --git a/reference/6/Microsoft.PowerShell.Utility/Import-Alias.md b/reference/6/Microsoft.PowerShell.Utility/Import-Alias.md index fe987145a9bf..b98a7cf5b743 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Import-Alias.md +++ b/reference/6/Microsoft.PowerShell.Utility/Import-Alias.md @@ -123,7 +123,7 @@ Specifies the path to a file that includes exported alias information. Unlike the **Path** parameter, the value of the **LiteralPath** parameter is used exactly as it is typed. No characters are interpreted as wildcards. If the path includes escape characters, enclose it in single quotation marks. -Single quotation marks tell Windows PowerShell not to interpret any characters as escape sequences. +Single quotation marks tell PowerShell not to interpret any characters as escape sequences. ```yaml Type: String diff --git a/reference/6/Microsoft.PowerShell.Utility/Import-Clixml.md b/reference/6/Microsoft.PowerShell.Utility/Import-Clixml.md index 596df4bb2265..d0e8d438dc4c 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Import-Clixml.md +++ b/reference/6/Microsoft.PowerShell.Utility/Import-Clixml.md @@ -11,7 +11,7 @@ title: Import-Clixml # Import-Clixml ## SYNOPSIS -Imports a CLIXML file and creates corresponding objects in Windows PowerShell. +Imports a CLIXML file and creates corresponding objects in PowerShell. ## SYNTAX @@ -26,7 +26,7 @@ Import-Clixml -LiteralPath [-IncludeTotalCount] [-Skip ] [-Fi ``` ## DESCRIPTION -The **Import-CliXml** cmdlet imports a CLIXML file with data that represents Microsoft .NET Framework objects and creates the objects in Windows PowerShell. +The **Import-CliXml** cmdlet imports a CLIXML file with data that represents Microsoft .NET Framework objects and creates the objects in PowerShell. A valuable use of **Import-CliXml** is to import credentials and secure strings that have been exported as secure XML by running the Export-Clixml cmdlet. For an example of how to do this, see Example 2. @@ -88,7 +88,7 @@ Specifies the XML files. Unlike *Path*, the value of the *LiteralPath* parameter is used exactly as it is typed. No characters are interpreted as wildcards. If the path includes escape characters, enclose it in single quotation marks. -Single quotation marks tell Windows PowerShell not to interpret any characters as escape sequences. +Single quotation marks tell PowerShell not to interpret any characters as escape sequences. ```yaml Type: String[] diff --git a/reference/6/Microsoft.PowerShell.Utility/Import-Csv.md b/reference/6/Microsoft.PowerShell.Utility/Import-Csv.md index d79da425ad16..9cef1e312c7a 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Import-Csv.md +++ b/reference/6/Microsoft.PowerShell.Utility/Import-Csv.md @@ -196,7 +196,7 @@ LinkID TopicTitle 113207 about_Aliases ``` -This example shows how to create a custom object in Windows PowerShell by using a CSV file. +This example shows how to create a custom object in PowerShell by using a CSV file. The first command uses the Get-Content cmdlet to get the Links.csv file. @@ -206,7 +206,7 @@ The third command uses the Get-Member cmdlet to get the type and members of the The output shows that **Import-Csv** returns a collection of custom objects (**PSCustomObject**). In addition to some default properties, the custom objects have "LinkId" and "TopicTitle" note properties. -This command shows that you can use the custom object like you would any object in Windows PowerShell. +This command shows that you can use the custom object like you would any object in PowerShell. The command pipes the custom objects in the $A variable to the **Where-Object** cmdlet, which gets only objects with a "TopicTitle" property that includes "alias". diff --git a/reference/6/Microsoft.PowerShell.Utility/Import-LocalizedData.md b/reference/6/Microsoft.PowerShell.Utility/Import-LocalizedData.md index b04f7dfb892e..032f076d33f0 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Import-LocalizedData.md +++ b/reference/6/Microsoft.PowerShell.Utility/Import-LocalizedData.md @@ -91,7 +91,7 @@ Msg3 = "Use $_ to represent the object that is being processed." Import-LocalizedData -BindingVariable "Messages" Write-Host $Messages.Msg2 -# In Windows PowerShell +# In PowerShell PS C:\> .\Test.ps1 diff --git a/reference/6/Microsoft.PowerShell.Utility/Import-PSSession.md b/reference/6/Microsoft.PowerShell.Utility/Import-PSSession.md index cd3a41a9e73c..5572d6784e23 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Import-PSSession.md +++ b/reference/6/Microsoft.PowerShell.Utility/Import-PSSession.md @@ -26,7 +26,7 @@ Import-PSSession [-Prefix ] [-DisableNameChecking] [[-CommandName] $S = New-PSSession -ComputerName Server01 PS C:\> Invoke-Command -Session $S {Import-Module TestManagement} PS C:\> Import-PSSession -Session $S -Module TestManagement ``` -This example shows how to import the cmdlets and functions from a Windows PowerShell module on a remote computer into the current session. +This example shows how to import the cmdlets and functions from a PowerShell module on a remote computer into the current session. The first command creates a PSSession on the Server01 computer and saves it in the $S variable. The second command uses the **Invoke-Command** cmdlet to run an Import-Module command in the PSSession in $S. -Typically, the module would be added to all sessions by an **Import-Module** command in a Windows PowerShell profile, but profiles are not run in PSSessions. +Typically, the module would be added to all sessions by an **Import-Module** command in a PowerShell profile, but profiles are not run in PSSessions. The third command uses the *Module* parameter of **Import-PSSession** to import the cmdlets and functions in the module into the current session. @@ -200,11 +200,11 @@ The output shows that the session includes the original **Get-Date** cmdlet and The **Get-Date** function runs the imported **Get-Date** cmdlet in the PSSession in $S. The third command runs a **Get-Date** command. -Because functions take precedence over cmdlets, Windows PowerShell runs the imported **Get-Date** function, which returns a Julian date. +Because functions take precedence over cmdlets, PowerShell runs the imported **Get-Date** function, which returns a Julian date. The fourth and fifth commands show how to use a qualified name to run a command that is hidden by an imported command. -The fourth command gets the name of the Windows PowerShell snap-in that added the original **Get-Date** cmdlet to the current session. +The fourth command gets the name of the PowerShell snap-in that added the original **Get-Date** cmdlet to the current session. The fifth command uses the snap-in-qualified name of the **Get-Date** cmdlet to run a **Get-Date** command. @@ -244,7 +244,7 @@ The **Import-PSSession** command returns a temporary module, and the command sav The second command uses the Get-Command cmdlet to get the commands that are exported by the module in the $M variable. The *Module* parameter takes a string value, which is designed for the module name. -However, when you submit a module object, Windows PowerShell uses the **ToString** method on the module object, which returns the module name. +However, when you submit a module object, PowerShell uses the **ToString** method on the module object, which returns the module name. The **Get-Command** command is the equivalent of `Get-Command $M.Name`". @@ -318,7 +318,7 @@ Use *CommandType* or its alias, *Type*. The acceptable values for this parameter are: - Alias. -The Windows PowerShell aliases in the remote session. +The PowerShell aliases in the remote session. - All. The cmdlets and functions in the remote session. - Application. @@ -329,7 +329,7 @@ The cmdlets in the remote session. - ExternalScript. The .ps1 files in the paths listed in the Path environment variable ($env:path) in the remote session. - Filter and Function. -The Windows PowerShell functions in the remote session. +The PowerShell functions in the remote session. - Script. The script blocks in the remote session. @@ -349,7 +349,7 @@ Accept wildcard characters: False ### -DisableNameChecking Indicates that this cmdlet suppresses the message that warns you when you import a cmdlet or function whose name includes an unapproved verb or a prohibited character. -By default, when a module that you import exports cmdlets or functions that have unapproved verbs in their names, the Windows PowerShell displays the following warning message: +By default, when a module that you import exports cmdlets or functions that have unapproved verbs in their names, the PowerShell displays the following warning message: "WARNING: Some imported command names include unapproved verbs which might make them less discoverable. Use the Verbose parameter for more detail or type Get-Verb to see the list of approved verbs." @@ -416,7 +416,7 @@ Accept wildcard characters: False ``` ### -Module -Specifies and array of commands in the Windows PowerShell snap-ins and modules. +Specifies and array of commands in the PowerShell snap-ins and modules. Enter the snap-in and module names. Wildcards are not permitted. @@ -509,14 +509,14 @@ However, the imported module is temporary and exists only in the current session To create a permanent module on disk, use the Export-PSSession cmdlet. ## NOTES -* **Import-PSSession** relies on the Windows PowerShell remoting infrastructure. To use this cmdlet, the computer must be configured for WS-Management remoting. For more information, see about_Remote and about_Remote_Requirements. -* **Import-PSSession** does not import variables or Windows PowerShell providers. +* **Import-PSSession** relies on the PowerShell remoting infrastructure. To use this cmdlet, the computer must be configured for WS-Management remoting. For more information, see about_Remote and about_Remote_Requirements. +* **Import-PSSession** does not import variables or PowerShell providers. * When you import commands that have the same names as commands in the current session, the imported commands can hide aliases, functions, and cmdlets in the session and they can replace functions and variables in the session. To prevent name conflicts, use the *Prefix* parameter. For more information, see about_Command_Precedence. * **Import-PSSession** converts all commands into functions before it imports them. As a result, imported commands behave a bit differently than they would if they retained their original command type. For example, if you import a cmdlet from a PSSession and then import a cmdlet with the same name from a module or snap-in, the cmdlet that is imported from the PSSession always runs by default because functions take precedence over cmdlets. Conversely, if you import an alias into a session that has an alias with the same name, the original alias is always used, because aliases take precedence over functions. For more information, see about_Command_Precedence. * **Import-PSSession** uses the Write-Progress cmdlet to display the progress of the command. You might see the progress bar while the command is running. * To find the commands to import, **Import-PSSession** uses the Invoke-Command cmdlet to run a Get-Command command in the PSSession. To get formatting data for the commands, it uses the Get-FormatData cmdlet. You might see error messages from these cmdlets when you run an **Import-PSSession** command. Also, **Import-PSSession** cannot import commands from a PSSession that does not include the Get-Command, Get-FormatData, Select-Object, and Get-Help cmdlets. * Imported commands have the same limitations as other remote commands, including the inability to start a program with a user interface, such as Notepad. -* Because Windows PowerShell profiles are not run in PSSessions, the commands that a profile adds to a session are not available to **Import-PSSession**. To import commands from a profile, use an Invoke-Command command to run the profile in the PSSession manually before importing commands. +* Because PowerShell profiles are not run in PSSessions, the commands that a profile adds to a session are not available to **Import-PSSession**. To import commands from a profile, use an Invoke-Command command to run the profile in the PSSession manually before importing commands. * The temporary module that **Import-PSSession** creates might include a formatting file, even if the command does not import formatting data. If the command does not import formatting data, any formatting files that are created will not contain formatting data. * To use **Import-PSSession**, the execution policy in the current session cannot be Restricted or AllSigned, because the temporary module that **Import-PSSession** creates contains unsigned script files that are prohibited by these policies. To use **Import-PSSession** without changing the execution policy for the local computer, use the *Scope* parameter of Set-ExecutionPolicy to set a less restrictive execution policy for a single process. * In Windows PowerShell 2.0, help topics for commands that are imported from another session do not include the prefix that you assign by using the *Prefix* parameter. To get help for an imported command in Windows PowerShell 2.0, use the original (non-prefixed) command name. diff --git a/reference/6/Microsoft.PowerShell.Utility/Invoke-Expression.md b/reference/6/Microsoft.PowerShell.Utility/Invoke-Expression.md index 9b1577b844f4..c458a6b8a444 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Invoke-Expression.md +++ b/reference/6/Microsoft.PowerShell.Utility/Invoke-Expression.md @@ -46,7 +46,7 @@ Without **Invoke-Expression**, the expression is printed, but not evaluated. The first command assigns a value of Get-Process (a string) to the $Command variable. The second command shows the effect of typing the variable name at the command line. -Windows PowerShell echoes the string. +PowerShell echoes the string. The third command uses **Invoke-Expression** to evaluate the string. @@ -120,7 +120,7 @@ Use the $Input automatic variable to represent the input objects in the command. Returns the output that is generated by the invoked command (the value of the *Command* parameter). ## NOTES -* An expression is a statement that can be evaluated and produces a result, such as a Windows PowerShell command. +* An expression is a statement that can be evaluated and produces a result, such as a PowerShell command. * Take reasonable precautions when using the **Invoke-Expression** cmdlet in scripts. When using **Invoke-Expression** to run a command that the user enters, verify that the command is safe to run before running it. In general, it is best to design your script with predefined input options, rather than allowing freeform input. ## RELATED LINKS \ No newline at end of file diff --git a/reference/6/Microsoft.PowerShell.Utility/Measure-Command.md b/reference/6/Microsoft.PowerShell.Utility/Measure-Command.md index 77a86a2ed873..90a80afc98ee 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Measure-Command.md +++ b/reference/6/Microsoft.PowerShell.Utility/Measure-Command.md @@ -40,7 +40,7 @@ The first command measures the time it takes to process a recursive `Get-ChildIt The second command measures the time it takes to process a recursive `Get-ChildItem` command that uses the provider-specific `-Filter` parameter. -These commands show the value of using a provider-specific filter in Windows PowerShell commands. +These commands show the value of using a provider-specific filter in PowerShell commands. ```powershell Measure-Command { Get-ChildItem -Path C:\Windows\*.txt -Recurse } diff --git a/reference/6/Microsoft.PowerShell.Utility/Microsoft.PowerShell.Utility.md b/reference/6/Microsoft.PowerShell.Utility/Microsoft.PowerShell.Utility.md index 4931d669b746..b3b3af1d6a55 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Microsoft.PowerShell.Utility.md +++ b/reference/6/Microsoft.PowerShell.Utility/Microsoft.PowerShell.Utility.md @@ -12,15 +12,15 @@ Module Name: Microsoft.PowerShell.Utility # Microsoft.PowerShell.Utility Module ## Description -This section contains the help topics for the cmdlets that are installed with Windows PowerShell® Utility module, Microsoft.PowerShell.Utility. The Utility module contains cmdlets that manage the basic features of Windows PowerShell. +This section contains the help topics for the cmdlets that are installed with PowerShell Utility module, Microsoft.PowerShell.Utility. The Utility module contains cmdlets that manage the basic features of PowerShell. ## Microsoft.PowerShell.Utility Cmdlets ### [Add-Member](Add-Member.md) -Adds custom properties and methods to an instance of a Windows PowerShell object. +Adds custom properties and methods to an instance of a PowerShell object. ### [Add-Type](Add-Type.md) -Adds a Microsoft .NET Framework type (a class) to a Windows PowerShell session. +Adds a Microsoft .NET Framework type (a class) to a PowerShell session. ### [Clear-Variable](Clear-Variable.md) @@ -100,7 +100,7 @@ Saves formatting data from the current session in a formatting file. ### [Export-PSSession](Export-PSSession.md) -Imports commands from another session and saves them in a Windows PowerShell module. +Imports commands from another session and saves them in a PowerShell module. ### [Format-Custom](Format-Custom.md) @@ -172,7 +172,7 @@ Gets a random number, or selects objects randomly from a collection. ### [Get-Runspace](Get-Runspace.md) -Gets active runspaces within a Windows PowerShellhost process. +Gets active runspaces within a PowerShellhost process. ### [Get-RunspaceDebug](Get-RunspaceDebug.md) @@ -180,7 +180,7 @@ Shows runspace debugging options. ### [Get-TraceSource](Get-TraceSource.md) -Gets Windows PowerShell components that are instrumented for tracing. +Gets PowerShell components that are instrumented for tracing. ### [Get-TypeData](Get-TypeData.md) @@ -211,7 +211,7 @@ Imports an alias list from a file. ### [Import-Clixml](Import-Clixml.md) -Imports a CLIXML file and creates corresponding objects in Windows PowerShell. +Imports a CLIXML file and creates corresponding objects in PowerShell. ### [Import-Csv](Import-Csv.md) @@ -290,7 +290,7 @@ Reads a line of input from the console. ### [Register-EngineEvent](Register-EngineEvent.md) -Subscribes to events that are generated by the Windows PowerShell engine and by the New-Event cmdlet. +Subscribes to events that are generated by the PowerShell engine and by the New-Event cmdlet. ### [Register-ObjectEvent](Register-ObjectEvent.md) @@ -326,7 +326,7 @@ Finds text in an XML string or document. ### [Set-Alias](Set-Alias.md) -Creates or changes an alias for a cmdlet or other command element in the current Windows PowerShell session. +Creates or changes an alias for a cmdlet or other command element in the current PowerShell session. ### [Set-Date](Set-Date.md) @@ -338,7 +338,7 @@ Sets a breakpoint on a line, command, or variable. ### [Set-TraceSource](Set-TraceSource.md) -Configures, starts, and stops a trace of Windows PowerShell components. +Configures, starts, and stops a trace of PowerShell components. ### [Set-Variable](Set-Variable.md) @@ -398,7 +398,7 @@ Writes customized output to a host. ### [Write-Information](Write-Information.md) -Specifies how Windows PowerShell handles information stream data for a command. +Specifies how PowerShell handles information stream data for a command. ### [Write-Output](Write-Output.md) @@ -406,7 +406,7 @@ Sends the specified objects to the next command in the pipeline. ### [Write-Progress](Write-Progress.md) -Displays a progress bar within a Windows PowerShell command window. +Displays a progress bar within a PowerShell command window. ### [Write-Verbose](Write-Verbose.md) diff --git a/reference/6/Microsoft.PowerShell.Utility/New-Alias.md b/reference/6/Microsoft.PowerShell.Utility/New-Alias.md index 2a980bd51ee9..f4517ccbc785 100644 --- a/reference/6/Microsoft.PowerShell.Utility/New-Alias.md +++ b/reference/6/Microsoft.PowerShell.Utility/New-Alias.md @@ -21,8 +21,8 @@ New-Alias [-Name] [-Value] [-Description ] [-Option New-Event -SourceIdentifier Timer -Sender windows.timer -MessageData "Test" ``` -This command creates a new event in the Windows PowerShell event queue. +This command creates a new event in the PowerShell event queue. It uses a **Windows.Timer** object to send the event. ### Example 2: Raise an event in response to another event @@ -60,7 +60,7 @@ This sample function uses the **New-Event** cmdlet to raise an event in response The command uses the Register-ObjectEvent cmdlet to subscribe to the Windows Management Instrumentation (WMI) event that is raised when a new process is created. The command uses the *Action* parameter of the cmdlet to call the **New-Event** cmdlet, which creates the new event. -Because the events that **New-Event** raises are automatically added to the Windows PowerShellevent queue, you do not need to register for that event. +Because the events that **New-Event** raises are automatically added to the PowerShell event queue, you do not need to register for that event. ## PARAMETERS @@ -97,7 +97,7 @@ Accept wildcard characters: False ### -Sender Specifies the object that raises the event. -The default is the Windows PowerShell engine. +The default is the PowerShell engine. ```yaml Type: PSObject diff --git a/reference/6/Microsoft.PowerShell.Utility/New-Object.md b/reference/6/Microsoft.PowerShell.Utility/New-Object.md index 3c89b28bb76f..a0dbdda6f02b 100644 --- a/reference/6/Microsoft.PowerShell.Utility/New-Object.md +++ b/reference/6/Microsoft.PowerShell.Utility/New-Object.md @@ -238,7 +238,7 @@ You cannot pipe input to this cmdlet. **New-Object** returns the object that is created. ## NOTES -* **New-Object** provides the most commonly-used functionality of the VBScript CreateObject function. A statement like `Set objShell = CreateObject("Shell.Application")` in VBScript can be translated to `$objShell = New-Object -COMObject "Shell.Application"` in Windows PowerShell. +* **New-Object** provides the most commonly-used functionality of the VBScript CreateObject function. A statement like `Set objShell = CreateObject("Shell.Application")` in VBScript can be translated to `$objShell = New-Object -COMObject "Shell.Application"` in PowerShell. * **New-Object** expands upon the functionality available in the Windows Script Host environment by making it easy to work with .NET Framework objects from the command line and within scripts. ## RELATED LINKS diff --git a/reference/6/Microsoft.PowerShell.Utility/New-TimeSpan.md b/reference/6/Microsoft.PowerShell.Utility/New-TimeSpan.md index f8aa78b8205d..79744b336eca 100644 --- a/reference/6/Microsoft.PowerShell.Utility/New-TimeSpan.md +++ b/reference/6/Microsoft.PowerShell.Utility/New-TimeSpan.md @@ -80,7 +80,7 @@ This command tells you how long it has been since the about_remote.help.txt file You can use this command format on any file, and on any other object that has a **LastWriteTime** property. This command works because the *Start* parameter of **New-TimeSpan** has an alias of LastWriteTime. -When you pipe an object that has a **LastWriteTime** property to **New-TimeSpan**, Windows PowerShell uses the value of the **LastWriteTime** property as the value of the *Start* parameter. +When you pipe an object that has a **LastWriteTime** property to **New-TimeSpan**, PowerShell uses the value of the **LastWriteTime** property as the value of the *Start* parameter. ## PARAMETERS diff --git a/reference/6/Microsoft.PowerShell.Utility/New-Variable.md b/reference/6/Microsoft.PowerShell.Utility/New-Variable.md index 110c849fe181..1e851bd54ca3 100644 --- a/reference/6/Microsoft.PowerShell.Utility/New-Variable.md +++ b/reference/6/Microsoft.PowerShell.Utility/New-Variable.md @@ -22,7 +22,7 @@ New-Variable [-Name] [[-Value] ] [-Description ] [-Opti ``` ## DESCRIPTION -The **New-Variable** cmdlet creates a new variable in Windows PowerShell. +The **New-Variable** cmdlet creates a new variable in PowerShell. You can assign a value to the variable while creating it or assign or change the value after it is created. You can use the parameters of **New-Variable** to set the properties of the variable, set the scope of a variable, and determine whether variables are public or private. diff --git a/reference/6/Microsoft.PowerShell.Utility/Out-File.md b/reference/6/Microsoft.PowerShell.Utility/Out-File.md index 31c2b6c10583..d73f5ffc1fa4 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Out-File.md +++ b/reference/6/Microsoft.PowerShell.Utility/Out-File.md @@ -293,7 +293,7 @@ Accept wildcard characters: False Specifies the number of characters in each line of output. Any additional characters are truncated, not wrapped. If you omit this parameter, the width is determined by the characteristics of the host. -The default for the Windows PowerShell console is 80 characters. +The default for the PowerShell console is 80 characters. ```yaml Type: Int32 diff --git a/reference/6/Microsoft.PowerShell.Utility/Read-Host.md b/reference/6/Microsoft.PowerShell.Utility/Read-Host.md index f32d624c1956..a65a4eae6f4c 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Read-Host.md +++ b/reference/6/Microsoft.PowerShell.Utility/Read-Host.md @@ -66,7 +66,7 @@ Accept wildcard characters: False Specifies the text of the prompt. Type a string. If the string includes spaces, enclose it in quotation marks. -Windows PowerShell appends a colon (:) to the text that you enter. +PowerShell appends a colon (:) to the text that you enter. ```yaml Type: Object diff --git a/reference/6/Microsoft.PowerShell.Utility/Register-EngineEvent.md b/reference/6/Microsoft.PowerShell.Utility/Register-EngineEvent.md index 688ff3c91095..15cc8b96853a 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Register-EngineEvent.md +++ b/reference/6/Microsoft.PowerShell.Utility/Register-EngineEvent.md @@ -11,7 +11,7 @@ title: Register-EngineEvent # Register-EngineEvent ## SYNOPSIS -Subscribes to events that are generated by the Windows PowerShell engine and by the New-Event cmdlet. +Subscribes to events that are generated by the PowerShell engine and by the New-Event cmdlet. ## SYNTAX @@ -21,7 +21,7 @@ Register-EngineEvent [-SourceIdentifier] [[-Action] ] [-Me ``` ## DESCRIPTION -The **Register-EngineEvent** cmdlet subscribes to events that are generated by the Windows PowerShell engine and the New-Event cmdlet. +The **Register-EngineEvent** cmdlet subscribes to events that are generated by the PowerShell engine and the New-Event cmdlet. Use the *SourceIdentifier* parameter to specify the event. You can use this cmdlet to subscribe to the Exiting engine event and events generated by the New-Event cmdlet. @@ -43,7 +43,7 @@ PS C:\> $S = New-PSSession -ComputerName "Server01, Server02" PS C:\> Invoke-Command -Session $S { Register-EngineEvent -SourceIdentifier ([System.Management.Automation.PsEngineEvent]::Exiting) -Forward } ``` -This command registers for a Windows PowerShell engine event on two remote computers. +This command registers for a PowerShell engine event on two remote computers. The first command creates a user-managed session (PSSession) on each of the remote computers. @@ -61,7 +61,7 @@ PS C:\> Register-EngineEvent -SourceIdentifier PowerShell.Exiting -SupportEvent This command shows how to run **Register-EngineEvent** to take a specific action when the **PowerShell.Exiting** event occurs. The *SupportEvent* parameter is added to hide the event subscription. -When Windows PowerShell exits, in this case, the command history from the exiting session is exported in XML format to a file name and path in the user's $Home directory. +When PowerShell exits, in this case, the command history from the exiting session is exported in XML format to a file name and path in the user's $Home directory. ## PARAMETERS diff --git a/reference/6/Microsoft.PowerShell.Utility/Register-ObjectEvent.md b/reference/6/Microsoft.PowerShell.Utility/Register-ObjectEvent.md index a3fa5bb64726..8d142ef404a9 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Register-ObjectEvent.md +++ b/reference/6/Microsoft.PowerShell.Utility/Register-ObjectEvent.md @@ -262,7 +262,7 @@ Accept wildcard characters: False ### -SourceIdentifier Specifies a name that you select for the subscription. The name that you select must be unique in the current session. -The default value is the GUID that Windows PowerShell assigns. +The default value is the GUID that PowerShell assigns. The value of this parameter appears in the value of the SourceIdentifier property of the subcriber object and of all event objects associated with this subscription. diff --git a/reference/6/Microsoft.PowerShell.Utility/Remove-PSBreakpoint.md b/reference/6/Microsoft.PowerShell.Utility/Remove-PSBreakpoint.md index 7389f2ffe6dc..d695a0b42260 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Remove-PSBreakpoint.md +++ b/reference/6/Microsoft.PowerShell.Utility/Remove-PSBreakpoint.md @@ -32,8 +32,8 @@ Enter a breakpoint object or a breakpoint ID. When you remove a breakpoint, the breakpoint object is no longer available or functional. If you have saved a breakpoint object in a variable, the reference still exists, but the breakpoint does not function. -**Remove-PSBreakpoint** is one of several cmdlets designed for debugging Windows PowerShell scripts. -For more information about the Windows PowerShell debugger, see about_Debuggers. +**Remove-PSBreakpoint** is one of several cmdlets designed for debugging PowerShell scripts. +For more information about the PowerShell debugger, see about_Debuggers. ## EXAMPLES @@ -79,7 +79,7 @@ Then, it uses a pipeline operator (|) to send the breakpoints to the **Remove-PS As a result, you can type `del-psb` instead of the longer command. -To save the function, add it to your Windows PowerShell profile. +To save the function, add it to your PowerShell profile. ## PARAMETERS diff --git a/reference/6/Microsoft.PowerShell.Utility/Remove-TypeData.md b/reference/6/Microsoft.PowerShell.Utility/Remove-TypeData.md index 22a8e6aabd02..8dab640c1752 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Remove-TypeData.md +++ b/reference/6/Microsoft.PowerShell.Utility/Remove-TypeData.md @@ -34,7 +34,7 @@ Remove-TypeData -Path [-WhatIf] [-Confirm] [] The **Remove-TypeData** cmdlet deletes extended type data from the current session. This cmdlet affects only the current session and sessions that are created in the current session. -You can add properties and methods to objects in Windows PowerShell by defining them in Update-TypeData commands and Types.ps1xml files. +You can add properties and methods to objects in PowerShell by defining them in Update-TypeData commands and Types.ps1xml files. **Remove-TypeData** deletes those extended properties and methods from the current session. **Remove-TypeData** does not delete the Types.ps1xml files or delete any extended type definitions from the Types.ps1xml files. For more information about Types.ps1xml files, see about_Types.ps1xml (http://go.microsoft.com/fwlink/?LinkID=113274). @@ -52,7 +52,7 @@ This command deletes from the session all type data for the **System.Array** typ ### Example 2: Remove an extended data type from a session ``` -The first command uses the Get-TypeData cmdlet to get extended type data for the **System.DateTime** type.The output shows that a **DateTime** property has been added to all **System.DateTime** objects in Windows PowerShell. +The first command uses the Get-TypeData cmdlet to get extended type data for the **System.DateTime** type.The output shows that a **DateTime** property has been added to all **System.DateTime** objects in PowerShell. PS C:\> Get-TypeData System.DateTime TypeName Members -------- ------- diff --git a/reference/6/Microsoft.PowerShell.Utility/Remove-Variable.md b/reference/6/Microsoft.PowerShell.Utility/Remove-Variable.md index 16ff7d1c3dd6..5d6d3e837e78 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Remove-Variable.md +++ b/reference/6/Microsoft.PowerShell.Utility/Remove-Variable.md @@ -172,7 +172,7 @@ You can pipe a variable object to **Remove-Variable**. This cmdlet does not return any output. ## NOTES -* Changes affect only the current scope, such as a session. To delete a variable from all sessions, add a **Remove-Variable** command to your Windows PowerShell profile. +* Changes affect only the current scope, such as a session. To delete a variable from all sessions, add a **Remove-Variable** command to your PowerShell profile. You can also refer to **Remove-Variable** by its built-in alias, **rv**. For more information, see about_Aliases. diff --git a/reference/6/Microsoft.PowerShell.Utility/Select-Object.md b/reference/6/Microsoft.PowerShell.Utility/Select-Object.md index 642dbf503cec..2bcf7f09122b 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Select-Object.md +++ b/reference/6/Microsoft.PowerShell.Utility/Select-Object.md @@ -48,7 +48,7 @@ To select object properties, use the **Property** parameter. When you select properties, `Select-Object` returns new objects that have only the specified properties. Beginning in Windows PowerShell 3.0, `Select-Object` includes an optimization feature that prevents commands from creating and processing objects that are not used. -When you include a `Select-Object` command with the **First** or **Index** parameters in a command pipeline, Windows PowerShell stops the command that generates the objects as soon as the selected number of objects is generated, even when the command that generates the objects appears before the `Select-Object` command in the pipeline. +When you include a `Select-Object` command with the **First** or **Index** parameters in a command pipeline, PowerShell stops the command that generates the objects as soon as the selected number of objects is generated, even when the command that generates the objects appears before the `Select-Object` command in the pipeline. To turn off this optimizing behavior, use the **Wait** parameter. ## EXAMPLES @@ -192,7 +192,7 @@ The command uses the **ReadOnly** dynamic parameter of the `Get-ChildItem` for F It uses a pipeline operator (|) to send the files to the `Rename-Item` cmdlet, which renames the file. It uses the **Passthru** parameter of `Rename-Item` to send the renamed files to the `Select-Object` cmdlet, which selects the first 5 for display. -The **Wait** parameter of `Select-Object` prevents Windows PowerShell from stopping the `Get-ChildItem` cmdlet after it gets the first five read-only text files. +The **Wait** parameter of `Select-Object` prevents PowerShell from stopping the `Get-ChildItem` cmdlet after it gets the first five read-only text files. Without this parameter, only the first five read-only files would be renamed. ### Example 9: Demonstrate the intricacies of the -ExpandProperty parameter @@ -440,8 +440,8 @@ Accept wildcard characters: False ### -Wait Indicates that the cmdlet turns off optimization. -Windows PowerShell runs commands in the order that they appear in the command pipeline and lets them generate all objects. -By default, if you include a `Select-Object` command with the **First** or **Index** parameters in a command pipeline, Windows PowerShell stops the command that generates the objects as soon as the selected number of objects is generated. +PowerShell runs commands in the order that they appear in the command pipeline and lets them generate all objects. +By default, if you include a `Select-Object` command with the **First** or **Index** parameters in a command pipeline, PowerShell stops the command that generates the objects as soon as the selected number of objects is generated. This parameter was introduced in Windows PowerShell 3.0. diff --git a/reference/6/Microsoft.PowerShell.Utility/Select-String.md b/reference/6/Microsoft.PowerShell.Utility/Select-String.md index 263ab67c2204..02d2438903c5 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Select-String.md +++ b/reference/6/Microsoft.PowerShell.Utility/Select-String.md @@ -84,10 +84,10 @@ This command searches through all files with the .xml file name extension in the PS C:\> Select-String -Path "$pshome\en-US\*.txt" -Pattern "@" ``` -This command searches the Windows PowerShell conceptual Help files (about_*.txt) for information about the use of the at sign (@). +This command searches the PowerShell conceptual Help files (about_*.txt) for information about the use of the at sign (@). -To indicate the path, this command uses the value of the $pshome automatic variable, which stores the path to the Windows PowerShell installation directory. -In this example, the command searches the en-US subdirectory, which contains the English (US) language Help files for Windows PowerShell. +To indicate the path, this command uses the value of the $pshome automatic variable, which stores the path to the PowerShell installation directory. +In this example, the command searches the en-US subdirectory, which contains the English (US) language Help files for PowerShell. ### Example 4: Use Select-String in a function @@ -99,12 +99,12 @@ PS C:\> function search-help } ``` -This simple function uses the **Select-String** cmdlet to search the Windows PowerShell Help files for a particular string. +This simple function uses the **Select-String** cmdlet to search the PowerShell Help files for a particular string. In this example, the function searches the "en-US" subdirectory for English-United States language files. To use the function to find a string, such as "psdrive", type `search-help psdrive`. -To use this function in any Windows PowerShell console, change the path to point to the Windows PowerShell Help files on your system, and then paste the function in your Windows PowerShell profile. +To use this function in any PowerShell console, change the path to point to the PowerShell Help files on your system, and then paste the function in your PowerShell profile. ### Example 5: Search for a string in the Application log @@ -201,7 +201,7 @@ Value : Transcript This example demonstrates the effect of the *AllMatches* parameter of **Select-String**. *AllMatches* finds all pattern matches in a line, instead of just finding the first match in each line. -The first command in the example searches the Windows PowerShell conceptual Help files ("about" Help) for instances of the word "transcript". +The first command in the example searches the PowerShell conceptual Help files ("about" Help) for instances of the word "transcript". The output of the first command is saved in the $A variable. The second command is identical, except that it uses the *AllMatches* parameter. @@ -490,7 +490,7 @@ Specifies the path to the files to be searched. Unlike **Path**, the value of the **LiteralPath** parameter is used exactly as it is typed. No characters are interpreted as wildcards. If the path includes escape characters, enclose it in single quotation marks. -Single quotation marks tell Windows PowerShell not to interpret any characters as escape sequences. +Single quotation marks tell PowerShell not to interpret any characters as escape sequences. ```yaml Type: String[] diff --git a/reference/6/Microsoft.PowerShell.Utility/Select-Xml.md b/reference/6/Microsoft.PowerShell.Utility/Select-Xml.md index 44fea8d3c087..6170832079d6 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Select-Xml.md +++ b/reference/6/Microsoft.PowerShell.Utility/Select-Xml.md @@ -123,7 +123,7 @@ Checkpoint-Computer C:\Windows\system32\WindowsPowerShell\v1.0\en-us\Microso ... ``` -This example shows how to use the **Select-Xml** cmdlet to search the Windows PowerShell XML-based cmdlet help files. +This example shows how to use the **Select-Xml** cmdlet to search the PowerShell XML-based cmdlet help files. In this example, we'll search for the cmdlet name that serves as a title for each help file and the path to the help file. The first command creates a hash table that represents the XML namespace that is used for the help files and saves it in the $Namespace variable. @@ -279,7 +279,7 @@ Specifies the paths and file names of the XML files to search. Unlike *Path*, the value of the *LiteralPath* parameter is used exactly as it is typed. No characters are interpreted as wildcards. If the path includes escape characters, enclose it in single quotation marks. -Single quotation marks tell Windows PowerShell not to interpret any characters as escape sequences. +Single quotation marks tell PowerShell not to interpret any characters as escape sequences. ```yaml Type: String[] diff --git a/reference/6/Microsoft.PowerShell.Utility/Set-Alias.md b/reference/6/Microsoft.PowerShell.Utility/Set-Alias.md index 8db4c595f387..ff8784ceaa4b 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Set-Alias.md +++ b/reference/6/Microsoft.PowerShell.Utility/Set-Alias.md @@ -11,7 +11,7 @@ title: Set-Alias # Set-Alias ## SYNOPSIS -Creates or changes an alias for a cmdlet or other command element in the current Windows PowerShell session. +Creates or changes an alias for a cmdlet or other command element in the current PowerShell session. ## SYNTAX @@ -23,7 +23,7 @@ Set-Alias [-Name] [-Value] [-Description ] [-Option Set-Alias scrub Remove-Item -Option ReadOnly -Passthru | Format-List This command associates the alias **scrub** with the **Remove-Item** cmdlet. It uses the ReadOnly option to prevent the alias from being deleted or assigned to another cmdlet. -The *PassThru* parameter directs Windows PowerShell to pass an object that represents the new alias through the pipeline to the Format-List cmdlet. +The *PassThru* parameter directs PowerShell to pass an object that represents the new alias through the pipeline to the Format-List cmdlet. If the *PassThru* parameter were omitted, there would be no output from this cmdlet to display (in a list or otherwise). ### Example 4: Create an alias for Notepad.exe @@ -64,7 +64,7 @@ PS C:\> Set-Alias np c:\windows\notepad.exe ``` This command associates the alias, **np**, with the executable file for Notepad. -After the command completes, to open Notepad from the Windows PowerShell command line, just type `np`. +After the command completes, to open Notepad from the PowerShell command line, just type `np`. This example demonstrates that you can create aliases for executable files and elements other than cmdlets. @@ -279,7 +279,7 @@ Otherwise, this cmdlet does not generate any output. * To create a new alias, use **Set-Alias** or New-Alias. To delete an alias, use Remove-Item. * A cmdlet can have multiple aliases, but an alias can only be associated with one cmdlet at a time. If you use **Set-Alias** to associate the alias with a different cmdlet, it is no longer associated with the original cmdlet. * You can create an alias for a cmdlet, but you cannot create an alias for a command with parameters and values. For example, you can create an alias for **Set-Location**, but you cannot create an alias for `Set-Location C:\Windows\System32`. To create an alias for a command, create a function that includes the command, and then create an alias to the function. -* To save the aliases from a session and use them in a different session, add the **Set-Alias** command to your Windows PowerShell profile. Profiles do not exist by default. To create a profile in the path stored in the $profile variable, type `New-Item -Type file -Force $profile`. To see the value of the $profile variable, type `$profile`. +* To save the aliases from a session and use them in a different session, add the **Set-Alias** command to your PowerShell profile. Profiles do not exist by default. To create a profile in the path stored in the $profile variable, type `New-Item -Type file -Force $profile`. To see the value of the $profile variable, type `$profile`. * You can also save your aliases by using Export-Alias to copy the aliases from the session to a file, and then use Import-Alias to add them to the alias list for a new session. * You can also refer to **Set-Alias** by its built-in alias, **sal**. For more information, see about_Aliases. diff --git a/reference/6/Microsoft.PowerShell.Utility/Set-PSBreakpoint.md b/reference/6/Microsoft.PowerShell.Utility/Set-PSBreakpoint.md index 1e04f2792d1b..a5d868459beb 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Set-PSBreakpoint.md +++ b/reference/6/Microsoft.PowerShell.Utility/Set-PSBreakpoint.md @@ -48,12 +48,12 @@ Each **Set-PSBreakpoint** command creates one of the following three types of br You can set a breakpoint on multiple lines, commands, or variables in a single **Set-PSBreakpoint** command, but each **Set-PSBreakpoint** command sets only one type of breakpoint. -At a breakpoint, Windows PowerShell temporarily stops executing and gives control to the debugger. +At a breakpoint, PowerShell temporarily stops executing and gives control to the debugger. The command prompt changes to `DBG\>`, and a set of debugger commands become available for use. However, you can use the *Action* parameter to specify an alternate response, such as conditions for the breakpoint or instructions to perform additional tasks such as logging or diagnostics. -The **Set-PSBreakpoint** cmdlet is one of several cmdlets designed for debugging Windows PowerShell scripts. -For more information about the Windows PowerShell debugger, see about_Debuggers. +The **Set-PSBreakpoint** cmdlet is one of several cmdlets designed for debugging PowerShell scripts. +For more information about the PowerShell debugger, see about_Debuggers. ## EXAMPLES @@ -214,7 +214,7 @@ The default is column 1. The Column value is used with the value of the Line parameter to specify the breakpoint. If the Line parameter specifies multiple lines, the *Column* parameter sets a breakpoint at the specified column on each of the specified lines. -Windows PowerShell stops executing before the statement or expression that includes the character at the specified line and column position. +PowerShell stops executing before the statement or expression that includes the character at the specified line and column position. Columns are counted from the top left margin beginning with column number 1 (not 0). If you specify a column that does not exist in the script, an error is not declared, but the breakpoint is never executed. @@ -254,7 +254,7 @@ Accept wildcard characters: False ### -Line Sets a line breakpoint in a script. Enter one or more line numbers, separated by commas. -Windows PowerShell stops immediately before executing the statement that begins on each of the specified lines. +PowerShell stops immediately before executing the statement that begins on each of the specified lines. Lines are counted from the top left margin of the script file beginning with line number 1 (not 0). If you specify a blank line, execution stops before the next non-blank line. diff --git a/reference/6/Microsoft.PowerShell.Utility/Set-TraceSource.md b/reference/6/Microsoft.PowerShell.Utility/Set-TraceSource.md index 0cd3f211c3e8..87753c77a938 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Set-TraceSource.md +++ b/reference/6/Microsoft.PowerShell.Utility/Set-TraceSource.md @@ -11,7 +11,7 @@ title: Set-TraceSource # Set-TraceSource ## SYNOPSIS -Configures, starts, and stops a trace of Windows PowerShell components. +Configures, starts, and stops a trace of PowerShell components. ## SYNTAX @@ -32,7 +32,7 @@ Set-TraceSource [-Name] [-RemoveFileListener ] [ Set-TraceSource -Name "ParameterBinding" -Option ExecutionFlow -PSHost -ListenerOption "ProcessId,TimeStamp" ``` -This command starts tracing for the ParameterBinding component of Windows PowerShell. -It uses the *Name* parameter to specify the trace source, the *Option* parameter to select the ExecutionFlow trace events, and the *PSHost* parameter to select the Windows PowerShell host listener, which sends the output to the console. +This command starts tracing for the ParameterBinding component of PowerShell. +It uses the *Name* parameter to specify the trace source, the *Option* parameter to select the ExecutionFlow trace events, and the *PSHost* parameter to select the PowerShell host listener, which sends the output to the console. The *ListenerOption* parameter adds the ProcessID and TimeStamp values to the trace message prefix. ### Example 2: Stop a trace @@ -51,7 +51,7 @@ The *ListenerOption* parameter adds the ProcessID and TimeStamp values to the tr PS C:\> Set-TraceSource -Name "ParameterBinding" -RemoveListener "Host" ``` -This command stops the trace of the ParameterBinding component of Windows PowerShell. +This command stops the trace of the ParameterBinding component of PowerShell. It uses the *Name* parameter to identify the component that was being traced and the *RemoveListener* parameter to identify the trace listener. ## PARAMETERS @@ -200,7 +200,7 @@ Accept wildcard characters: False ``` ### -PSHost -ndicates that this cmdlet sends the trace output to the Windows PowerShell host. +ndicates that this cmdlet sends the trace output to the PowerShell host. This parameter also selects the PSHost trace listener. ```yaml @@ -287,10 +287,10 @@ Otherwise, this cmdlet does not generate any output. ## NOTES * Tracing is a method that developers use to debug and refine programs. When tracing, the program generates detailed messages about each step in its internal processing. - The Windows PowerShell tracing cmdlets are designed to help Windows PowerShell developers, but they are available to all users. -They let you monitor nearly every aspect of the functionality of Windows PowerShell. + The PowerShell tracing cmdlets are designed to help PowerShell developers, but they are available to all users. +They let you monitor nearly every aspect of the functionality of PowerShell. - A trace source is the part of each Windows PowerShell component that manages tracing and generates trace messages for the component. + A trace source is the part of each PowerShell component that manages tracing and generates trace messages for the component. To trace a component, you identify its trace source. A trace listener receives the output of the trace and displays it to the user. @@ -301,7 +301,7 @@ You can elect to send the trace data to a user-mode or kernel-mode debugger, to * To start a trace, use the *Name* parameter to specify a trace source and the *FilePath*, *Debugger*, or *PSHost* parameters to specify a listener (a destination for the output). Use the *Options* parameter to determine the types of events that are traced and the *ListenerOption* parameter to configure the trace output. -* To change the configuration of a trace, enter a **Set-TraceSource** command as you would to start a trace. Windows PowerShell recognizes that the trace source is already being traced. It stops the trace, adds the new configuration, and starts or restarts the trace. +* To change the configuration of a trace, enter a **Set-TraceSource** command as you would to start a trace. PowerShell recognizes that the trace source is already being traced. It stops the trace, adds the new configuration, and starts or restarts the trace. * To stop a trace, use the *RemoveListener* parameter. To stop a trace that uses the file listener (a trace started by using the *FilePath* parameter), use the *RemoveFileListener* parameter. When you remove the listener, the trace stops. * To determine which components can be traced, use Get-TraceSource. The trace sources for each module are loaded automatically when the component is in use, and they appear in the output of **Get-TraceSource**. diff --git a/reference/6/Microsoft.PowerShell.Utility/Tee-Object.md b/reference/6/Microsoft.PowerShell.Utility/Tee-Object.md index 7dd507191b2b..cb9bbc5aa556 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Tee-Object.md +++ b/reference/6/Microsoft.PowerShell.Utility/Tee-Object.md @@ -156,7 +156,7 @@ Specifies a file that this cmdlet saves the object to. Unlike *FilePath*, the value of the *LiteralPath* parameter is used exactly as it is typed. No characters are interpreted as wildcards. If the path includes escape characters, enclose it in single quotation marks. -Single quotation marks tell Windows PowerShell not to interpret any characters as escape sequences. +Single quotation marks tell PowerShell not to interpret any characters as escape sequences. ```yaml Type: String diff --git a/reference/6/Microsoft.PowerShell.Utility/Trace-Command.md b/reference/6/Microsoft.PowerShell.Utility/Trace-Command.md index 1551936fee89..56d039709e8c 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Trace-Command.md +++ b/reference/6/Microsoft.PowerShell.Utility/Trace-Command.md @@ -53,7 +53,7 @@ PS C:\> $A = "i*" PS C:\> Trace-Command ParameterBinding {Get-Alias $Input} -PSHost -InputObject $A ``` -These commands trace the actions of the ParameterBinding operations of Windows PowerShell while it processes a Get-Alias expression that takes input from the pipeline. +These commands trace the actions of the ParameterBinding operations of PowerShell while it processes a Get-Alias expression that takes input from the pipeline. In **Trace-Command**, the *InputObject* parameter passes an object to the expression that is being processed during the trace. @@ -212,7 +212,7 @@ Accept wildcard characters: False ``` ### -Name -Specifies an array of Windows PowerShell components that are traced. +Specifies an array of PowerShell components that are traced. Enter the name of the trace source of each component. Wildcards are permitted. To find the trace sources on your computer, type `Get-TraceSource`. @@ -277,7 +277,7 @@ Accept wildcard characters: False ``` ### -PSHost -Indicates that the cmdlet sends the trace output to the Windows PowerShell host. +Indicates that the cmdlet sends the trace output to the PowerShell host. This parameter also selects the PSHost trace listener. ```yaml @@ -307,16 +307,16 @@ Returns the command trace in the debug stream. ## NOTES * Tracing is a method that developers use to debug and refine programs. When tracing, the program generates detailed messages about each step in its internal processing. -* The Windows PowerShell tracing cmdlets are designed to help Windows PowerShell developers, but they are available to all users. They let you monitor nearly every aspect of the functionality of the shell. -* To find the Windows PowerShell components that are enabled for tracing, type `Get-Help Get-TraceSource`. +* The PowerShell tracing cmdlets are designed to help PowerShell developers, but they are available to all users. They let you monitor nearly every aspect of the functionality of the shell. +* To find the PowerShell components that are enabled for tracing, type `Get-Help Get-TraceSource`. - A trace source is the part of each Windows PowerShell component that manages tracing and generates trace messages for the component. + A trace source is the part of each PowerShell component that manages tracing and generates trace messages for the component. To trace a component, you identify its trace source. A trace listener receives the output of the trace and displays it to the user. You can elect to send the trace data to a user-mode or kernel-mode debugger, to the host or console, to a file, or to a custom listener derived from the **System.Diagnostics.TraceListener** class. -* When you use the commandSet parameter set, Windows PowerShell processes the command just as it would be processed in a pipeline. For example, command discovery is not repeated for each incoming object. +* When you use the commandSet parameter set, PowerShell processes the command just as it would be processed in a pipeline. For example, command discovery is not repeated for each incoming object. * The names of the *Name*, *Expression*, *Option*, and *Command* parameters are optional. If you omit the parameter names, the unnamed parameter values must appear in this order: *Name*, *Expression*, *Option* or *Name*, *Command*, *Option*. If you include the parameter names, the parameters can appear in any order. ## RELATED LINKS diff --git a/reference/6/Microsoft.PowerShell.Utility/Unblock-File.md b/reference/6/Microsoft.PowerShell.Utility/Unblock-File.md index a96111eaab19..9cb9d060f45f 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Unblock-File.md +++ b/reference/6/Microsoft.PowerShell.Utility/Unblock-File.md @@ -27,14 +27,14 @@ Unblock-File -LiteralPath [-WhatIf] [-Confirm] [] ## DESCRIPTION The **Unblock-File** cmdlet lets you open files that were downloaded from the Internet. -It unblocks Windows PowerShell script files that were downloaded from the Internet so you can run them, even when the Windows PowerShell execution policy is **RemoteSigned**. +It unblocks PowerShell script files that were downloaded from the Internet so you can run them, even when the PowerShell execution policy is **RemoteSigned**. By default, these files are blocked to protect the computer from untrusted files. Before using the **Unblock-File** cmdlet, review the file and its source and verify that it is safe to open. Internally, the **Unblock-File** cmdlet removes the Zone.Identifier alternate data stream, which has a value of "3" to indicate that it was downloaded from the Internet. -For more information about Windows PowerShell execution policies, see about_Execution_Policies (http://go.microsoft.com/fwlink/?LinkID=135170). +For more information about PowerShell execution policies, see about_Execution_Policies (http://go.microsoft.com/fwlink/?LinkID=135170). This cmdlet was introduced in Windows PowerShell 3.0. @@ -65,7 +65,7 @@ Stream Length ------ ------ Zone.Identifier 26 -The second command shows what happens when you run a blocked script in a Windows PowerShell session in which the execution policy is **RemoteSigned**. The RemoteSigned policy prevents you from running scripts that are downloaded from the Internet unless they are digitally signed. +The second command shows what happens when you run a blocked script in a PowerShell session in which the execution policy is **RemoteSigned**. The RemoteSigned policy prevents you from running scripts that are downloaded from the Internet unless they are digitally signed. PS C:\> C:\ps-test\Start-ActivityTracker.ps1 c:\ps-test\Start-ActivityTracker.ps1 : File c:\ps-test\Start-ActivityTracker.ps1 cannot be loaded. The file c:\ps-test\Start-ActivityTracker.ps1 is not digitally signed. The script @@ -81,7 +81,7 @@ The third command uses the **Unblock-File** cmdlet to unblock the script so it c PS C:\> Get-Item C:\ps-test\Start-ActivityTracker.ps1 | Unblock-File ``` -This command shows how to find and unblock Windows PowerShell scripts. +This command shows how to find and unblock PowerShell scripts. ## PARAMETERS @@ -90,7 +90,7 @@ Specifies the files to unblock. Unlike *Path*, the value of the *LiteralPath* parameter is used exactly as it is typed. No characters are interpreted as wildcards. If the path includes escape characters, enclose it in single quotation marks. -Single quotation marks tell Windows PowerShell not to interpret any characters as escape sequences. +Single quotation marks tell PowerShell not to interpret any characters as escape sequences. ```yaml Type: String[] diff --git a/reference/6/Microsoft.PowerShell.Utility/Update-FormatData.md b/reference/6/Microsoft.PowerShell.Utility/Update-FormatData.md index 30a960a84c4c..d0aaafbdc4da 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Update-FormatData.md +++ b/reference/6/Microsoft.PowerShell.Utility/Update-FormatData.md @@ -21,7 +21,7 @@ Update-FormatData [[-AppendPath] ] [-PrependPath ] [-WhatIf] ## DESCRIPTION The **Update-FormatData** cmdlet reloads the formatting data from formatting files into the current session. -This cmdlet lets you update the formatting data without restarting Windows PowerShell. +This cmdlet lets you update the formatting data without restarting PowerShell. Without parameters, **Update-FormatData** reloads the formatting files that it loaded previously. You can use the parameters of **Update-FormatData** to add new formatting files to the session. @@ -29,11 +29,11 @@ You can use the parameters of **Update-FormatData** to add new formatting files Formatting files are text files in XML format with the format.ps1xml file name extension. The formatting data in the files defines the display of Microsoft .NET Framework objects in the session. -When Windows PowerShell starts, it loads the format data from the formatting files in the Windows PowerShell installation directory ($pshome) into the session. -You can use **Update-FormatData** to reload the formatting data into the current session without restarting Windows PowerShell. +When PowerShell starts, it loads the format data from the formatting files in the PowerShell installation directory ($pshome) into the session. +You can use **Update-FormatData** to reload the formatting data into the current session without restarting PowerShell. This is useful when you have added or changed a formatting file, but do not want to interrupt the session. -For more information about formatting files in Windows PowerShell, see about_Format.ps1xml. +For more information about formatting files in PowerShell, see about_Format.ps1xml. ## EXAMPLES @@ -78,10 +78,10 @@ Because the NewFiles.format.ps1xml file was previously loaded, **Update-FormatDa ### -AppendPath Specifies formatting files that this cmdlet adds to the session. -The files are loaded after Windows PowerShell loads the built-in formatting files. +The files are loaded after PowerShell loads the built-in formatting files. -When formatting .NET objects, Windows PowerShell uses the first formatting definition that it finds for each .NET type. -If you use the *AppendPath* parameter, Windows PowerShell searches the data from the built-in files before it encounters the formatting data that you are adding. +When formatting .NET objects, PowerShell uses the first formatting definition that it finds for each .NET type. +If you use the *AppendPath* parameter, PowerShell searches the data from the built-in files before it encounters the formatting data that you are adding. Use this parameter to add a file that formats a .NET object that is not referenced in the built-in formatting files. @@ -99,10 +99,10 @@ Accept wildcard characters: False ### -PrependPath Specifies formatting files that this cmdlet adds to the session. -The files are loaded before Windows PowerShell loads the built-in formatting files. +The files are loaded before PowerShell loads the built-in formatting files. -When formatting .NET objects, Windows PowerShell uses the first formatting definition that it finds for each .NET type. -If you use the *PrependPath* parameter, Windows PowerShell searches the data from the files that you are adding before it encounters the formatting data from the built-in files. +When formatting .NET objects, PowerShell uses the first formatting definition that it finds for each .NET type. +If you use the *PrependPath* parameter, PowerShell searches the data from the files that you are adding before it encounters the formatting data from the built-in files. Use this parameter to add a file that formats a .NET object that is also referenced in the built-in formatting files. diff --git a/reference/6/Microsoft.PowerShell.Utility/Update-TypeData.md b/reference/6/Microsoft.PowerShell.Utility/Update-TypeData.md index eede155cae09..b0c6498d018c 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Update-TypeData.md +++ b/reference/6/Microsoft.PowerShell.Utility/Update-TypeData.md @@ -40,7 +40,7 @@ Update-TypeData [-Force] [-TypeData] [-InformationAction Get-ChildItem | ForEach-Object { if ($_.GetType().ToString() -eq "Microsoft.Win32.RegistryKey") {Write-Error "Invalid object" -ErrorID B1 -Targetobject $_ } else {$_ } } ``` -This command declares a non-terminating error when the Get-ChildItem cmdlet returns a Microsoft.Win32.RegistryKey object, such as the objects in the HKLM: or HKCU: drives of the Windows PowerShell Registry provider. +This command declares a non-terminating error when the Get-ChildItem cmdlet returns a Microsoft.Win32.RegistryKey object, such as the objects in the HKLM: or HKCU: drives of the PowerShell Registry provider. ### Example 2: Write an error message to the console ``` diff --git a/reference/6/Microsoft.PowerShell.Utility/Write-Information.md b/reference/6/Microsoft.PowerShell.Utility/Write-Information.md index 44390238cd72..b2c603302664 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Write-Information.md +++ b/reference/6/Microsoft.PowerShell.Utility/Write-Information.md @@ -11,7 +11,7 @@ title: Write-Information ## SYNOPSIS -Specifies how Windows PowerShell handles information stream data for a command. +Specifies how PowerShell handles information stream data for a command. ## SYNTAX @@ -21,10 +21,10 @@ Write-Information [-MessageData] [[-Tags] ] [ [!NOTE] > The information stream does not follow the standard convention of prefixing its messages with "[Stream Name]:". This was intended for brevity and visual cleanliness. diff --git a/reference/6/Microsoft.PowerShell.Utility/Write-Progress.md b/reference/6/Microsoft.PowerShell.Utility/Write-Progress.md index 3a14a6e5ab5d..c222750db9e3 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Write-Progress.md +++ b/reference/6/Microsoft.PowerShell.Utility/Write-Progress.md @@ -11,7 +11,7 @@ title: Write-Progress # Write-Progress ## SYNOPSIS -Displays a progress bar within a Windows PowerShell command window. +Displays a progress bar within a PowerShell command window. ## SYNTAX @@ -22,7 +22,7 @@ Write-Progress [-Activity] [[-Status] ] [[-Id] ] [-Perce ``` ## DESCRIPTION -The `Write-Progress` cmdlet displays a progress bar in a Windows PowerShell command window that depicts the status of a running command or script. +The `Write-Progress` cmdlet displays a progress bar in a PowerShell command window that depicts the status of a running command or script. You can select the indicators that the bar reflects and the text that appears above and below the progress bar. ## EXAMPLES @@ -242,7 +242,7 @@ You cannot pipe input to this cmdlet. `Write-Progress` does not generate any output. ## NOTES -If the progress bar does not appear, check the value of the $ProgressPreference variable. If the value is set to SilentlyContinue, the progress bar is not displayed. For more information about Windows PowerShell preferences, see about_Preference_Variables. +If the progress bar does not appear, check the value of the $ProgressPreference variable. If the value is set to SilentlyContinue, the progress bar is not displayed. For more information about PowerShell preferences, see about_Preference_Variables. The parameters of the cmdlet correspond to the properties of the ProgressRecord class (System.Management.Automation.ProgressRecord). For more information, see [ProgressRecord Class](https://msdn.microsoft.com/library/system.management.automation.progressrecord) in the MSDN library. diff --git a/reference/6/Microsoft.PowerShell.Utility/Write-Verbose.md b/reference/6/Microsoft.PowerShell.Utility/Write-Verbose.md index 6bebf30f54d7..9d9cfa228b09 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Write-Verbose.md +++ b/reference/6/Microsoft.PowerShell.Utility/Write-Verbose.md @@ -20,7 +20,7 @@ Write-Verbose [-Message] [] ``` ## DESCRIPTION -The **Write-Verbose** cmdlet writes text to the verbose message stream in Windows PowerShell. +The **Write-Verbose** cmdlet writes text to the verbose message stream in PowerShell. Typically, the verbose message stream is used to deliver information about command processing that is used for debugging a command. By default, the verbose message stream is not displayed, but you can display it by changing the value of the **$VerbosePreference** variable or using the **Verbose** common parameter in any command. @@ -85,7 +85,7 @@ You can pipe a string that contains the message to **Write-Verbose**. ## NOTES * Verbose messages are returned only when the command uses the **Verbose** common parameter. For more information, see about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216). -* In Windows PowerShell background jobs and remote commands, the **$VerbosePreference** variable in the job session and remote session determine whether the verbose message is displayed by default. For more information about the **$VerbosePreference** variable, see [about_Preference_Variables](../Microsoft.PowerShell.Core/About/about_Preference_Variables.md). +* In PowerShell background jobs and remote commands, the **$VerbosePreference** variable in the job session and remote session determine whether the verbose message is displayed by default. For more information about the **$VerbosePreference** variable, see [about_Preference_Variables](../Microsoft.PowerShell.Core/About/about_Preference_Variables.md). ## RELATED LINKS diff --git a/reference/6/Microsoft.PowerShell.Utility/Write-Warning.md b/reference/6/Microsoft.PowerShell.Utility/Write-Warning.md index 376c19f9a4be..518e4a9f0135 100644 --- a/reference/6/Microsoft.PowerShell.Utility/Write-Warning.md +++ b/reference/6/Microsoft.PowerShell.Utility/Write-Warning.md @@ -20,7 +20,7 @@ Write-Warning [-Message] [] ``` ## DESCRIPTION -The **Write-Warning** cmdlet writes a warning message to the Windows PowerShell host. +The **Write-Warning** cmdlet writes a warning message to the PowerShell host. The response to the warning depends on the value of the user's $WarningPreference variable and the use of the *WarningAction* common parameter. ## EXAMPLES @@ -77,7 +77,7 @@ Continue with this operation? ``` This example shows the effect of the *WarningAction* common parameter on a **Write-Warning** command. -You can use the *WarningAction* common parameter with any cmdlet to determine how Windows PowerShell responds to warnings resulting from that command. +You can use the *WarningAction* common parameter with any cmdlet to determine how PowerShell responds to warnings resulting from that command. The *WarningAction* common parameter overrides the value of the $WarningPreference only for that particular command. This command uses the **Write-Warning** cmdlet to display a warning.