Publish to live

.github/ISSUE_TEMPLATE/Documentation_Issue.md

@@ -36,6 +36,7 @@ Be sure to change the issue title. Titles should be brief and meaningful.
 
 **Cmdlet reference & about_ topics**
 - [ ] Preview content
+- [ ] Version 7.2 content
 - [ ] Version 7.1 content
 - [ ] Version 7.0 content
 - [ ] Version 5.1 content

.github/PULL_REQUEST_TEMPLATE.md

@@ -29,6 +29,7 @@ Select the area of the Table of Contents containing the documents being changed.
 
 **Cmdlet reference & about_ topics**
 - [ ] Preview content
+- [ ] Version 7.2 content
 - [ ] Version 7.1 content
 - [ ] Version 7.0 content
 - [ ] Version 5.1 content

README.md

@@ -35,7 +35,7 @@ The following list describes the main folders in this repository.
   - `5.1` - contains the cmdlet reference and about topics for PowerShell 5.1
   - `7.0` - contains the cmdlet reference and about topics for PowerShell 7.0
   - `7.1` - contains the cmdlet reference and about topics for PowerShell 7.1
-  - `7.2` - contains the cmdlet reference and about topics for PowerShell 7.2 (preview)
+  - `7.2` - contains the cmdlet reference and about topics for PowerShell 7.2
   - `bread` - contains the TOC used for breadcrumb navigation
   - `docs-conceptual` - contains the conceptual articles that are published to the Docs site. In
     general, the folder structure mirrors the Table of Contents (TOC).

reference/5.1/Microsoft.PowerShell.Core/About/about_Redirection.md

@@ -232,7 +232,7 @@ truncated to 80 characters:
 ```Output
 Name                         Value
 ----                         -----
-Path                         C:\Program Files\PowerShell\7-preview;C:\WINDOWS…
+Path                         C:\Program Files\PowerShell\7;C:\WINDOWS…
 ```
 
 Considering that the console width may be set arbitrarily on systems where

reference/7.0/Microsoft.PowerShell.Core/About/about_PowerShell_Config.md

@@ -220,7 +220,7 @@ Where:
 > You may want to have different **LogIdentity** values for each different
 > instance of PowerShell you have installed.
 
-In this example, we are configuring the **LogIdentity** for a preview release
+In this example, we are configuring the **LogIdentity** for a  release
 of PowerShell.
 
 ```json

reference/7.0/Microsoft.PowerShell.Core/About/about_Redirection.md

@@ -232,7 +232,7 @@ truncated to 80 characters:
 ```Output
 Name                         Value
 ----                         -----
-Path                         C:\Program Files\PowerShell\7-preview;C:\WINDOWS…
+Path                         C:\Program Files\PowerShell\7;C:\WINDOWS…
 ```
 
 Considering that the console width may be set arbitrarily on systems where

reference/7.2/Microsoft.PowerShell.Core/About/about_Redirection.md

@@ -232,7 +232,7 @@ truncated to 80 characters:
 ```Output
 Name                         Value
 ----                         -----
-Path                         C:\Program Files\PowerShell\7-preview;C:\WINDOWS…
+Path                         C:\Program Files\PowerShell\7;C:\WINDOWS…
 ```
 
 Considering that the console width may be set arbitrarily on systems where

reference/docs-conceptual/dev-cross-plat/create-standard-library-binary-Module.md

@@ -1,7 +1,7 @@
 ---
 description: The PowerShell Standard Library allows us to create cross platform modules that work in both PowerShell and with Windows PowerShell 5.1.
 ms.custom: contributor-KevinMarquette
-ms.date: 10/22/2021
+ms.date: 11/08/2021
 title: How to create a Standard Library Binary Module
 ---
 # How to create a Standard Library binary module
@@ -110,7 +110,7 @@ most recent version available for the level of compatibility that you need. I wo
 latest version but I don't think this module leverages any features newer than PowerShell 3.0.
 
 ```powershell
