From 7342375f380dd9bfe34420a4c3840d43469bf8b1 Mon Sep 17 00:00:00 2001 From: Luke Humberdross <46994024+lukejjh@users.noreply.github.com> Date: Wed, 3 Nov 2021 23:34:31 +1000 Subject: [PATCH 1/4] everything-about-pscustomobject.md - fixed typo (#8298) everything-about-pscustomobject.md - fixed typo: about_Inrinsic_Members => about_Intrinsic_Members --- .../learn/deep-dives/everything-about-pscustomobject.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/reference/docs-conceptual/learn/deep-dives/everything-about-pscustomobject.md b/reference/docs-conceptual/learn/deep-dives/everything-about-pscustomobject.md index dc69b413dda8..0d8440fd22a0 100644 --- a/reference/docs-conceptual/learn/deep-dives/everything-about-pscustomobject.md +++ b/reference/docs-conceptual/learn/deep-dives/everything-about-pscustomobject.md @@ -109,7 +109,7 @@ $myObject.psobject.properties.remove('ID') ``` The `.psobject` is an intrinsic member that gives you access to base object metadata. For more -information about intrinsic members, see [about_Inrinsic_Members](/powershell/module/microsoft.powershell.core/about/about_intrinsic_members). +information about intrinsic members, see [about_Intrinsic_Members](/powershell/module/microsoft.powershell.core/about/about_intrinsic_members). + ### Enumerating property names From 7fcce7efe81b0a16b53f4e3f5a66b0f6f19bab6b Mon Sep 17 00:00:00 2001 From: Sean Wheeler Date: Wed, 3 Nov 2021 09:03:25 -0500 Subject: [PATCH 2/4] Correct information about path creation (#8301) --- .../Add-Content.md | 180 +++++++++--------- .../Set-Content.md | 35 ++-- .../Add-Content.md | 58 +++--- .../Set-Content.md | 22 ++- .../Add-Content.md | 56 +++--- .../Set-Content.md | 22 ++- .../Add-Content.md | 56 +++--- .../Set-Content.md | 22 ++- 8 files changed, 240 insertions(+), 211 deletions(-) diff --git a/reference/5.1/Microsoft.PowerShell.Management/Add-Content.md b/reference/5.1/Microsoft.PowerShell.Management/Add-Content.md index 093f39e023d5..198260fc9567 100644 --- a/reference/5.1/Microsoft.PowerShell.Management/Add-Content.md +++ b/reference/5.1/Microsoft.PowerShell.Management/Add-Content.md @@ -2,7 +2,7 @@ external help file: Microsoft.PowerShell.Commands.Management.dll-Help.xml Locale: en-US Module Name: Microsoft.PowerShell.Management -ms.date: 04/23/2019 +ms.date: 11/03/2021 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.management/add-content?view=powershell-5.1&WT.mc_id=ps-gethelp schema: 2.0.0 title: Add-Content @@ -50,9 +50,9 @@ their file name. Add-Content -Path .\*.txt -Exclude help* -Value 'End of file' ``` -The `Add-Content` cmdlet uses the **Path** parameter to specify all .txt files in the current -directory. The **Exclude** parameter ignores file names that match the specified pattern. The -**Value** parameter specifies the text string that is written to the files. +The **Path** parameter specifies all `.txt` files in the current directory, but the **Exclude** +parameter ignores file names that match the specified pattern. The **Value** parameter specifies the +text string that is written to the files. Use [Get-Content](Get-Content.md) to display the contents of these files. @@ -66,45 +66,46 @@ Add-Content -Path .\DateTimeFile1.log, .\DateTimeFile2.log -Value (Get-Date) -Pa Get-Content -Path .\DateTimeFile1.log ``` -The `Add-Content` cmdlet uses the **Path** and **Value** parameters to create two new files in the -current directory. The **Value** parameter specifies the `Get-Date` cmdlet to get the date and -passes the date to `Add-Content`. The `Add-Content` cmdlet writes the date to each file. The -**PassThru** parameter passes an object that represents the date object. Because there is no other -cmdlet to receive the passed object, it is displayed in the PowerShell console. The `Get-Content` -cmdlet displays the updated file, DateTimeFile1.log. +```Output +Tuesday, May 14, 2019 8:24:27 AM +Tuesday, May 14, 2019 8:24:27 AM +5/14/2019 8:24:27 AM +``` + +The `Add-Content` cmdlet creates two new files in the current directory. The **Value** parameter +contains the output of the `Get-Date` cmdlet. The **PassThru** parameter outputs the added contents +to the pipeline. Because there is no other cmdlet to receive the output, it is displayed in the +PowerShell console. The `Get-Content` cmdlet displays the updated file, `DateTimeFile1.log`. ### Example 3: Add the contents of a specified file to another file -This example gets the content from a file and appends that content into another file. +This example gets the content from a file and stores the content in a variable. The variable is +used to append the content into another file. ```powershell -Add-Content -Path .\CopyToFile.txt -Value (Get-Content -Path .\CopyFromFile.txt) +$From = Get-Content -Path .\CopyFromFile.txt +Add-Content -Path .\CopyToFile.txt -Value $From Get-Content -Path .\CopyToFile.txt ``` -The `Add-Content` cmdlet uses the **Path** parameter to specify the new file in the current -directory, CopyToFile.txt. The **Value** parameter uses the `Get-Content` cmdlet to get the -contents of the file, CopyFromFile.txt. The parentheses around the `Get-Content` cmdlet ensure that -the command finishes before the `Add-Content` command begins. The **Value** parameter is passed to -`Add-Content`. The `Add-Content` cmdlet appends the data to the CopyToFile.txt file. The -`Get-Content` cmdlet displays the updated file, CopyToFile.txt. +- The `Get-Content` cmdlet gets the contents of `CopyFromFile.txt` and stores the contents in the + `$From` variable. +- The `Add-Content` cmdlet updates the `CopyToFile.txt` file using the contents of the `$From` + variable. +- The `Get-Content` cmdlet displays CopyToFile.txt. -### Example 4: Use a variable to add the contents of a specified file to another file +### Example 4: Add the contents of a specified file to another file using the pipeline -This example gets the content from a file and stores the content in a variable. The variable is -used to append the content into another file. +This example gets the content from a file and pipes it to the `Add-Content` cmdlet. ```powershell -$From = Get-Content -Path .\CopyFromFile.txt -Add-Content -Path .\CopyToFile.txt -Value $From +Get-Content -Path .\CopyFromFile.txt | Add-Content -Path .\CopyToFile.txt Get-Content -Path .\CopyToFile.txt ``` -The `Get-Content` cmdlet gets the contents of CopyFromFile.txt and stores the contents in the -`$From` variable. The `Add-Content` cmdlet uses the **Path** parameter to specify the -CopyToFile.txt file in the current directory. The **Value** parameter uses the `$From` variable and -passes the content to `Add-Content`. The `Add-Content` cmdlet updates the CopyToFile.txt file. The -`Get-Content` cmdlet displays CopyToFile.txt. +The `Get-Content` cmdlet gets the contents of `CopyFromFile.txt`. The results are piped to the +`Add-Content` cmdlet, which updates the `CopyToFile.txt`. +The last `Get-Content` cmdlet displays `CopyToFile.txt`. ### Example 5: Create a new file and copy content @@ -115,16 +116,16 @@ Add-Content -Path .\NewFile.txt -Value (Get-Content -Path .\CopyFromFile.txt) Get-Content -Path .\NewFile.txt ``` -The `Add-Content` cmdlet uses the **Path** and **Value** parameters to create a new file in the -current directory. The **Value** parameter uses the `Get-Content` cmdlet to get the contents of an -existing file, CopyFromFile.txt. The parentheses around the `Get-Content` cmdlet ensure that the -command finishes before the `Add-Content` command begins. The **Value** parameter passes the -content to `Add-Content` which updates the NewFile.txt file. The `Get-Content` cmdlet displays the -contents of the new file, NewFile.txt. +- The `Add-Content` cmdlet uses the **Path** and **Value** parameters to create a new file in the + current directory. +- The `Get-Content` cmdlet gets the contents of an existing file, `CopyFromFile.txt` + and passes it to the **Value** parameter. The parentheses around the `Get-Content` cmdlet ensure + that the command finishes before the `Add-Content` command begins. +- The `Get-Content` cmdlet displays the contents of the new file, `NewFile.txt`. ### Example 6: Add content to a read-only file -This command adds the value to the file even if the **IsReadOnly** file attribute is set to True. +This command adds a value to the file even if the **IsReadOnly** file attribute is set to **True**. The steps to create a read-only file are included in the example. ```powershell @@ -138,16 +139,18 @@ Get-Content -Path .\IsReadOnlyTextFile.txt ```Output Mode LastWriteTime Length Name ---- ------------- ------ ---- --ar--- 1/28/2019 13:35 0 IsReadOnlyTextFile.txt +-ar-- 1/28/2019 13:35 0 IsReadOnlyTextFile.txt ``` -The `New-Item` cmdlet uses the **Path** and **ItemType** parameters to create the file -IsReadOnlyTextFile.txt in the current directory. The `Set-ItemProperty` cmdlet uses the **Name** -and **Value** parameters to change the file's **IsReadOnly** property to True. The `Get-ChildItem` -cmdlet shows the file is empty (0) and has the read-only attribute (`r`). The `Add-Content` cmdlet -uses the **Path** parameter to specify the file. The **Value** parameter includes the text string -to append to the file. The **Force** parameter writes the text to the read-only file. The -`Get-Content` cmdlet uses the **Path** parameter to display the file's contents. +- The `New-Item` cmdlet uses the **Path** and **ItemType** parameters to create the file + `IsReadOnlyTextFile.txt` in the current directory. +- The `Set-ItemProperty` cmdlet uses the **Name** and **Value** parameters to change the file's + **IsReadOnly** property to True. +- The `Get-ChildItem` cmdlet shows the file is empty (0) and has the read-only attribute (`r`). +- The `Add-Content` cmdlet uses the **Path** parameter to specify the file. The **Value** parameter + includes the text string to append to the file. The **Force** parameter writes the text to the + read-only file. +- The `Get-Content` cmdlet uses the **Path** parameter to display the file's contents. To remove the read-only attribute, use the `Set-ItemProperty` command with the **Value** parameter set to `False`. @@ -156,15 +159,10 @@ set to `False`. ### -Credential -Specifies a user account that has permission to perform this action. The default is the current -user. - -Type a user name, such as **User01** or **Domain01\User01**, or enter a **PSCredential** object, -such as one generated by the `Get-Credential` cmdlet. If you type a user name, you will be prompted -for a password. - -> [!WARNING] +> [!NOTE] > This parameter is not supported by any providers installed with PowerShell. +> To impersonate another user, or elevate your credentials when running this cmdlet, +> use [Invoke-Command](../Microsoft.PowerShell.Core/Invoke-Command.md). ```yaml Type: System.Management.Automation.PSCredential @@ -215,8 +213,11 @@ Accept wildcard characters: False ### -Exclude -Omits the specified items. The value of this parameter qualifies the **Path** parameter. Enter a -path element or pattern, such as **\*.txt**. Wildcards are permitted. +Specifies, as a string array, an item or items that this cmdlet excludes in the operation. The value +of this parameter qualifies the **Path** parameter. Enter a path element or pattern, such as +`*.txt`. Wildcard characters are permitted. The **Exclude** parameter is effective only when the +command includes the contents of an item, such as `C:\Windows\*`, where the wildcard character +specifies the contents of the `C:\Windows` directory. ```yaml Type: System.String[] @@ -232,11 +233,13 @@ Accept wildcard characters: True ### -Filter -Specifies a filter in the provider's format or language. The value of this parameter qualifies the -**Path** parameter. The syntax of the filter, including the use of wildcards, depends on the -provider. **Filters** are more efficient than other parameters because the provider applies filters -when objects are retrieved. Otherwise, PowerShell processes filters after the objects are -retrieved. +Specifies a filter to qualify the **Path** parameter. The +[FileSystem](../Microsoft.PowerShell.Core/About/about_FileSystem_Provider.md) provider is the only +installed PowerShell provider that supports the use of filters. You can find the syntax for the +**FileSystem** filter language in +[about_Wildcards](../Microsoft.PowerShell.Core/About/about_Wildcards.md). Filters are more efficient +than other parameters, because the provider applies them when the cmdlet gets the objects rather +than having PowerShell filter the objects after they are retrieved. ```yaml Type: System.String @@ -253,8 +256,7 @@ Accept wildcard characters: True ### -Force Overrides the read-only attribute, allowing you to add content to a read-only file. For example, -**Force** will override the read-only attribute or create directories to complete a file path, but -it will not attempt to change file permissions. +**Force** overrides the read-only attribute but it does not change file permissions. ```yaml Type: System.Management.Automation.SwitchParameter @@ -270,8 +272,11 @@ Accept wildcard characters: False ### -Include -Adds only the specified items. The value of this parameter qualifies the **Path** parameter. Enter -a path element or pattern, such as **\*.txt**. Wildcards are permitted. +Specifies, as a string array, an item or items that this cmdlet includes in the operation. The value +of this parameter qualifies the **Path** parameter. Enter a path element or pattern, such as +`"*.txt"`. Wildcard characters are permitted. The **Include** parameter is effective only when the +command includes the contents of an item, such as `C:\Windows\*`, where the wildcard character +specifies the contents of the `C:\Windows` directory. ```yaml Type: System.String[] @@ -287,10 +292,13 @@ Accept wildcard characters: True ### -LiteralPath -Specifies the path to the items that receive the additional content. Unlike **Path**, 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 -PowerShell not to interpret any characters as escape sequences. +Specifies a path to one or more locations. 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 PowerShell not to interpret any characters +as escape sequences. + +For more information, see +[about_Quoting_Rules](../Microsoft.Powershell.Core/About/about_Quoting_Rules.md). ```yaml Type: System.String[] @@ -342,8 +350,10 @@ Accept wildcard characters: False ### -Path -Specifies the path to the items that receive the additional content. Wildcards are permitted. If -you specify multiple paths, use commas to separate the paths. +Specifies the path to the items that receive the additional content. Wildcard characters are +permitted. The paths must be paths to items, not to containers. For example, you must specify a path +to one or more files, not a path to a directory. If you specify multiple paths, use commas to +separate the paths. ```yaml Type: System.String[] @@ -365,10 +375,10 @@ it. Wildcard characters are not supported. **Stream** is a dynamic parameter that the FileSystem provider adds to `Add-Content`. This parameter works only in file system drives. -You can use the `Add-Content` cmdlet to change the content of the **Zone.Identifier** alternate -data stream. However, we do not recommend this as a way to eliminate security checks that block -files that are downloaded from the Internet. If you verify that a downloaded file is safe, use the -`Unblock-File` cmdlet. +You can use the `Add-Content` cmdlet to change the content of any alternate data stream, such as +`Zone.Identifier`. However, we do not recommend this as a way to eliminate security checks that +block files that are downloaded from the Internet. If you verify that a downloaded file is safe, use +the `Unblock-File` cmdlet. This parameter was introduced in PowerShell 3.0. @@ -456,9 +466,9 @@ Accept wildcard characters: False ### CommonParameters -This cmdlet supports the common parameters: `-Debug`, `-ErrorAction`, `-ErrorVariable`, -`-InformationAction`, `-InformationVariable`, `-OutVariable`, `-OutBuffer`, `-PipelineVariable`, -`-Verbose`, `-WarningAction`, and `-WarningVariable`. For more information, see +This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, +-InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, +-WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216). ## Inputs @@ -476,17 +486,15 @@ represents the content. Otherwise, this cmdlet does not generate any output. ## Notes -When you pipe an object to `Add-Content`, the object is converted to a string before it is added to -the item. The object type determines the string format, but the format might be different than the -default display of the object. To control the string format, use the formatting parameters of the -sending cmdlet. - -You can also refer to `Add-Content` by its built-in alias, `ac`. For more information, see -[about_Aliases](../Microsoft.PowerShell.Core/About/about_Aliases.md). - -The `Add-Content` cmdlet is designed to work with the data exposed by any provider. To list the -providers available in your session, type `Get-PSProvider`. For more information, see -[about_Providers](../Microsoft.PowerShell.Core/About/about_Providers.md). +- When you pipe an object to `Add-Content`, the object is converted to a string before it is added + to the item. The object type determines the string format, but the format might be different than + the default display of the object. To control the string format, use the formatting parameters of + the sending cmdlet. +- You can also refer to `Add-Content` by its built-in alias, `ac`. For more information, see + [about_Aliases](../Microsoft.PowerShell.Core/About/about_Aliases.md). +- The `Add-Content` cmdlet is designed to work with the data exposed by any provider. To list the + providers available in your session, type `Get-PSProvider`. For more information, see + [about_Providers](../Microsoft.PowerShell.Core/About/about_Providers.md). ## Related links diff --git a/reference/5.1/Microsoft.PowerShell.Management/Set-Content.md b/reference/5.1/Microsoft.PowerShell.Management/Set-Content.md index 683e01dad422..5679d9252b3d 100644 --- a/reference/5.1/Microsoft.PowerShell.Management/Set-Content.md +++ b/reference/5.1/Microsoft.PowerShell.Management/Set-Content.md @@ -2,7 +2,7 @@ external help file: Microsoft.PowerShell.Commands.Management.dll-Help.xml Locale: en-US Module Name: Microsoft.PowerShell.Management -ms.date: 05/14/2019 +ms.date: 11/03/2021 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.management/set-content?view=powershell-5.1&WT.mc_id=ps-gethelp schema: 2.0.0 title: Set-Content @@ -225,11 +225,13 @@ Accept wildcard characters: True ### -Filter -Specifies a filter to qualify the **Path** parameter. The [FileSystem](../Microsoft.PowerShell.Core/About/about_FileSystem_Provider.md) -provider is the only installed PowerShell provider that supports the use of filters. You can find -the syntax for the **FileSystem** filter language in [about_Wildcards](../Microsoft.PowerShell.Core/About/about_Wildcards.md). -Filters are more efficient than other parameters, because the provider applies them when the cmdlet -gets the objects rather than having PowerShell filter the objects after they are retrieved. +Specifies a filter to qualify the **Path** parameter. The +[FileSystem](../Microsoft.PowerShell.Core/About/about_FileSystem_Provider.md) provider is the only +installed PowerShell provider that supports the use of filters. You can find the syntax for the +**FileSystem** filter language in +[about_Wildcards](../Microsoft.PowerShell.Core/About/about_Wildcards.md). Filters are more efficient +than other parameters, because the provider applies them when the cmdlet gets the objects rather +than having PowerShell filter the objects after they are retrieved. ```yaml Type: System.String @@ -246,8 +248,9 @@ Accept wildcard characters: True ### -Force Forces the cmdlet to set the contents of a file, even if the file is read-only. Implementation -varies from provider to provider. For more information, see [about_Providers](../Microsoft.PowerShell.Core/About/about_Providers.md). -The **Force** parameter does not override security restrictions. +varies from provider to provider. For more information, see +[about_Providers](../Microsoft.PowerShell.Core/About/about_Providers.md). The **Force** parameter +does not override security restrictions. ```yaml Type: System.Management.Automation.SwitchParameter @@ -360,10 +363,10 @@ it. Wildcard characters are not supported. **Stream** is a dynamic parameter that the **FileSystem** provider adds to `Set-Content`. This parameter works only in file system drives. -You can use the `Set-Content` cmdlet to change the content of the **Zone.Identifier** alternate data -stream. However, we do not recommend this as a way to eliminate security checks that block files -that are downloaded from the Internet. If you verify that a downloaded file is safe, use the -`Unblock-File` cmdlet. +You can use the `Set-Content` cmdlet to create or update the content of any alternate data stream, +such as `Zone.Identifier`. However, we do not recommend this as a way to eliminate security checks +that block files that are downloaded from the Internet. If you verify that a downloaded file is +safe, use the `Unblock-File` cmdlet. This parameter was introduced in PowerShell 3.0. @@ -446,10 +449,10 @@ Accept wildcard characters: False ### CommonParameters -This cmdlet supports the common parameters: `-Debug`, `-ErrorAction`, `-ErrorVariable`, -`-InformationAction`, `-InformationVariable`, `-OutVariable`, `-OutBuffer`, `-PipelineVariable`, -`-Verbose`, `-WarningAction`, and `-WarningVariable`. -For more information, see [about_CommonParameters](../Microsoft.PowerShell.Core/About/about_CommonParameters.md). +This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, +-InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, +-WarningAction, and -WarningVariable. For more information, see +[about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216). ## Inputs diff --git a/reference/7.0/Microsoft.PowerShell.Management/Add-Content.md b/reference/7.0/Microsoft.PowerShell.Management/Add-Content.md index 00ee670c06a4..d009904f3978 100644 --- a/reference/7.0/Microsoft.PowerShell.Management/Add-Content.md +++ b/reference/7.0/Microsoft.PowerShell.Management/Add-Content.md @@ -2,7 +2,7 @@ external help file: Microsoft.PowerShell.Commands.Management.dll-Help.xml Locale: en-US Module Name: Microsoft.PowerShell.Management -ms.date: 12/18/2020 +ms.date: 11/03/2021 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.management/add-content?view=powershell-7&WT.mc_id=ps-gethelp schema: 2.0.0 title: Add-Content @@ -54,6 +54,8 @@ The **Path** parameter specifies all `.txt` files in the current directory, but parameter ignores file names that match the specified pattern. The **Value** parameter specifies the text string that is written to the files. +Use [Get-Content](Get-Content.md) to display the contents of these files. + ### Example 2: Add a date to the end of the specified files This example appends the date to files in the current directory and displays the date in the @@ -70,10 +72,10 @@ Tuesday, May 14, 2019 8:24:27 AM 5/14/2019 8:24:27 AM ``` -The `Add-Content` cmdlet creates two new files in the current directory. The **Value** parameter contains -the output of the `Get-Date` cmdlet. The **PassThru** parameter outputs the added contents to the pipeline. -Because there is no other cmdlet to receive the output, it is displayed in the PowerShell console. -The `Get-Content` cmdlet displays the updated file, `DateTimeFile1.log`. +The `Add-Content` cmdlet creates two new files in the current directory. The **Value** parameter +contains the output of the `Get-Date` cmdlet. The **PassThru** parameter outputs the added contents +to the pipeline. Because there is no other cmdlet to receive the output, it is displayed in the +PowerShell console. The `Get-Content` cmdlet displays the updated file, `DateTimeFile1.log`. ### Example 3: Add the contents of a specified file to another file @@ -209,7 +211,7 @@ Accept wildcard characters: False ### -Encoding -Specifies the type of encoding for the target file. The default value is `utf8BOM`. +Specifies the type of encoding for the target file. The default value is `utf8NoBOM`. Encoding is a dynamic parameter that the FileSystem provider adds to the `Add-Content` cmdlet. This parameter works only in file system drives. @@ -266,11 +268,13 @@ Accept wildcard characters: True ### -Filter -Specifies a filter to qualify the **Path** parameter. The [FileSystem](../Microsoft.PowerShell.Core/About/about_FileSystem_Provider.md) -provider is the only installed PowerShell provider that supports the use of filters. You can find -the syntax for the **FileSystem** filter language in [about_Wildcards](../Microsoft.PowerShell.Core/About/about_Wildcards.md). -Filters are more efficient than other parameters, because the provider applies them when the cmdlet -gets the objects rather than having PowerShell filter the objects after they are retrieved. +Specifies a filter to qualify the **Path** parameter. The +[FileSystem](../Microsoft.PowerShell.Core/About/about_FileSystem_Provider.md) provider is the only +installed PowerShell provider that supports the use of filters. You can find the syntax for the +**FileSystem** filter language in +[about_Wildcards](../Microsoft.PowerShell.Core/About/about_Wildcards.md). Filters are more efficient +than other parameters, because the provider applies them when the cmdlet gets the objects rather +than having PowerShell filter the objects after they are retrieved. ```yaml Type: System.String @@ -287,8 +291,7 @@ Accept wildcard characters: True ### -Force Overrides the read-only attribute, allowing you to add content to a read-only file. For example, -**Force** will override the read-only attribute or create directories to complete a file path, but -it will not attempt to change file permissions. +**Force** overrides the read-only attribute but it does not change file permissions. ```yaml Type: System.Management.Automation.SwitchParameter @@ -329,7 +332,8 @@ typed. No characters are interpreted as wildcards. If the path includes escape c it in single quotation marks. Single quotation marks tell PowerShell not to interpret any characters as escape sequences. -For more information, see [about_Quoting_Rules](../Microsoft.Powershell.Core/About/about_Quoting_Rules.md). +For more information, see +[about_Quoting_Rules](../Microsoft.Powershell.Core/About/about_Quoting_Rules.md). ```yaml Type: System.String[] @@ -381,11 +385,10 @@ Accept wildcard characters: False ### -Path -Specifies the path to the items that receive the additional content. -Wildcard characters are permitted. -The paths must be paths to items, not to containers. -For example, you must specify a path to one or more files, not a path to a directory. -If you specify multiple paths, use commas to separate the paths. +Specifies the path to the items that receive the additional content. Wildcard characters are +permitted. The paths must be paths to items, not to containers. For example, you must specify a path +to one or more files, not a path to a directory. If you specify multiple paths, use commas to +separate the paths. ```yaml Type: System.String[] @@ -410,11 +413,10 @@ it. Wildcard characters are not supported. **Stream** is a dynamic parameter that the FileSystem provider adds to `Add-Content`. This parameter works only in file system drives. -You can use the `Add-Content` cmdlet to change the content of any alternate -data stream, such as `Zone.Identifier`. However, we do not recommend this as -a way to eliminate security checks that block files that are downloaded from -the Internet. If you verify that a downloaded file is safe, use the -`Unblock-File` cmdlet. +You can use the `Add-Content` cmdlet to change the content of any alternate data stream, such as +`Zone.Identifier`. However, we do not recommend this as a way to eliminate security checks that +block files that are downloaded from the Internet. If you verify that a downloaded file is safe, use +the `Unblock-File` cmdlet. This parameter was introduced in PowerShell 3.0. @@ -505,10 +507,10 @@ represents the content. Otherwise, this cmdlet does not generate any output. ## Notes -- When you pipe an object to `Add-Content`, the object is converted to a string before it is added to - the item. The object type determines the string format, but the format might be different than the - default display of the object. To control the string format, use the formatting parameters of the - sending cmdlet. +- When you pipe an object to `Add-Content`, the object is converted to a string before it is added + to the item. The object type determines the string format, but the format might be different than + the default display of the object. To control the string format, use the formatting parameters of + the sending cmdlet. - You can also refer to `Add-Content` by its built-in alias, `ac`. For more information, see [about_Aliases](../Microsoft.PowerShell.Core/About/about_Aliases.md). - The `Add-Content` cmdlet is designed to work with the data exposed by any provider. To list the diff --git a/reference/7.0/Microsoft.PowerShell.Management/Set-Content.md b/reference/7.0/Microsoft.PowerShell.Management/Set-Content.md index f62d4202356b..1eb7c7b26116 100644 --- a/reference/7.0/Microsoft.PowerShell.Management/Set-Content.md +++ b/reference/7.0/Microsoft.PowerShell.Management/Set-Content.md @@ -2,7 +2,7 @@ external help file: Microsoft.PowerShell.Commands.Management.dll-Help.xml Locale: en-US Module Name: Microsoft.PowerShell.Management -ms.date: 12/18/2020 +ms.date: 11/03/2021 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.management/set-content?view=powershell-7&WT.mc_id=ps-gethelp schema: 2.0.0 title: Set-Content @@ -244,11 +244,13 @@ Accept wildcard characters: True ### -Filter -Specifies a filter to qualify the **Path** parameter. The [FileSystem](../Microsoft.PowerShell.Core/About/about_FileSystem_Provider.md) -provider is the only installed PowerShell provider that supports the use of filters. You can find -the syntax for the **FileSystem** filter language in [about_Wildcards](../Microsoft.PowerShell.Core/About/about_Wildcards.md). -Filters are more efficient than other parameters, because the provider applies them when the cmdlet -gets the objects rather than having PowerShell filter the objects after they are retrieved. +Specifies a filter to qualify the **Path** parameter. The +[FileSystem](../Microsoft.PowerShell.Core/About/about_FileSystem_Provider.md) provider is the only +installed PowerShell provider that supports the use of filters. You can find the syntax for the +**FileSystem** filter language in +[about_Wildcards](../Microsoft.PowerShell.Core/About/about_Wildcards.md). Filters are more efficient +than other parameters, because the provider applies them when the cmdlet gets the objects rather +than having PowerShell filter the objects after they are retrieved. ```yaml Type: System.String @@ -265,8 +267,9 @@ Accept wildcard characters: True ### -Force Forces the cmdlet to set the contents of a file, even if the file is read-only. Implementation -varies from provider to provider. For more information, see [about_Providers](../Microsoft.PowerShell.Core/About/about_Providers.md). -The **Force** parameter does not override security restrictions. +varies from provider to provider. For more information, see +[about_Providers](../Microsoft.PowerShell.Core/About/about_Providers.md). The **Force** parameter +does not override security restrictions. ```yaml Type: System.Management.Automation.SwitchParameter @@ -307,7 +310,8 @@ typed. No characters are interpreted as wildcards. If the path includes escape c it in single quotation marks. Single quotation marks tell PowerShell not to interpret any characters as escape sequences. -For more information, see [about_Quoting_Rules](../Microsoft.Powershell.Core/About/about_Quoting_Rules.md). +For more information, see +[about_Quoting_Rules](../Microsoft.Powershell.Core/About/about_Quoting_Rules.md). ```yaml Type: System.String[] diff --git a/reference/7.1/Microsoft.PowerShell.Management/Add-Content.md b/reference/7.1/Microsoft.PowerShell.Management/Add-Content.md index 8cae1dd86dc6..608a7b91f029 100644 --- a/reference/7.1/Microsoft.PowerShell.Management/Add-Content.md +++ b/reference/7.1/Microsoft.PowerShell.Management/Add-Content.md @@ -2,7 +2,7 @@ external help file: Microsoft.PowerShell.Commands.Management.dll-Help.xml Locale: en-US Module Name: Microsoft.PowerShell.Management -ms.date: 12/18/2020 +ms.date: 11/03/2021 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.management/add-content?view=powershell-7.1&WT.mc_id=ps-gethelp schema: 2.0.0 title: Add-Content @@ -54,6 +54,8 @@ The **Path** parameter specifies all `.txt` files in the current directory, but parameter ignores file names that match the specified pattern. The **Value** parameter specifies the text string that is written to the files. +Use [Get-Content](Get-Content.md) to display the contents of these files. + ### Example 2: Add a date to the end of the specified files This example appends the date to files in the current directory and displays the date in the @@ -70,10 +72,10 @@ Tuesday, May 14, 2019 8:24:27 AM 5/14/2019 8:24:27 AM ``` -The `Add-Content` cmdlet creates two new files in the current directory. The **Value** parameter contains -the output of the `Get-Date` cmdlet. The **PassThru** parameter outputs the added contents to the pipeline. -Because there is no other cmdlet to receive the output, it is displayed in the PowerShell console. -The `Get-Content` cmdlet displays the updated file, `DateTimeFile1.log`. +The `Add-Content` cmdlet creates two new files in the current directory. The **Value** parameter +contains the output of the `Get-Date` cmdlet. The **PassThru** parameter outputs the added contents +to the pipeline. Because there is no other cmdlet to receive the output, it is displayed in the +PowerShell console. The `Get-Content` cmdlet displays the updated file, `DateTimeFile1.log`. ### Example 3: Add the contents of a specified file to another file @@ -271,11 +273,13 @@ Accept wildcard characters: True ### -Filter -Specifies a filter to qualify the **Path** parameter. The [FileSystem](../Microsoft.PowerShell.Core/About/about_FileSystem_Provider.md) -provider is the only installed PowerShell provider that supports the use of filters. You can find -the syntax for the **FileSystem** filter language in [about_Wildcards](../Microsoft.PowerShell.Core/About/about_Wildcards.md). -Filters are more efficient than other parameters, because the provider applies them when the cmdlet -gets the objects rather than having PowerShell filter the objects after they are retrieved. +Specifies a filter to qualify the **Path** parameter. The +[FileSystem](../Microsoft.PowerShell.Core/About/about_FileSystem_Provider.md) provider is the only +installed PowerShell provider that supports the use of filters. You can find the syntax for the +**FileSystem** filter language in +[about_Wildcards](../Microsoft.PowerShell.Core/About/about_Wildcards.md). Filters are more efficient +than other parameters, because the provider applies them when the cmdlet gets the objects rather +than having PowerShell filter the objects after they are retrieved. ```yaml Type: System.String @@ -292,8 +296,7 @@ Accept wildcard characters: True ### -Force Overrides the read-only attribute, allowing you to add content to a read-only file. For example, -**Force** will override the read-only attribute or create directories to complete a file path, but -it will not attempt to change file permissions. +**Force** overrides the read-only attribute but it does not change file permissions. ```yaml Type: System.Management.Automation.SwitchParameter @@ -334,7 +337,8 @@ typed. No characters are interpreted as wildcards. If the path includes escape c it in single quotation marks. Single quotation marks tell PowerShell not to interpret any characters as escape sequences. -For more information, see [about_Quoting_Rules](../Microsoft.Powershell.Core/About/about_Quoting_Rules.md). +For more information, see +[about_Quoting_Rules](../Microsoft.Powershell.Core/About/about_Quoting_Rules.md). ```yaml Type: System.String[] @@ -386,11 +390,10 @@ Accept wildcard characters: False ### -Path -Specifies the path to the items that receive the additional content. -Wildcard characters are permitted. -The paths must be paths to items, not to containers. -For example, you must specify a path to one or more files, not a path to a directory. -If you specify multiple paths, use commas to separate the paths. +Specifies the path to the items that receive the additional content. Wildcard characters are +permitted. The paths must be paths to items, not to containers. For example, you must specify a path +to one or more files, not a path to a directory. If you specify multiple paths, use commas to +separate the paths. ```yaml Type: System.String[] @@ -415,11 +418,10 @@ it. Wildcard characters are not supported. **Stream** is a dynamic parameter that the FileSystem provider adds to `Add-Content`. This parameter works only in file system drives. -You can use the `Add-Content` cmdlet to change the content of any alternate -data stream, such as `Zone.Identifier`. However, we do not recommend this as -a way to eliminate security checks that block files that are downloaded from -the Internet. If you verify that a downloaded file is safe, use the -`Unblock-File` cmdlet. +You can use the `Add-Content` cmdlet to change the content of any alternate data stream, such as +`Zone.Identifier`. However, we do not recommend this as a way to eliminate security checks that +block files that are downloaded from the Internet. If you verify that a downloaded file is safe, use +the `Unblock-File` cmdlet. This parameter was introduced in PowerShell 3.0. @@ -510,10 +512,10 @@ represents the content. Otherwise, this cmdlet does not generate any output. ## Notes -- When you pipe an object to `Add-Content`, the object is converted to a string before it is added to - the item. The object type determines the string format, but the format might be different than the - default display of the object. To control the string format, use the formatting parameters of the - sending cmdlet. +- When you pipe an object to `Add-Content`, the object is converted to a string before it is added + to the item. The object type determines the string format, but the format might be different than + the default display of the object. To control the string format, use the formatting parameters of + the sending cmdlet. - You can also refer to `Add-Content` by its built-in alias, `ac`. For more information, see [about_Aliases](../Microsoft.PowerShell.Core/About/about_Aliases.md). - The `Add-Content` cmdlet is designed to work with the data exposed by any provider. To list the diff --git a/reference/7.1/Microsoft.PowerShell.Management/Set-Content.md b/reference/7.1/Microsoft.PowerShell.Management/Set-Content.md index 86f409e78150..548a6325d182 100644 --- a/reference/7.1/Microsoft.PowerShell.Management/Set-Content.md +++ b/reference/7.1/Microsoft.PowerShell.Management/Set-Content.md @@ -2,7 +2,7 @@ external help file: Microsoft.PowerShell.Commands.Management.dll-Help.xml Locale: en-US Module Name: Microsoft.PowerShell.Management -ms.date: 12/18/2020 +ms.date: 11/03/2021 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.management/set-content?view=powershell-7.1&WT.mc_id=ps-gethelp schema: 2.0.0 title: Set-Content @@ -249,11 +249,13 @@ Accept wildcard characters: True ### -Filter -Specifies a filter to qualify the **Path** parameter. The [FileSystem](../Microsoft.PowerShell.Core/About/about_FileSystem_Provider.md) -provider is the only installed PowerShell provider that supports the use of filters. You can find -the syntax for the **FileSystem** filter language in [about_Wildcards](../Microsoft.PowerShell.Core/About/about_Wildcards.md). -Filters are more efficient than other parameters, because the provider applies them when the cmdlet -gets the objects rather than having PowerShell filter the objects after they are retrieved. +Specifies a filter to qualify the **Path** parameter. The +[FileSystem](../Microsoft.PowerShell.Core/About/about_FileSystem_Provider.md) provider is the only +installed PowerShell provider that supports the use of filters. You can find the syntax for the +**FileSystem** filter language in +[about_Wildcards](../Microsoft.PowerShell.Core/About/about_Wildcards.md). Filters are more efficient +than other parameters, because the provider applies them when the cmdlet gets the objects rather +than having PowerShell filter the objects after they are retrieved. ```yaml Type: System.String @@ -270,8 +272,9 @@ Accept wildcard characters: True ### -Force Forces the cmdlet to set the contents of a file, even if the file is read-only. Implementation -varies from provider to provider. For more information, see [about_Providers](../Microsoft.PowerShell.Core/About/about_Providers.md). -The **Force** parameter does not override security restrictions. +varies from provider to provider. For more information, see +[about_Providers](../Microsoft.PowerShell.Core/About/about_Providers.md). The **Force** parameter +does not override security restrictions. ```yaml Type: System.Management.Automation.SwitchParameter @@ -312,7 +315,8 @@ typed. No characters are interpreted as wildcards. If the path includes escape c it in single quotation marks. Single quotation marks tell PowerShell not to interpret any characters as escape sequences. -For more information, see [about_Quoting_Rules](../Microsoft.Powershell.Core/About/about_Quoting_Rules.md). +For more information, see +[about_Quoting_Rules](../Microsoft.Powershell.Core/About/about_Quoting_Rules.md). ```yaml Type: System.String[] diff --git a/reference/7.2/Microsoft.PowerShell.Management/Add-Content.md b/reference/7.2/Microsoft.PowerShell.Management/Add-Content.md index bad3c322b28b..b0099e580f0a 100644 --- a/reference/7.2/Microsoft.PowerShell.Management/Add-Content.md +++ b/reference/7.2/Microsoft.PowerShell.Management/Add-Content.md @@ -2,7 +2,7 @@ external help file: Microsoft.PowerShell.Commands.Management.dll-Help.xml Locale: en-US Module Name: Microsoft.PowerShell.Management -ms.date: 12/18/2020 +ms.date: 11/03/2021 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.management/add-content?view=powershell-7.2&WT.mc_id=ps-gethelp schema: 2.0.0 title: Add-Content @@ -54,6 +54,8 @@ The **Path** parameter specifies all `.txt` files in the current directory, but parameter ignores file names that match the specified pattern. The **Value** parameter specifies the text string that is written to the files. +Use [Get-Content](Get-Content.md) to display the contents of these files. + ### Example 2: Add a date to the end of the specified files This example appends the date to files in the current directory and displays the date in the @@ -70,10 +72,10 @@ Tuesday, May 14, 2019 8:24:27 AM 5/14/2019 8:24:27 AM ``` -The `Add-Content` cmdlet creates two new files in the current directory. The **Value** parameter contains -the output of the `Get-Date` cmdlet. The **PassThru** parameter outputs the added contents to the pipeline. -Because there is no other cmdlet to receive the output, it is displayed in the PowerShell console. -The `Get-Content` cmdlet displays the updated file, `DateTimeFile1.log`. +The `Add-Content` cmdlet creates two new files in the current directory. The **Value** parameter +contains the output of the `Get-Date` cmdlet. The **PassThru** parameter outputs the added contents +to the pipeline. Because there is no other cmdlet to receive the output, it is displayed in the +PowerShell console. The `Get-Content` cmdlet displays the updated file, `DateTimeFile1.log`. ### Example 3: Add the contents of a specified file to another file @@ -271,11 +273,13 @@ Accept wildcard characters: True ### -Filter -Specifies a filter to qualify the **Path** parameter. The [FileSystem](../Microsoft.PowerShell.Core/About/about_FileSystem_Provider.md) -provider is the only installed PowerShell provider that supports the use of filters. You can find -the syntax for the **FileSystem** filter language in [about_Wildcards](../Microsoft.PowerShell.Core/About/about_Wildcards.md). -Filters are more efficient than other parameters, because the provider applies them when the cmdlet -gets the objects rather than having PowerShell filter the objects after they are retrieved. +Specifies a filter to qualify the **Path** parameter. The +[FileSystem](../Microsoft.PowerShell.Core/About/about_FileSystem_Provider.md) provider is the only +installed PowerShell provider that supports the use of filters. You can find the syntax for the +**FileSystem** filter language in +[about_Wildcards](../Microsoft.PowerShell.Core/About/about_Wildcards.md). Filters are more efficient +than other parameters, because the provider applies them when the cmdlet gets the objects rather +than having PowerShell filter the objects after they are retrieved. ```yaml Type: System.String @@ -292,8 +296,7 @@ Accept wildcard characters: True ### -Force Overrides the read-only attribute, allowing you to add content to a read-only file. For example, -**Force** will override the read-only attribute or create directories to complete a file path, but -it will not attempt to change file permissions. +**Force** overrides the read-only attribute but it does not change file permissions. ```yaml Type: System.Management.Automation.SwitchParameter @@ -334,7 +337,8 @@ typed. No characters are interpreted as wildcards. If the path includes escape c it in single quotation marks. Single quotation marks tell PowerShell not to interpret any characters as escape sequences. -For more information, see [about_Quoting_Rules](../Microsoft.Powershell.Core/About/about_Quoting_Rules.md). +For more information, see +[about_Quoting_Rules](../Microsoft.Powershell.Core/About/about_Quoting_Rules.md). ```yaml Type: System.String[] @@ -386,11 +390,10 @@ Accept wildcard characters: False ### -Path -Specifies the path to the items that receive the additional content. -Wildcard characters are permitted. -The paths must be paths to items, not to containers. -For example, you must specify a path to one or more files, not a path to a directory. -If you specify multiple paths, use commas to separate the paths. +Specifies the path to the items that receive the additional content. Wildcard characters are +permitted. The paths must be paths to items, not to containers. For example, you must specify a path +to one or more files, not a path to a directory. If you specify multiple paths, use commas to +separate the paths. ```yaml Type: System.String[] @@ -415,11 +418,10 @@ it. Wildcard characters are not supported. **Stream** is a dynamic parameter that the FileSystem provider adds to `Add-Content`. This parameter works only in file system drives. -You can use the `Add-Content` cmdlet to change the content of any alternate -data stream, such as `Zone.Identifier`. However, we do not recommend this as -a way to eliminate security checks that block files that are downloaded from -the Internet. If you verify that a downloaded file is safe, use the -`Unblock-File` cmdlet. +You can use the `Add-Content` cmdlet to change the content of any alternate data stream, such as +`Zone.Identifier`. However, we do not recommend this as a way to eliminate security checks that +block files that are downloaded from the Internet. If you verify that a downloaded file is safe, use +the `Unblock-File` cmdlet. This parameter was introduced in PowerShell 3.0. As of PowerShell 7.2, `Add-Content` can target alternative data streams on both files and directories. @@ -512,10 +514,10 @@ represents the content. Otherwise, this cmdlet does not generate any output. ## Notes -- When you pipe an object to `Add-Content`, the object is converted to a string before it is added to - the item. The object type determines the string format, but the format might be different than the - default display of the object. To control the string format, use the formatting parameters of the - sending cmdlet. +- When you pipe an object to `Add-Content`, the object is converted to a string before it is added + to the item. The object type determines the string format, but the format might be different than + the default display of the object. To control the string format, use the formatting parameters of + the sending cmdlet. - You can also refer to `Add-Content` by its built-in alias, `ac`. For more information, see [about_Aliases](../Microsoft.PowerShell.Core/About/about_Aliases.md). - The `Add-Content` cmdlet is designed to work with the data exposed by any provider. To list the diff --git a/reference/7.2/Microsoft.PowerShell.Management/Set-Content.md b/reference/7.2/Microsoft.PowerShell.Management/Set-Content.md index ca525c72cb02..2fa43087c6dd 100644 --- a/reference/7.2/Microsoft.PowerShell.Management/Set-Content.md +++ b/reference/7.2/Microsoft.PowerShell.Management/Set-Content.md @@ -2,7 +2,7 @@ external help file: Microsoft.PowerShell.Commands.Management.dll-Help.xml Locale: en-US Module Name: Microsoft.PowerShell.Management -ms.date: 12/18/2020 +ms.date: 11/03/2021 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.management/set-content?view=powershell-7.2&WT.mc_id=ps-gethelp schema: 2.0.0 title: Set-Content @@ -249,11 +249,13 @@ Accept wildcard characters: True ### -Filter -Specifies a filter to qualify the **Path** parameter. The [FileSystem](../Microsoft.PowerShell.Core/About/about_FileSystem_Provider.md) -provider is the only installed PowerShell provider that supports the use of filters. You can find -the syntax for the **FileSystem** filter language in [about_Wildcards](../Microsoft.PowerShell.Core/About/about_Wildcards.md). -Filters are more efficient than other parameters, because the provider applies them when the cmdlet -gets the objects rather than having PowerShell filter the objects after they are retrieved. +Specifies a filter to qualify the **Path** parameter. The +[FileSystem](../Microsoft.PowerShell.Core/About/about_FileSystem_Provider.md) provider is the only +installed PowerShell provider that supports the use of filters. You can find the syntax for the +**FileSystem** filter language in +[about_Wildcards](../Microsoft.PowerShell.Core/About/about_Wildcards.md). Filters are more efficient +than other parameters, because the provider applies them when the cmdlet gets the objects rather +than having PowerShell filter the objects after they are retrieved. ```yaml Type: System.String @@ -270,8 +272,9 @@ Accept wildcard characters: True ### -Force Forces the cmdlet to set the contents of a file, even if the file is read-only. Implementation -varies from provider to provider. For more information, see [about_Providers](../Microsoft.PowerShell.Core/About/about_Providers.md). -The **Force** parameter does not override security restrictions. +varies from provider to provider. For more information, see +[about_Providers](../Microsoft.PowerShell.Core/About/about_Providers.md). The **Force** parameter +does not override security restrictions. ```yaml Type: System.Management.Automation.SwitchParameter @@ -312,7 +315,8 @@ typed. No characters are interpreted as wildcards. If the path includes escape c it in single quotation marks. Single quotation marks tell PowerShell not to interpret any characters as escape sequences. -For more information, see [about_Quoting_Rules](../Microsoft.Powershell.Core/About/about_Quoting_Rules.md). +For more information, see +[about_Quoting_Rules](../Microsoft.Powershell.Core/About/about_Quoting_Rules.md). ```yaml Type: System.String[] From e341b87ee30e1d3a258f50e976926a94dae21be8 Mon Sep 17 00:00:00 2001 From: Matt Gucci Date: Thu, 4 Nov 2021 02:58:26 +0900 Subject: [PATCH 3/4] Remove redundant qualifiers: Provider types (#8302) For readability. --- .../developer/provider/provider-types.md | 144 +++++++++--------- 1 file changed, 72 insertions(+), 72 deletions(-) diff --git a/reference/docs-conceptual/developer/provider/provider-types.md b/reference/docs-conceptual/developer/provider/provider-types.md index e45827c3501b..5143b54be068 100644 --- a/reference/docs-conceptual/developer/provider/provider-types.md +++ b/reference/docs-conceptual/developer/provider/provider-types.md @@ -26,7 +26,7 @@ not want to allow the user to create and remove drives. To create a drive-enabled provider, your provider class must derive from the [System.Management.Automation.Provider.DriveCmdletProvider](/dotnet/api/System.Management.Automation.Provider.DriveCmdletProvider) class or another class that derives from that class. The -**System.Management.Automation.Provider.DriveCmdletProvider** class defines the following methods +**DriveCmdletProvider** class defines the following methods for implementing the default drives of the provider and supporting the `New-PSDrive` and `Remove-PSDrive` cmdlets. In most cases, to support a provider cmdlet you must overwrite the method that the PowerShell engine calls to invoke the cmdlet, such as the `NewDrive` method for the @@ -34,18 +34,18 @@ that the PowerShell engine calls to invoke the cmdlet, such as the `NewDrive` me `NewDriveDynamicParameters`, for adding dynamic parameters to the cmdlet. - The - [System.Management.Automation.Provider.DriveCmdletProvider.InitializeDefaultDrives](/dotnet/api/System.Management.Automation.Provider.DriveCmdletProvider.InitializeDefaultDrives) + [InitializeDefaultDrives](/dotnet/api/System.Management.Automation.Provider.DriveCmdletProvider.InitializeDefaultDrives) method defines the default drives that are available to the user whenever the provider is used. - The - [System.Management.Automation.Provider.DriveCmdletProvider.NewDrive](/dotnet/api/System.Management.Automation.Provider.DriveCmdletProvider.NewDrive) + [NewDrive](/dotnet/api/System.Management.Automation.Provider.DriveCmdletProvider.NewDrive) and - [System.Management.Automation.Provider.DriveCmdletProvider.NewDriveDynamicParameters](/dotnet/api/System.Management.Automation.Provider.DriveCmdletProvider.NewDriveDynamicParameters) + [NewDriveDynamicParameters](/dotnet/api/System.Management.Automation.Provider.DriveCmdletProvider.NewDriveDynamicParameters) methods defines how your provider supports the `New-PSDrive` provider cmdlet. This cmdlet allows the user to create drives to access the data store. - The - [System.Management.Automation.Provider.DriveCmdletProvider.RemoveDrive](/dotnet/api/System.Management.Automation.Provider.DriveCmdletProvider.RemoveDrive) + [RemoveDrive](/dotnet/api/System.Management.Automation.Provider.DriveCmdletProvider.RemoveDrive) method defines how your provider supports the `Remove-PSDrive` provider cmdlet. This cmdlet allows the user to remove drives from the data store. @@ -57,57 +57,57 @@ item-enabled provider, your provider class must derive from the [System.Management.Automation.Provider.ItemCmdletProvider](/dotnet/api/System.Management.Automation.Provider.ItemCmdletProvider) class or another class that derives from that class. -The **System.Management.Automation.Provider.ItemCmdletProvider** class defines the following methods +The **ItemCmdletProvider** class defines the following methods for implementing specific provider cmdlets. In most cases, to support a provider cmdlet you must overwrite the method that the PowerShell engine calls to invoke the cmdlet, such as the `ClearItem` method for the `Clear-Item` cmdlet, and optionally you can overwrite a second method, such as `ClearItemDynamicParameters`, for adding dynamic parameters to the cmdlet. - The - [System.Management.Automation.Provider.ItemCmdletProvider.ClearItem](/dotnet/api/System.Management.Automation.Provider.ItemCmdletProvider.ClearItem) + [ClearItem](/dotnet/api/System.Management.Automation.Provider.ItemCmdletProvider.ClearItem) and - [System.Management.Automation.Provider.ItemCmdletProvider.ClearItemDynamicParameters](/dotnet/api/System.Management.Automation.Provider.ItemCmdletProvider.ClearItemDynamicParameters) + [ClearItemDynamicParameters](/dotnet/api/System.Management.Automation.Provider.ItemCmdletProvider.ClearItemDynamicParameters) methods define how your provider supports the `Clear-Item` provider cmdlet. This cmdlet allows the user to remove of the value of an item in the data store. - The - [System.Management.Automation.Provider.ItemCmdletProvider.GetItem](/dotnet/api/System.Management.Automation.Provider.ItemCmdletProvider.GetItem) + [GetItem](/dotnet/api/System.Management.Automation.Provider.ItemCmdletProvider.GetItem) and - [System.Management.Automation.Provider.ItemCmdletProvider.GetItemDynamicParameters](/dotnet/api/System.Management.Automation.Provider.ItemCmdletProvider.GetItemDynamicParameters) + [GetItemDynamicParameters](/dotnet/api/System.Management.Automation.Provider.ItemCmdletProvider.GetItemDynamicParameters) methods define how your provider supports the `Get-Item` provider cmdlet. This cmdlet allows the user to retrieve data from the data store. - The - [System.Management.Automation.Provider.ItemCmdletProvider.SetItem](/dotnet/api/System.Management.Automation.Provider.ItemCmdletProvider.SetItem) + [SetItem](/dotnet/api/System.Management.Automation.Provider.ItemCmdletProvider.SetItem) and - [System.Management.Automation.Provider.ItemCmdletProvider.SetItemDynamicParameters](/dotnet/api/System.Management.Automation.Provider.ItemCmdletProvider.SetItemDynamicParameters) + [SetItemDynamicParameters](/dotnet/api/System.Management.Automation.Provider.ItemCmdletProvider.SetItemDynamicParameters) methods define how your provider supports the `Set-Item` provider cmdlet. This cmdlet allows the user to update the values of items in the data store. - The - [System.Management.Automation.Provider.Itemcmdletprovider.InvokeDefaultAction](/dotnet/api/System.Management.Automation.Provider.ItemCmdletProvider.InvokeDefaultAction) + [InvokeDefaultAction](/dotnet/api/System.Management.Automation.Provider.ItemCmdletProvider.InvokeDefaultAction) and - [System.Management.Automation.Provider.Itemcmdletprovider.InvokeDefaultActionDynamicParameters](/dotnet/api/system.management.automation.provider.itemcmdletprovider.invokedefaultactiondynamicparameters) + [InvokeDefaultActionDynamicParameters](/dotnet/api/system.management.automation.provider.itemcmdletprovider.invokedefaultactiondynamicparameters) methods define how your provider supports the `Invoke-Item` provider cmdlet. This cmdlet allows the user to perform the default action specified by the item. - The - [System.Management.Automation.Provider.ItemCmdletProvider.ItemExists](/dotnet/api/System.Management.Automation.Provider.ItemCmdletProvider.ItemExists) + [ItemExists](/dotnet/api/System.Management.Automation.Provider.ItemCmdletProvider.ItemExists) and - [System.Management.Automation.Provider.ItemCmdletProvider.ItemExistsDynamicParameters](/dotnet/api/System.Management.Automation.Provider.ItemCmdletProvider.ItemExistsDynamicParameters) + [ItemExistsDynamicParameters](/dotnet/api/System.Management.Automation.Provider.ItemCmdletProvider.ItemExistsDynamicParameters) methods define how your provider supports the `Test-Path` provider cmdlet. This cmdlet allows the user to determine if all the elements of a path exist. In addition to the methods used to implement provider cmdlets, the -**System.Management.Automation.Provider.ItemCmdletProvider** class also defines the following +**ItemCmdletProvider** class also defines the following methods: - The - [System.Management.Automation.Provider.ItemCmdletProvider.ExpandPath](/dotnet/api/System.Management.Automation.Provider.ItemCmdletProvider.ExpandPath) + [ExpandPath](/dotnet/api/System.Management.Automation.Provider.ItemCmdletProvider.ExpandPath) method allows the user to use wildcards when specifying the provider path. - The - [System.Management.Automation.Provider.ItemCmdletProvider.IsValidPath](/dotnet/api/System.Management.Automation.Provider.ItemCmdletProvider.IsValidPath) + [IsValidPath](/dotnet/api/System.Management.Automation.Provider.ItemCmdletProvider.IsValidPath) is used to determine if a path is syntactically and semantically valid for the provider. ## Container-enabled providers @@ -122,64 +122,64 @@ class or another class that derives from that class. > Container-enabled providers can't access data stores that contain nested containers. If a child > item of a container is another container, you must implement a navigation-enabled provider. -The **System.Management.Automation.Provider.ContainerCmdletProvider** class defines the following +The **ContainerCmdletProvider** class defines the following methods for implementing specific provider cmdlets. In most cases, to support a provider cmdlet you must overwrite the method that the PowerShell engine calls to invoke the cmdlet, such as the `CopyItem` method for the `Copy-Item` cmdlet, and optionally you can overwrite a second method, such as `CopyItemDynamicParameters`, for adding dynamic parameters to the cmdlet. - The - [System.Management.Automation.Provider.ContainerCmdletProvider.CopyItem](/dotnet/api/System.Management.Automation.Provider.ContainerCmdletProvider.CopyItem) + [CopyItem](/dotnet/api/System.Management.Automation.Provider.ContainerCmdletProvider.CopyItem) and - [System.Management.Automation.Provider.ContainerCmdletProvider.CopyItemDynamicParameters](/dotnet/api/System.Management.Automation.Provider.ContainerCmdletProvider.CopyItemDynamicParameters) + [CopyItemDynamicParameters](/dotnet/api/System.Management.Automation.Provider.ContainerCmdletProvider.CopyItemDynamicParameters) methods define how your provider supports the `Copy-Item` provider cmdlet. This cmdlet allows the user to copy an item from one location to another. - The - [System.Management.Automation.Provider.ContainerCmdletProvider.GetChildItems](/dotnet/api/System.Management.Automation.Provider.ContainerCmdletProvider.GetChildItems) + [GetChildItems](/dotnet/api/System.Management.Automation.Provider.ContainerCmdletProvider.GetChildItems) and - [System.Management.Automation.Provider.ContainerCmdletProvider.GetChildItemsDynamicParameters](/dotnet/api/System.Management.Automation.Provider.ContainerCmdletProvider.GetChildItemsDynamicParameters) + [GetChildItemsDynamicParameters](/dotnet/api/System.Management.Automation.Provider.ContainerCmdletProvider.GetChildItemsDynamicParameters) methods define how your provider supports the `Get-ChildItem` provider cmdlet. This cmdlet allows the user to retrieve the child items of the parent item. - The - [System.Management.Automation.Provider.ContainerCmdletProvider.GetChildNames](/dotnet/api/System.Management.Automation.Provider.ContainerCmdletProvider.GetChildNames) + [GetChildNames](/dotnet/api/System.Management.Automation.Provider.ContainerCmdletProvider.GetChildNames) and - [System.Management.Automation.Provider.ContainerCmdletProvider.GetChildNamesDynamicParameters](/dotnet/api/System.Management.Automation.Provider.ContainerCmdletProvider.GetChildNamesDynamicParameters) + [GetChildNamesDynamicParameters](/dotnet/api/System.Management.Automation.Provider.ContainerCmdletProvider.GetChildNamesDynamicParameters) methods define how your provider supports the `Get-ChildItem` provider cmdlet if its `Name` parameter is specified. - The - [System.Management.Automation.Provider.ContainerCmdletProvider.NewItem](/dotnet/api/System.Management.Automation.Provider.ContainerCmdletProvider.NewItem) + [NewItem](/dotnet/api/System.Management.Automation.Provider.ContainerCmdletProvider.NewItem) and - [System.Management.Automation.Provider.ContainerCmdletProvider.NewItemDynamicParameters](/dotnet/api/System.Management.Automation.Provider.ContainerCmdletProvider.NewItemDynamicParameters) + [NewItemDynamicParameters](/dotnet/api/System.Management.Automation.Provider.ContainerCmdletProvider.NewItemDynamicParameters) methods define how your provider supports the `New-Item` provider cmdlet. This cmdlet allows the user to create new items in the data store. - The - [System.Management.Automation.Provider.ContainerCmdletProvider.RemoveItem](/dotnet/api/System.Management.Automation.Provider.ContainerCmdletProvider.RemoveItem) + [RemoveItem](/dotnet/api/System.Management.Automation.Provider.ContainerCmdletProvider.RemoveItem) and - [System.Management.Automation.Provider.ContainerCmdletProvider.RemoveItemDynamicParameters](/dotnet/api/System.Management.Automation.Provider.ContainerCmdletProvider.RemoveItemDynamicParameters) + [RemoveItemDynamicParameters](/dotnet/api/System.Management.Automation.Provider.ContainerCmdletProvider.RemoveItemDynamicParameters) methods define how your provider supports the `Remove-Item` provider cmdlet. This cmdlet allows the user to remove items from the data store. - The - [System.Management.Automation.Provider.ContainerCmdletProvider.RenameItem](/dotnet/api/System.Management.Automation.Provider.ContainerCmdletProvider.RenameItem) + [RenameItem](/dotnet/api/System.Management.Automation.Provider.ContainerCmdletProvider.RenameItem) and - [System.Management.Automation.Provider.ContainerCmdletProvider.RenameItemDynamicParameters](/dotnet/api/System.Management.Automation.Provider.ContainerCmdletProvider.RenameItemDynamicParameters) + [RenameItemDynamicParameters](/dotnet/api/System.Management.Automation.Provider.ContainerCmdletProvider.RenameItemDynamicParameters) methods define how your provider supports the `Rename-Item` provider cmdlet. This cmdlet allows the user to rename items in the data store. In addition to the methods used to implement provider cmdlets, the -**System.Management.Automation.Provider.ContainerCmdletProvider** class also defines the following +**ContainerCmdletProvider** class also defines the following methods: - The - [System.Management.Automation.Provider.ContainerCmdletProvider.HasChildItems](/dotnet/api/System.Management.Automation.Provider.ContainerCmdletProvider.HasChildItems) + [HasChildItems](/dotnet/api/System.Management.Automation.Provider.ContainerCmdletProvider.HasChildItems) method can be used by the provider class to determine whether an item has child items. - The - [System.Management.Automation.Provider.ContainerCmdletProvider.ConvertPath](/dotnet/api/System.Management.Automation.Provider.ContainerCmdletProvider.ConvertPath) + [ConvertPath](/dotnet/api/System.Management.Automation.Provider.ContainerCmdletProvider.ConvertPath) method can be used by the provider class to create a new provider-specific path from a specified path. @@ -190,43 +190,43 @@ navigation-enabled provider, your provider class must derive from the [System.Management.Automation.Provider.NavigationCmdletProvider](/dotnet/api/System.Management.Automation.Provider.NavigationCmdletProvider) class. -The **System.Management.Automation.Provider.NavigationCmdletProvider** class defines the following +The **NavigationCmdletProvider** class defines the following methods for implementing specific provider cmdlets. In most cases, to support a provider cmdlet you must overwrite the method that the PowerShell engine calls to invoke the cmdlet, such as the `MoveItem` method for the `Move-Item` cmdlet, and optionally you can overwrite a second method, such as `MoveItemDynamicParameters`, for adding dynamic parameters to the cmdlet. - The - [System.Management.Automation.Provider.NavigationCmdletProvider.MoveItem](/dotnet/api/System.Management.Automation.Provider.NavigationCmdletProvider.MoveItem) + [MoveItem](/dotnet/api/System.Management.Automation.Provider.NavigationCmdletProvider.MoveItem) and - [System.Management.Automation.Provider.NavigationCmdletProvider.MoveItemDynamicParameters](/dotnet/api/System.Management.Automation.Provider.NavigationCmdletProvider.MoveItemDynamicParameters) + [MoveItemDynamicParameters](/dotnet/api/System.Management.Automation.Provider.NavigationCmdletProvider.MoveItemDynamicParameters) methods define how your provider supports the `Move-Item` provider cmdlet. This cmdlet allows the user to move an item from one location in the store to another location. - The - [System.Management.Automation.Provider.NavigationCmdletProvider.MakePath](/dotnet/api/System.Management.Automation.Provider.NavigationCmdletProvider.MakePath) + [MakePath](/dotnet/api/System.Management.Automation.Provider.NavigationCmdletProvider.MakePath) method defines how your provider supports the `Join-Path` provider cmdlet. This cmdlet allows the user to combine a parent and child path segment to create a provider-internal path. In addition to the methods used to implement provider cmdlets, the -**System.Management.Automation.Provider.NavigationCmdletProvider** class also defines the following +**NavigationCmdletProvider** class also defines the following methods: - The - [System.Management.Automation.Provider.NavigationCmdletProvider.GetChildName](/dotnet/api/System.Management.Automation.Provider.NavigationCmdletProvider.GetChildName) + [GetChildName](/dotnet/api/System.Management.Automation.Provider.NavigationCmdletProvider.GetChildName) method extracts the name of the child node of a path. - The - [System.Management.Automation.Provider.NavigationCmdletProvider.GetParentPath](/dotnet/api/System.Management.Automation.Provider.NavigationCmdletProvider.GetParentPath) + [GetParentPath](/dotnet/api/System.Management.Automation.Provider.NavigationCmdletProvider.GetParentPath) method extracts the parent part of a path. - The - [System.Management.Automation.Provider.NavigationCmdletProvider.IsItemContainer](/dotnet/api/System.Management.Automation.Provider.NavigationCmdletProvider.IsItemContainer) + [IsItemContainer](/dotnet/api/System.Management.Automation.Provider.NavigationCmdletProvider.IsItemContainer) method determines whether the item is a container item. In this context, a container is a group of child items under a common parent item. - The - [System.Management.Automation.Provider.NavigationCmdletProvider.NormalizeRelativePath](/dotnet/api/System.Management.Automation.Provider.NavigationCmdletProvider.NormalizeRelativePath) + [NormalizeRelativePath](/dotnet/api/System.Management.Automation.Provider.NavigationCmdletProvider.NormalizeRelativePath) method returns a path to an item that's relative to a specified base path. ## Content-enabled providers @@ -238,36 +238,36 @@ the [System.Management.Automation.Provider.IContentCmdletProvider](/dotnet/api/System.Management.Automation.Provider.IContentCmdletProvider) interface. -The **System.Management.Automation.Provider.IContentCmdletProvider** interface defines the following +The **IContentCmdletProvider** interface defines the following methods for implementing specific provider cmdlets. In most cases, to support a provider cmdlet you must overwrite the method that the PowerShell engine calls to invoke the cmdlet, such as the `ClearContent` method for the `Clear-Content` cmdlet, and optionally you can overwrite a second method, such as `ClearContentDynamicParameters`, for adding dynamic parameters to the cmdlet. - The - [System.Management.Automation.Provider.IContentCmdletProvider.ClearContent](/dotnet/api/System.Management.Automation.Provider.IContentCmdletProvider.ClearContent) + [ClearContent](/dotnet/api/System.Management.Automation.Provider.IContentCmdletProvider.ClearContent) and - [System.Management.Automation.Provider.IContentCmdletProvider.ClearContentDynamicParameters](/dotnet/api/System.Management.Automation.Provider.IContentCmdletProvider.ClearContentDynamicParameters) + [ClearContentDynamicParameters](/dotnet/api/System.Management.Automation.Provider.IContentCmdletProvider.ClearContentDynamicParameters) methods define how your provider supports the `Clear-Content` provider cmdlet. This cmdlet allows the user to delete the content of an item without deleting the item. - The - [System.Management.Automation.Provider.IContentCmdletProvider.GetContentReader](/dotnet/api/System.Management.Automation.Provider.IContentCmdletProvider.GetContentReader) + [GetContentReader](/dotnet/api/System.Management.Automation.Provider.IContentCmdletProvider.GetContentReader) and - [System.Management.Automation.Provider.IContentCmdletProvider.GetContentReaderDynamicParameters](/dotnet/api/System.Management.Automation.Provider.IContentCmdletProvider.GetContentReaderDynamicParameters) + [GetContentReaderDynamicParameters](/dotnet/api/System.Management.Automation.Provider.IContentCmdletProvider.GetContentReaderDynamicParameters) methods define how your provider supports the `Get-Content` provider cmdlet. This cmdlet allows the user to retrieve the content of an item. The - `System.Management.Automation.Provider.IContentCmdletProvider.GetContentReader` method returns an + `GetContentReader` method returns an [System.Management.Automation.Provider.IContentReader](/dotnet/api/System.Management.Automation.Provider.IContentReader) interface that defines the methods used to read the content. - The - [System.Management.Automation.Provider.IContentCmdletProvider.GetContentWriter](/dotnet/api/System.Management.Automation.Provider.IContentCmdletProvider.GetContentWriter) + [GetContentWriter](/dotnet/api/System.Management.Automation.Provider.IContentCmdletProvider.GetContentWriter) and - [System.Management.Automation.Provider.IContentCmdletProvider.GetContentWriterDynamicParameters](/dotnet/api/System.Management.Automation.Provider.IContentCmdletProvider.GetContentWriterDynamicParameters) + [GetContentWriterDynamicParameters](/dotnet/api/System.Management.Automation.Provider.IContentCmdletProvider.GetContentWriterDynamicParameters) methods define how your provider supports the `Set-Content` provider cmdlet. This cmdlet allows the user to update the content of an item. The - `System.Management.Automation.Provider.IContentCmdletProvider.GetContentWriter` method returns an + `GetContentWriter` method returns an [System.Management.Automation.Provider.IContentWriter](/dotnet/api/System.Management.Automation.Provider.IContentWriter) interface that defines the methods used to write the content. @@ -283,65 +283,65 @@ PowerShell engine calls to invoke the cmdlet, such as the `ClearProperty` method Clear-Property cmdlet, and optionally you can overwrite a second method, such as `ClearPropertyDynamicParameters`, for adding dynamic parameters to the cmdlet. -The **System.Management.Automation.Provider.IPropertyCmdletProvider** interface defines the +The **IPropertyCmdletProvider** interface defines the following methods for implementing specific provider cmdlets: - The - [System.Management.Automation.Provider.IPropertyCmdletProvider.ClearProperty](/dotnet/api/System.Management.Automation.Provider.IPropertyCmdletProvider.ClearProperty) + [ClearProperty](/dotnet/api/System.Management.Automation.Provider.IPropertyCmdletProvider.ClearProperty) and - [System.Management.Automation.Provider.IPropertyCmdletProvider.ClearPropertyDynamicParameters](/dotnet/api/System.Management.Automation.Provider.IPropertyCmdletProvider.ClearPropertyDynamicParameters) + [ClearPropertyDynamicParameters](/dotnet/api/System.Management.Automation.Provider.IPropertyCmdletProvider.ClearPropertyDynamicParameters) methods define how your provider supports the `Clear-ItemProperty` provider cmdlet. This cmdlet allows the user to delete the value of a property. - The - [System.Management.Automation.Provider.IPropertyCmdletProvider.GetProperty](/dotnet/api/System.Management.Automation.Provider.IPropertyCmdletProvider.GetProperty) + [GetProperty](/dotnet/api/System.Management.Automation.Provider.IPropertyCmdletProvider.GetProperty) and - [System.Management.Automation.Provider.IPropertyCmdletProvider.GetPropertyDynamicParameters](/dotnet/api/System.Management.Automation.Provider.IPropertyCmdletProvider.GetPropertyDynamicParameters) + [GetPropertyDynamicParameters](/dotnet/api/System.Management.Automation.Provider.IPropertyCmdletProvider.GetPropertyDynamicParameters) methods define how your provider supports the `Get-ItemProperty` provider cmdlet. This cmdlet allows the user to retrieve the property of an item. - The - [System.Management.Automation.Provider.IPropertyCmdletProvider.SetProperty](/dotnet/api/System.Management.Automation.Provider.IPropertyCmdletProvider.SetProperty) + [SetProperty](/dotnet/api/System.Management.Automation.Provider.IPropertyCmdletProvider.SetProperty) and - [System.Management.Automation.Provider.IPropertyCmdletProvider.SetPropertyDynamicParameters](/dotnet/api/System.Management.Automation.Provider.IPropertyCmdletProvider.SetPropertyDynamicParameters) + [SetPropertyDynamicParameters](/dotnet/api/System.Management.Automation.Provider.IPropertyCmdletProvider.SetPropertyDynamicParameters) methods define how your provider supports the `Set-ItemProperty` provider cmdlet. This cmdlet allows the user to update the properties of an item. - The **System.Management.Automation.Provider.IDynamicPropertyCmdletProvider** interface defines the - following methods for implementing specific provider cmdlets: +The **IDynamicPropertyCmdletProvider** interface defines the +following methods for implementing specific provider cmdlets: - The - [System.Management.Automation.Provider.IDynamicPropertyCmdletProvider.CopyProperty](/dotnet/api/System.Management.Automation.Provider.IDynamicPropertyCmdletProvider.CopyProperty) + [CopyProperty](/dotnet/api/System.Management.Automation.Provider.IDynamicPropertyCmdletProvider.CopyProperty) and - [System.Management.Automation.Provider.IDynamicPropertyCmdletProvider.CopyPropertyDynamicParameters](/dotnet/api/System.Management.Automation.Provider.IDynamicPropertyCmdletProvider.CopyPropertyDynamicParameters) + [CopyPropertyDynamicParameters](/dotnet/api/System.Management.Automation.Provider.IDynamicPropertyCmdletProvider.CopyPropertyDynamicParameters) methods define how your provider supports the `Copy-ItemProperty` provider cmdlet. This cmdlet allows the user to copy a property and its value from one location to another. - The - [System.Management.Automation.Provider.IDynamicPropertyCmdletProvider.MoveProperty](/dotnet/api/System.Management.Automation.Provider.IDynamicPropertyCmdletProvider.MoveProperty) + [MoveProperty](/dotnet/api/System.Management.Automation.Provider.IDynamicPropertyCmdletProvider.MoveProperty) and - [System.Management.Automation.Provider.IDynamicPropertyCmdletProvider.MovePropertyDynamicParameters](/dotnet/api/System.Management.Automation.Provider.IDynamicPropertyCmdletProvider.MovePropertyDynamicParameters) + [MovePropertyDynamicParameters](/dotnet/api/System.Management.Automation.Provider.IDynamicPropertyCmdletProvider.MovePropertyDynamicParameters) methods define how your provider supports the `Move-ItemProperty` provider cmdlet. This cmdlet allows the user to move a property and its value from one location to another. - The - [System.Management.Automation.Provider.IDynamicPropertyCmdletProvider.NewProperty](/dotnet/api/System.Management.Automation.Provider.IDynamicPropertyCmdletProvider.NewProperty) + [NewProperty](/dotnet/api/System.Management.Automation.Provider.IDynamicPropertyCmdletProvider.NewProperty) and - [System.Management.Automation.Provider.IDynamicPropertyCmdletProvider.NewPropertyDynamicParameters](/dotnet/api/System.Management.Automation.Provider.IDynamicPropertyCmdletProvider.NewPropertyDynamicParameters) + [NewPropertyDynamicParameters](/dotnet/api/System.Management.Automation.Provider.IDynamicPropertyCmdletProvider.NewPropertyDynamicParameters) methods define how your provider supports the `New-ItemProperty` provider cmdlet. This cmdlet allows the user to create a new property and set its value. - The - [System.Management.Automation.Provider.IDynamicPropertyCmdletProvider.RemoveProperty](/dotnet/api/System.Management.Automation.Provider.IDynamicPropertyCmdletProvider.RemoveProperty) + [RemoveProperty](/dotnet/api/System.Management.Automation.Provider.IDynamicPropertyCmdletProvider.RemoveProperty) and - [System.Management.Automation.Provider.IDynamicPropertyCmdletProvider.RemovePropertyDynamicParameters](/dotnet/api/System.Management.Automation.Provider.IDynamicPropertyCmdletProvider.RemovePropertyDynamicParameters) + [RemovePropertyDynamicParameters](/dotnet/api/System.Management.Automation.Provider.IDynamicPropertyCmdletProvider.RemovePropertyDynamicParameters) methods define how your provider supports the `Remove-ItemProperty` cmdlet. This cmdlet allows the user to delete a property and its value. - The - [System.Management.Automation.Provider.IDynamicPropertyCmdletProvider.RenameProperty](/dotnet/api/System.Management.Automation.Provider.IDynamicPropertyCmdletProvider.RenameProperty) + [RenameProperty](/dotnet/api/System.Management.Automation.Provider.IDynamicPropertyCmdletProvider.RenameProperty) and - [System.Management.Automation.Provider.IDynamicPropertyCmdletProvider.RenamePropertyDynamicParameters](/dotnet/api/System.Management.Automation.Provider.IDynamicPropertyCmdletProvider.RenamePropertyDynamicParameters) + [RenamePropertyDynamicParameters](/dotnet/api/System.Management.Automation.Provider.IDynamicPropertyCmdletProvider.RenamePropertyDynamicParameters) methods define how your provider supports the `Rename-ItemProperty` cmdlet. This cmdlet allows the user to change the name of a property. From 5b4875e89a9fe906cffc684ce93fa497c53d8d11 Mon Sep 17 00:00:00 2001 From: Sean Wheeler Date: Wed, 3 Nov 2021 15:24:23 -0500 Subject: [PATCH 4/4] Update for rc.1 and remove Ubuntu 21.04 (#8303) --- .../Installing-PowerShell-on-Windows.md | 10 ++++----- .../install/Installing-PowerShell-on-macOS.md | 22 +++++++++---------- .../docs-conceptual/install/install-alpine.md | 8 +++---- .../docs-conceptual/install/install-centos.md | 8 +++---- .../docs-conceptual/install/install-debian.md | 4 ++-- .../docs-conceptual/install/install-fedora.md | 8 +++---- .../install/install-raspbian.md | 4 ++-- .../docs-conceptual/install/install-rhel.md | 8 +++---- .../docs-conceptual/install/install-ubuntu.md | 9 ++++---- 9 files changed, 40 insertions(+), 41 deletions(-) diff --git a/reference/docs-conceptual/install/Installing-PowerShell-on-Windows.md b/reference/docs-conceptual/install/Installing-PowerShell-on-Windows.md index 3a5e44c7f4d0..03a1f876752d 100644 --- a/reference/docs-conceptual/install/Installing-PowerShell-on-Windows.md +++ b/reference/docs-conceptual/install/Installing-PowerShell-on-Windows.md @@ -1,6 +1,6 @@ --- description: Information about installing PowerShell on Windows -ms.date: 10/22/2021 +ms.date: 11/03/2021 title: Installing PowerShell on Windows --- # Installing PowerShell on Windows @@ -172,15 +172,15 @@ For more information, see The preview version of PowerShell 7.2 can be downloaded using the following link: -- [PowerShell-7.2.0-preview.10-win-x64.msi][72x64msi] +- [PowerShell-7.2.0-rc.1-win-x64.msi][72x64msi] Preview releases of PowerShell 7 install to `$env:ProgramFiles\PowerShell\7-preview` so they can -be run side-by-side with non-preview releases of PowerShell. PowerShell 7.2-preview.10 is the +be run side-by-side with non-preview releases of PowerShell. PowerShell 7.2-rc.1 is the current preview release. ### Support for Microsoft Update in PowerShell 7.2 -PowerShell 7.2-preview.10 has support for Microsoft Update. When you enable this feature, you'll get +PowerShell 7.2-rc.1 has support for Microsoft Update. When you enable this feature, you'll get the latest PowerShell 7 updates in your traditional Microsoft Update (MU) management flow, whether that's with Windows Update for Business, WSUS, SCCM, or the interactive MU dialog in Settings. @@ -357,4 +357,4 @@ cannot support those methods. [x64zip]: https://github.com/PowerShell/PowerShell/releases/download/v7.1.5/PowerShell-7.1.5-win-x64.zip [x86msi]: https://github.com/PowerShell/PowerShell/releases/download/v7.1.5/PowerShell-7.1.5-win-x86.msi [x86zip]: https://github.com/PowerShell/PowerShell/releases/download/v7.1.5/PowerShell-7.1.5-win-x86.zip -[72x64msi]: https://github.com/PowerShell/PowerShell/releases/download/v7.2.0-preview.10/PowerShell-7.2.0-preview.10-win-x64.msi +[72x64msi]: https://github.com/PowerShell/PowerShell/releases/download/v7.2.0-rc.1/PowerShell-7.2.0-rc.1-win-x64.msi diff --git a/reference/docs-conceptual/install/Installing-PowerShell-on-macOS.md b/reference/docs-conceptual/install/Installing-PowerShell-on-macOS.md index 6691f8de3392..0e97163a7f99 100644 --- a/reference/docs-conceptual/install/Installing-PowerShell-on-macOS.md +++ b/reference/docs-conceptual/install/Installing-PowerShell-on-macOS.md @@ -1,6 +1,6 @@ --- description: Information about installing PowerShell on macOS -ms.date: 10/15/2021 +ms.date: 11/03/2021 title: Installing PowerShell on macOS --- @@ -126,9 +126,9 @@ brew upgrade powershell PowerShell 7.2 adds support for the Apple M1 processor. Download the install package from the [releases][releases] page onto your computer. The links to the current versions are: -- PowerShell 7.2-preview.10 - - x64 processors - [powershell-7.2.0-preview.10-osx-x64.pkg][72x64pkg] - - M1 processors - [powershell-7.2.0-preview.10-osx-arm64.pkg][72m1pkg] +- PowerShell 7.2-rc.1 + - x64 processors - [powershell-7.2.0-rc.1-osx-x64.pkg][72x64pkg] + - M1 processors - [powershell-7.2.0-rc.1-osx-arm64.pkg][72m1pkg] - PowerShell 7.1.5 - [powershell-7.1.5-osx-x64.pkg][71x64pkg] - PowerShell 7.0.8 - [powershell-7.0.8-osx-x64.pkg][70x64pkg] @@ -178,9 +178,9 @@ operations. Download the install package from the [releases][releases] page onto your computer. The links to the current versions are: -- PowerShell 7.2-preview.10 - - x64 processors - [powershell-7.2.0-preview.10-osx-x64.tar.gz][72x64bin] - - M1 processors - [powershell-7.2.0-preview.10-osx-arm64.tar.gz][72m1bin] +- PowerShell 7.2-rc.1 + - x64 processors - [powershell-7.2.0-rc.1-osx-x64.tar.gz][72x64bin] + - M1 processors - [powershell-7.2.0-rc.1-osx-arm64.tar.gz][72m1bin] - PowerShell 7.1.5 - [powershell-7.1.5-osx-x64.tar.gz][71x64bin] - PowerShell 7.0.8 - [powershell-7.0.8-osx-x64.tar.gz][70x64bin] @@ -300,12 +300,12 @@ support those methods. [lts]: https://aka.ms/powershell-release?tag=lts [preview]: https://aka.ms/powershell-release?tag=preview -[72x64pkg]: https://github.com/PowerShell/PowerShell/releases/download/v7.2.0-preview.10/powershell-7.2.0-preview.10-osx-x64.pkg -[72m1pkg]: https://github.com/PowerShell/PowerShell/releases/download/v7.2.0-preview.10/powershell-7.2.0-preview.10-osx-arm64.pkg +[72x64pkg]: https://github.com/PowerShell/PowerShell/releases/download/v7.2.0-rc.1/powershell-7.2.0-rc.1-osx-x64.pkg +[72m1pkg]: https://github.com/PowerShell/PowerShell/releases/download/v7.2.0-rc.1/powershell-7.2.0-rc.1-osx-arm64.pkg [71x64pkg]: https://github.com/PowerShell/PowerShell/releases/download/v7.1.5/powershell-7.1.5-osx-x64.pkg [70x64pkg]: https://github.com/PowerShell/PowerShell/releases/download/v7.0.8/powershell-7.0.8-osx-x64.pkg -[72x64bin]: https://github.com/PowerShell/PowerShell/releases/download/v7.2.0-preview.10/powershell-7.2.0-preview.10-osx-x64.tar.gz -[72m1bin]: https://github.com/PowerShell/PowerShell/releases/download/v7.2.0-preview.10/powershell-7.2.0-preview.10-osx-arm64.tar.gz +[72x64bin]: https://github.com/PowerShell/PowerShell/releases/download/v7.2.0-rc.1/powershell-7.2.0-rc.1-osx-x64.tar.gz +[72m1bin]: https://github.com/PowerShell/PowerShell/releases/download/v7.2.0-rc.1/powershell-7.2.0-rc.1-osx-arm64.tar.gz [71x64bin]: https://github.com/PowerShell/PowerShell/releases/download/v7.1.5/powershell-7.1.5-osx-x64.tar.gz [70x64bin]: https://github.com/PowerShell/PowerShell/releases/download/v7.0.8/powershell-7.0.8-osx-x64.tar.gz diff --git a/reference/docs-conceptual/install/install-alpine.md b/reference/docs-conceptual/install/install-alpine.md index 9b78b701c8a3..d0ee92f1a242 100644 --- a/reference/docs-conceptual/install/install-alpine.md +++ b/reference/docs-conceptual/install/install-alpine.md @@ -1,6 +1,6 @@ --- description: Information about installing PowerShell on Alpine Linux -ms.date: 10/15/2021 +ms.date: 11/03/2021 title: Installing PowerShell on Alpine Linux --- # Installing PowerShell on Alpine Linux @@ -20,11 +20,11 @@ installing, check the list of [Supported versions](#supported-versions) below. Installation on Alpine is based on downloading tar.gz package from the [releases][releases] page. The URL to the package depends on the version of PowerShell you want to install. -- PowerShell 7.2-preview.10 - `https://github.com/PowerShell/PowerShell/releases/download/v7.2.0-preview.10/powershell-7.2.0-preview.10-linux-alpine-x64.tar.gz` +- PowerShell 7.2-rc.1 - `https://github.com/PowerShell/PowerShell/releases/download/v7.2.0-rc.1/powershell-7.2.0-rc.1-linux-alpine-x64.tar.gz` - PowerShell 7.1 - `https://github.com/PowerShell/PowerShell/releases/download/v7.1.5/powershell-7.1.5-linux-alpine-x64.tar.gz` - PowerShell 7.0 - `https://github.com/PowerShell/PowerShell/releases/download/v7.0.8/powershell-7.0.8-linux-alpine-x64.tar.gz` -Then, in the terminal, execute the following shell commands to install PowerShell 7.2-preview.10: +Then, in the terminal, execute the following shell commands to install PowerShell 7.2-rc.1: ```sh # install the requirements @@ -47,7 +47,7 @@ sudo apk -X https://dl-cdn.alpinelinux.org/alpine/edge/main add --no-cache \ lttng-ust # Download the powershell '.tar.gz' archive -curl -L https://github.com/PowerShell/PowerShell/releases/download/v7.2.0-preview.10/powershell-7.2.0-preview.10-linux-alpine-x64.tar.gz -o /tmp/powershell.tar.gz +curl -L https://github.com/PowerShell/PowerShell/releases/download/v7.2.0-rc.1/powershell-7.2.0-rc.1-linux-alpine-x64.tar.gz -o /tmp/powershell.tar.gz # Create the target folder where powershell will be placed sudo mkdir -p /opt/microsoft/powershell/7 diff --git a/reference/docs-conceptual/install/install-centos.md b/reference/docs-conceptual/install/install-centos.md index 882c8de049f6..2822c89acbd2 100644 --- a/reference/docs-conceptual/install/install-centos.md +++ b/reference/docs-conceptual/install/install-centos.md @@ -1,6 +1,6 @@ --- description: Information about installing PowerShell on CentOS -ms.date: 10/15/2021 +ms.date: 11/03/2021 title: Installing PowerShell on CentOS --- # Installing PowerShell on CentOS @@ -46,7 +46,7 @@ with `sudo yum update powershell`. PowerShell 7.2 is distributed as a universal RPM package. Previous versions of PowerShell had separate package for each OS. Download the RPM package you need onto your CentOS machine. -- PowerShell 7.2-preview.10 - `https://github.com/PowerShell/PowerShell/releases/download/v7.2.0-preview.10/powershell-preview-7.2.0_preview.10-1.rh.x86_64.rpm` +- PowerShell 7.2-rc.1 - `https://github.com/PowerShell/PowerShell/releases/download/v7.2.0-rc.1/powershell-preview-7.2.0_rc.1-1.rh.x86_64.rpm` - PowerShell 7.1.5 - CentOS 7 - `https://github.com/PowerShell/PowerShell/releases/download/v7.1.5/powershell-7.1.5-1.rhel.7.x86_64.rpm` - CentOS 8 - `https://github.com/PowerShell/PowerShell/releases/download/v7.1.5/powershell-7.1.5-1.centos.8.x86_64.rpm` @@ -59,13 +59,13 @@ Change the URL in the following shell commands to match the version you need. On CentOS 7: ```sh -sudo yum install https://github.com/PowerShell/PowerShell/releases/download/v7.2.0-preview.10/powershell-preview-7.2.0_preview.10-1.rh.x86_64.rpm +sudo yum install https://github.com/PowerShell/PowerShell/releases/download/v7.2.0-rc.1/powershell-preview-7.2.0_rc.1-1.rh.x86_64.rpm ``` On CentOS 8: ```sh -sudo dnf install https://github.com/PowerShell/PowerShell/releases/download/v7.2.0-preview.10/powershell-preview-7.2.0_preview.10-1.rh.x86_64.rpm +sudo dnf install https://github.com/PowerShell/PowerShell/releases/download/v7.2.0-rc.1/powershell-preview-7.2.0_rc.1-1.rh.x86_64.rpm ``` ## Uninstall PowerShell from CentOS diff --git a/reference/docs-conceptual/install/install-debian.md b/reference/docs-conceptual/install/install-debian.md index c3b3c2fc543d..fb783e5286ec 100644 --- a/reference/docs-conceptual/install/install-debian.md +++ b/reference/docs-conceptual/install/install-debian.md @@ -1,6 +1,6 @@ --- description: Information about installing PowerShell on Debian Linux -ms.date: 10/15/2021 +ms.date: 11/03/2021 title: Installing PowerShell on Debian Linux --- # Installing PowerShell on Debian Linux @@ -28,7 +28,7 @@ PowerShell 7.2 introduced a universal package that makes installation easier. Do package from the [releases][releases] page onto the Debian 10 machine. The link to the current version is: -- PowerShell 7.2-preview.10 - `https://github.com/PowerShell/PowerShell/releases/download/v7.2.0-preview.10/powershell-preview_7.2.0-preview.10-1.deb_amd64.deb` +- PowerShell 7.2-rc.1 - `https://github.com/PowerShell/PowerShell/releases/download/v7.2.0-rc.1/powershell-preview_7.2.0-rc.1-1.deb_amd64.deb` - PowerShell 7.1.5 - Debian 10 - `https://github.com/PowerShell/PowerShell/releases/download/v7.1.5/powershell_7.1.5-1.debian.10_amd64.deb` - Debian 9 - `https://github.com/PowerShell/PowerShell/releases/download/v7.1.5/powershell_7.1.5-1.debian.9_amd64.deb` diff --git a/reference/docs-conceptual/install/install-fedora.md b/reference/docs-conceptual/install/install-fedora.md index 5eb115cb3189..2dd07e3b4ac5 100644 --- a/reference/docs-conceptual/install/install-fedora.md +++ b/reference/docs-conceptual/install/install-fedora.md @@ -1,6 +1,6 @@ --- description: Information about installing PowerShell on Fedora Linux -ms.date: 10/15/2021 +ms.date: 11/03/2021 title: Installing PowerShell on Fedora Linux --- # Installing PowerShell on Fedora Linux @@ -48,14 +48,14 @@ PowerShell 7.2 introduced a universal package that makes installation easier. Th contains the dependencies needed by the package. Download the RPM package from the [releases][releases] page onto your openSUSE computer. The links to the current versions are: -- PowerShell 7.2-preview.10 - `https://github.com/PowerShell/PowerShell/releases/download/v7.2.0-preview.10/powershell-preview-7.2.0_preview.10-1.rh.x86_64.rpm` +- PowerShell 7.2-rc.1 - `https://github.com/PowerShell/PowerShell/releases/download/v7.2.0-rc.1/powershell-preview-7.2.0_rc.1-1.rh.x86_64.rpm` - PowerShell 7.1.5 - `https://github.com/PowerShell/PowerShell/releases/download/v7.1.5/powershell-7.1.5-1.rhel.7.x86_64.rpm` - PowerShell 7.0.8 - `https://github.com/PowerShell/PowerShell/releases/download/v7.0.8/powershell-7.0.8-1.rhel.7.x86_64.rpm` -The following shell command installs PowerShell 7.2-preview.10: +The following shell command installs PowerShell 7.2-rc.1: ```sh -sudo dnf install https://github.com/PowerShell/PowerShell/releases/download/v7.2.0-preview.10/powershell-preview-7.2.0_preview.10-1.rh.x86_64.rpm +sudo dnf install https://github.com/PowerShell/PowerShell/releases/download/v7.2.0-rc.1/powershell-preview-7.2.0_rc.1-1.rh.x86_64.rpm ``` Use the following shell commands to download and install the package. Change the URL to match the diff --git a/reference/docs-conceptual/install/install-raspbian.md b/reference/docs-conceptual/install/install-raspbian.md index 5530be31362d..babaa4673218 100644 --- a/reference/docs-conceptual/install/install-raspbian.md +++ b/reference/docs-conceptual/install/install-raspbian.md @@ -1,6 +1,6 @@ --- description: Information about installing PowerShell on Raspberry Pi OS -ms.date: 10/14/2021 +ms.date: 11/03/2021 title: Installing PowerShell on Raspberry Pi OS --- # Installing PowerShell on Raspberry Pi OS @@ -27,7 +27,7 @@ run `pwsh` from a terminal. Run `pwsh-preview` if you installed a preview releas Download the tar.gz package from the [releases][releases] page onto your Raspberry Pi computer. The links to the current versions are: -- PowerShell 7.2-preview.10 - `https://github.com/PowerShell/PowerShell/releases/download/v7.2.0-preview.10/powershell-7.2.0-preview.10-linux-arm32.tar.gz` +- PowerShell 7.2-rc.1 - `https://github.com/PowerShell/PowerShell/releases/download/v7.2.0-rc.1/powershell-7.2.0-rc.1-linux-arm32.tar.gz` - PowerShell 7.1.5 - `https://github.com/PowerShell/PowerShell/releases/download/v7.1.5/powershell-7.1.5-linux-arm32.tar.gz` - PowerShell 7.0.8 - `https://github.com/PowerShell/PowerShell/releases/download/v7.0.8/powershell-7.0.8-linux-arm32.tar.gz` diff --git a/reference/docs-conceptual/install/install-rhel.md b/reference/docs-conceptual/install/install-rhel.md index 9174f65c9f64..6a61f5d4fd4f 100644 --- a/reference/docs-conceptual/install/install-rhel.md +++ b/reference/docs-conceptual/install/install-rhel.md @@ -1,6 +1,6 @@ --- description: Information about installing PowerShell on Red Hat Enterprise Linux (RHEL) -ms.date: 10/15/2021 +ms.date: 11/03/2021 title: Installing PowerShell on Red Hat Enterprise Linux (RHEL) --- # Installing PowerShell on Red Hat Enterprise Linux (RHEL) @@ -59,7 +59,7 @@ with `sudo dnf upgrade powershell`. PowerShell 7.2 is distributed as a universal RPM package. Previous versions of PowerShell had separate package for each OS. Download the RPM package you need onto your CentOS machine. -- PowerShell 7.2-preview.10 - `https://github.com/PowerShell/PowerShell/releases/download/v7.2.0-preview.10/powershell-preview-7.2.0_preview.10-1.rh.x86_64.rpm` +- PowerShell 7.2-rc.1 - `https://github.com/PowerShell/PowerShell/releases/download/v7.2.0-rc.1/powershell-preview-7.2.0_rc.1-1.rh.x86_64.rpm` - PowerShell 7.1.5 - CentOS 7 - `https://github.com/PowerShell/PowerShell/releases/download/v7.1.5/powershell-7.1.5-1.rhel.7.x86_64.rpm` - CentOS 8 - `https://github.com/PowerShell/PowerShell/releases/download/v7.1.5/powershell-7.1.5-1.centos.8.x86_64.rpm` @@ -73,13 +73,13 @@ URL in the following shell commands to match the version you need. On RHEL 7: ```sh -sudo yum install https://github.com/PowerShell/PowerShell/releases/download/v7.2.0-preview.10/powershell-preview-7.2.0_preview.10-1.rh.x86_64.rpm +sudo yum install https://github.com/PowerShell/PowerShell/releases/download/v7.2.0-rc.1/powershell-preview-7.2.0_rc.1-1.rh.x86_64.rpm ``` On RHEL 8: ```sh -sudo dnf install https://github.com/PowerShell/PowerShell/releases/download/v7.2.0-preview.10/powershell-preview-7.2.0_preview.10-1.rh.x86_64.rpm +sudo dnf install https://github.com/PowerShell/PowerShell/releases/download/v7.2.0-rc.1/powershell-preview-7.2.0_rc.1-1.rh.x86_64.rpm ``` ## Uninstallation - Red Hat Enterprise Linux (RHEL) 7 diff --git a/reference/docs-conceptual/install/install-ubuntu.md b/reference/docs-conceptual/install/install-ubuntu.md index 233c83b31c92..139e95157fa1 100644 --- a/reference/docs-conceptual/install/install-ubuntu.md +++ b/reference/docs-conceptual/install/install-ubuntu.md @@ -1,6 +1,6 @@ --- description: Information about installing PowerShell on Ubuntu -ms.date: 10/15/2021 +ms.date: 11/03/2021 title: Installing PowerShell on Ubuntu --- # Installing PowerShell on Ubuntu @@ -23,7 +23,6 @@ Ubuntu uses APT (Advanced Package Tool) as a package manager. PowerShell for Linux is published to package repositories for easy installation and updates. The URL to the package varies by OS version: -- Ubuntu 21.04 - `https://packages.microsoft.com/config/ubuntu/21.04/packages-microsoft-prod.deb` - Ubuntu 20.04 - `https://packages.microsoft.com/config/ubuntu/20.04/packages-microsoft-prod.deb` - Ubuntu 18.04 - `https://packages.microsoft.com/config/ubuntu/18.04/packages-microsoft-prod.deb` @@ -56,8 +55,8 @@ PowerShell 7.2 introduced a universal package that makes installation easier. Do package from the [releases][releases] page onto the Ubuntu machine. The link to the current version is: -- PowerShell 7.2-preview.10 (universal package) for any support version of Ubuntu - - `https://github.com/PowerShell/PowerShell/releases/download/v7.2.0-preview.10/powershell-preview_7.2.0-preview.10-1.deb_amd64.deb` +- PowerShell 7.2-rc.1 (universal package) for any support version of Ubuntu + - `https://github.com/PowerShell/PowerShell/releases/download/v7.2.0-rc.1/powershell-preview_7.2.0-rc.1-1.deb_amd64.deb` - PowerShell 7.1.5 - Ubuntu 20.04 - `https://github.com/PowerShell/PowerShell/releases/download/v7.1.5/powershell_7.1.5-1.ubuntu.20.04_amd64.deb` - Ubuntu 18.04 - `https://github.com/PowerShell/PowerShell/releases/download/v7.1.5/powershell_7.1.5-1.ubuntu.18.04_amd64.deb` @@ -70,7 +69,7 @@ the version you downloaded. ```sh # Install the downloaded package -sudo dpkg -i powershell-preview_7.2.0-preview.10-1.deb_amd64.deb +sudo dpkg -i powershell-preview_7.2.0-rc.1-1.deb_amd64.deb # Resolve missing dependencies and finish the install (if necessary) sudo apt-get install -f