Updates from: 07/24/2021 03:12:12
Service Microsoft Docs article Related commit history on GitHub Change details
Microsoft.PowerShell.Core About Automatic Variables (7.2) https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Core/About/about_Automatic_Variables.md
--- description: Describes variables that store state information for PowerShell. These variables are created and maintained by PowerShell. Locale: en-US Previously updated : 07/06/2021 Last updated : 07/22/2021 no-loc: [Reset, Current, Background, Blink, Bold, Foreground, Formatting, Hidden, Italic, Reset, Reverse, Underline] online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_automatic_variables?view=powershell-7.2&WT.mc_id=ps-gethelp schema: 2.0.0
following properties:
- **BlinkOff** - Turns Blink off - **Bold** - Turns Bold on - **BoldOff** - Turns Bold off
+- **FileInfo** - Controls coloring of **FileInfo** objects.
- **Foreground** - Nested object to control foreground coloring - **Formatting** - Controls default formatting for output streams - **Hidden** - Turns Hidden on
contain the ANSI escape sequences for the 16 standard console colors as well as
an `Rgb()` method to specify 24-bit color. The values are settable and can contain any number of ANSI escape sequences.
+`$PSStyle.FileInfo` is a nested object to control the coloring of **FileInfo**
+objects.
+
+- **Directory** - Built-in member to specify color for directories
+- **SymbolicLink** - Built-in member to specify color for symbolic links
+- **Executable** - Built-in member to specify color for executables.
+- **Extension** - Use this member to define colors for different file
+ extensions. The **Extension** member pre-includes extensions for archive and
+ PowerShell files.
+ `$PSStyle.Formatting` is a nested object to control default formatting of debug, error, verbose, and warning messages. You can also control attributes like bolding and underlining. It replaces `$Host.PrivateData` as the way to
dsc Packagemanagementdscresource https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/docs-conceptual/dsc/reference/resources/packagemanagement/PackageManagementDscResource.md
PackageManagement [string] #ResourceName
|Property |Description | |---|---| |Name |Specifies the name of the Package to be installed or uninstalled. |
-|AdditionalParameters |Provider specific hashtable of parameters that would be passed to `Get-Package -AdditionalArguments`. For example, for NuGet provider you can pass additional parameters like DestinationPath. |
+|AdditionalParameters |Provider specific hashtable of parameters that would be passed to `Get-Package -AdditionalArguments`. For example, for NuGet provider you can pass additional parameters like **Destination**. |
|MaximumVersion |Specifies the maximum allowed version of the package that you want to find. If you do not add this parameter, the resource finds the highest available version of the package. | |MinimumVersion |Specifies the minimum allowed version of the package that you want to find. If you do not add this parameter, the resource finds the highest available version of the package that also satisfies any maximum specified version specified by the **MaximumVersion** parameter. | |ProviderName |Specifies a package provider name to which to scope your package search. You can get package provider names by running the `Get-PackageProvider` cmdlet. |
The following table lists options for the AdditionalParameters property.
|Parameter |Description | |---|---|
-|DestinationPath |Used by providers such as the built-in Nuget Provider. Specifies a file location where you want the package to be installed. |
+|Destination |Used by providers such as the built-in Nuget Provider. Specifies a file location where you want the package to be installed. |
|InstallationPolicy |Used by providers such as the built-in Nuget Provider. Determines whether you trust the package's source. One of: **Untrusted** or **Trusted**. | ## Common properties
learn Experimental Features https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/docs-conceptual/learn/experimental-features.md
--- Previously updated : 06/22/2021 Last updated : 07/22/2021 Title: Using Experimental Features in PowerShell description: Lists the currently available experimental features and how to use them. ---
Blink Property string Blink {get;}
BlinkOff Property string BlinkOff {get;} Bold Property string Bold {get;} BoldOff Property string BoldOff {get;}
+FileInfo Property System.Management.Automation.PSStyle+FileInfoFormatting {get;}
Foreground Property System.Management.Automation.PSStyle+ForegroundColor Foreground {get;} Formatting Property System.Management.Automation.PSStyle+FormattingData Formatting {get;} Hidden Property string Hidden {get;}
The following values of `$env:TERM` change the behavior as follows:
If `$env:NO_COLOR` exists, then sets `$PSStyle.OutputRendering = PlainText`. For more information, see [https://no-color.org/](https://no-color.org/).
+## PSAnsiRenderingFileInfo
+
+This experiment was added in PowerShell 7.2. This feature adds the $PSStyle.FileInfo member and
+enables coloring of specific file types.
+
+- `$PSStyle.FileInfo.Directory` - Built-in member to specify color for directories
+- `$PSStyle.FileInfo.SymbolicLink` - Built-in member to specify color for symbolic links
+- `$PSStyle.FileInfo.Executable` - Built-in member to specify color for executables.
+- `$PSStyle.FileInfo.Extension` - Use this member to define colors for different file extensions.
+ The **Extension** member pre-includes extensions for archive and PowerShell files.
+
+For more information, see [about_Automatic_Variables](/powershell/module/Microsoft.PowerShell.Core/About/about_Automatic_Variables.md)
+
+> [!NOTE]
+> You must have the **PSAnsiRendering** experimental feature enabled to use this feature.
+ ## PSAnsiProgress This experiment was added in PowerShell 7.2. The feature adds the `$PSStyle.Progress` member and