-dotnet add package PowerShellStandard.Library --version 7.0.0-preview.1
+dotnet add package PowerShellStandard.Library --version 7.2.0
 ```
 
 We should have a src folder that looks like this:

reference/docs-conceptual/developer/prog-guide/creating-a-windows-powershell-container-provider.md

@@ -41,11 +41,6 @@ A Windows PowerShell container provider must define a .NET class that derives fr
 base class. Here is the class definition for the Windows PowerShell container provider described in
 this section.
 
-```csharp
-[CmdletProvider("AccessDB", ProviderCapabilities.None)]
-public class AccessDBProvider : ContainerCmdletProvider
-```
-
 :::code language="csharp" source="~/../powershell-sdk-samples/SDK-2.0/csharp/AccessDBProviderSample04/AccessDBProviderSample04.cs" range="34-35":::
 
 Notice that in this class definition, the
@@ -96,61 +91,6 @@ method for this provider. Notice that this method retrieves the child items in a
 when the path indicates the Access database, and retrieves the child items from the rows of that
 table if the path indicates a data table.
 
-```csharp
-protected override void GetChildItems(string path, bool recurse)
-{
-    // If path represented is a drive then the children in the path are
-    // tables. Hence all tables in the drive represented will have to be
-    // returned
-    if (PathIsDrive(path))
-    {
-        foreach (DatabaseTableInfo table in GetTables())
-        {
-            WriteItemObject(table, path, true);
-
-            // if the specified item exists and recurse has been set then
-            // all child items within it have to be obtained as well
-            if (ItemExists(path) && recurse)
-            {
-                GetChildItems(path + pathSeparator + table.Name, recurse);
-            }
-        } // foreach (DatabaseTableInfo...
-    } // if (PathIsDrive...
-    else
-    {
-        // Get the table name, row number and type of path from the
-        // path specified
-        string tableName;
-        int rowNumber;
-
-        PathType type = GetNamesFromPath(path, out tableName, out rowNumber);
-
-        if (type == PathType.Table)
-        {
-            // Obtain all the rows within the table
-            foreach (DatabaseRowInfo row in GetRows(tableName))
-            {
-                WriteItemObject(row, path + pathSeparator + row.RowNumber,
-                        false);
-            } // foreach (DatabaseRowInfo...
-        }
-        else if (type == PathType.Row)
-        {
-            // In this case the user has directly specified a row, hence
-            // just give that particular row
-            DatabaseRowInfo row = GetRow(tableName, rowNumber);
-            WriteItemObject(row, path + pathSeparator + row.RowNumber,
-                        false);
-        }
-        else
-        {
-            // In this case, the path specified is not valid
-            ThrowTerminatingInvalidPathException(path);
-        }
-    } // else
-} // GetChildItems
-```
-
 :::code language="csharp" source="~/../powershell-sdk-samples/SDK-2.0/csharp/AccessDBProviderSample04/AccessDBProviderSample04.cs" range="311-362":::
 
 #### Things to Remember About Implementing GetChildItems
@@ -222,52 +162,6 @@ Here is the implementation of the
 method for this provider. Notice that the method retrieves table names if the specified path
 indicates the Access database (drive) and row numbers if the path indicates a table.
 
-```csharp
-protected override void GetChildNames(string path,
-                            ReturnContainers returnContainers)
-{
-    // If the path represented is a drive, then the child items are
-    // tables. get the names of all the tables in the drive.
-    if (PathIsDrive(path))
-    {
-        foreach (DatabaseTableInfo table in GetTables())
-        {
-            WriteItemObject(table.Name, path, true);
-        } // foreach (DatabaseTableInfo...
-    } // if (PathIsDrive...
-    else
-    {
-        // Get type, table name and row number from path specified
-        string tableName;
-        int rowNumber;
-
-        PathType type = GetNamesFromPath(path, out tableName, out rowNumber);
-
-        if (type == PathType.Table)
-        {
-            // Get all the rows in the table and then write out the
-            // row numbers.
-            foreach (DatabaseRowInfo row in GetRows(tableName))
-            {
-                WriteItemObject(row.RowNumber, path, false);
-            } // foreach (DatabaseRowInfo...
-        }
-        else if (type == PathType.Row)
-        {
-            // In this case the user has directly specified a row, hence
-            // just give that particular row
-            DatabaseRowInfo row = GetRow(tableName, rowNumber);
-
-            WriteItemObject(row.RowNumber, path, false);
-        }
-        else
-        {
-            ThrowTerminatingInvalidPathException(path);
-        }
-    } // else
-} // GetChildNames
-```
-
 :::code language="csharp" source="~/../powershell-sdk-samples/SDK-2.0/csharp/AccessDBProviderSample04/AccessDBProviderSample04.cs" range="369-411":::
 
 #### Things to Remember About Implementing GetChildNames

reference/docs-conceptual/dsc/pull-server/pullServer.md

@@ -1,6 +1,6 @@
 ---
 description: Local Configuration Manager (LCM) can be centrally managed by a Pull Service solution. When using this approach, the node that is being managed is registered with a service and assigned a configuration in LCM settings.
-ms.date: 11/01/2021
+ms.date: 11/08/2021
 title: DSC Pull Service
 ---
 
@@ -87,9 +87,9 @@ example script is provided below.
 
 ### Supported database systems
 
-| WMF 4.0 |       WMF 5.0        |       WMF 5.1        | WMF 5.1 (Windows Server Insider Preview 17090) |
-| ------- | -------------------- | -------------------- | ---------------------------------------------- |
-| MDB     | ESENT (Default), MDB | ESENT (Default), MDB | ESENT (Default), SQL Server, MDB               |
+| WMF 4.0 |       WMF 5.0        |       WMF 5.1        |             WMF 5.1              |
+| ------- | -------------------- | -------------------- | -------------------------------- |
+| MDB     | ESENT (Default), MDB | ESENT (Default), MDB | ESENT (Default), SQL Server, MDB |
 
 Starting in release 17090 of Windows Server, SQL Server is a supported option for the Pull Service
 (Windows Feature *DSC-Service*). This provides a new option for scaling large DSC environments that

reference/docs-conceptual/dsc/pull-server/secureServer.md

@@ -1,6 +1,6 @@
 ---
 description: This document provide best practices to assist engineers that are deploying the DSC Pull Server.
-ms.date: 06/12/2017
+ms.date: 11/08/2021
 title: Pull server best practices
 ---
 # Pull server best practices
@@ -111,8 +111,8 @@ ready to be used in a production environment even while WMF is released in previ
 that have historically been updated by WMF releases (see the WMF Release Notes for further detail):
 
 - Windows PowerShell Windows PowerShell Integrated Scripting
-- Environment (ISE) Windows PowerShell Web Services (Management OData
-- IIS Extension)  Windows PowerShell Desired State Configuration (DSC)
+- Environment (ISE) Windows PowerShell Web Services (Management OData IIS Extension)
+- Windows PowerShell Desired State Configuration (DSC)
 - Windows Remote Management (WinRM) Windows Management Instrumentation (WMI)
 
 ### DSC resource

reference/docs-conceptual/install/Installing-PowerShell-on-Linux.md

@@ -1,6 +1,6 @@
 ---
 description: Learn about the Linux distributions supported by PowerShell.
-ms.date: 09/22/2021
+ms.date: 11/08/2021
 title: Install PowerShell on Linux
 ---
 # Install PowerShell on Linux
@@ -79,9 +79,10 @@ PowerShell may be supported by the community for these releases. For more inform
 
 ## Alternate installation methods
 
-There are three other ways to install PowerShell on Linux, including Linux distributions that aren't officially supported. You can try to install PowerShell using
-the PowerShell Snap Package. You can also try deploying PowerShell binaries directly using the Linux
-`tar.gz`. For more information, see [Alternate ways to install PowerShell on Linux][other-linux].
+There are three other ways to install PowerShell on Linux, including Linux distributions that aren't
+officially supported. You can try to install PowerShell using the PowerShell Snap Package. You can
+also try deploying PowerShell binaries directly using the Linux `tar.gz`. For more information, see
+[Alternate ways to install PowerShell on Linux][other-linux].
 
 [community]: community-support.md
 [other-linux]: install-other-linux.md