MicrosoftDocs · Jak-MS · Aug 19, 2022 · Aug 17, 2022 · Aug 17, 2022 · Aug 18, 2022
diff --git a/docs/javascript/tutorial-asp-net-core-with-angular.md b/docs/javascript/tutorial-asp-net-core-with-angular.md
@@ -1,7 +1,7 @@
 ---
 title: "Create an ASP.NET Core app with Angular"
 description: In this tutorial, you create an app using ASP.NET Core and Angular
-ms.date: 06/17/2022
+ms.date: 08/17/2022
 ms.topic: tutorial
 ms.devlang: javascript
 author: mikejo5000
@@ -27,9 +27,6 @@ Starting in Visual Studio 2022 Preview 2, you can use the method described in th
 - Put the client app in a separate project, outside from the ASP.NET Core project
 - Create the client project based on the framework CLI installed on your computer
 
->[!NOTE]
-> Currently, the front-end project must be published manually (not currently supported with the Publish tool). For additional information, see [https://github.com/MicrosoftDocs/visualstudio-docs/issues/7135](https://github.com/MicrosoftDocs/visualstudio-docs/issues/7135).
-
 ## Prerequisites
 
 Make sure to install the following:
@@ -124,7 +121,40 @@ Before you start the project, make sure that the port numbers match.
    >[!NOTE]
    > Check console output for messages, such as a message instructing you to update your version of Node.js.
 
-You should see an Angular app appear, that is populated via the API.
+You should see an Angular app appear, that is populated via the API. If you don't see the app, see [Troubleshooting](#troubleshooting).
+
+## Publish the project
+
+Starting in Visual Studio 2022 version 17.3, you can publish the integrated solution using the Visual Studio Publish tool.
+
+>[!NOTE]
+> To use publish, create your JavaScript project using Visual Studio 2022 version 17.3 or later.
+
+1. In Solution Explorer, right-click the ASP.NET Core project and choose **Add** > **Project Reference**.
+
+1. Select the Angular project and choose **OK**.
+
+1. Right-click the ASP.NET Core project in Solution Explorer and choose **Unload Project**.
+
+   This opens the *.csproj* file for the project.
+
+1. In the *.csproj* file, update the project reference and add `<ReferenceOutputAssembly>` with the value set to `false`.
+
+   When you've updated the reference, it should look like this (substituting your own project folder and project name).
+
+   ```xml
+   <ProjectReference Include="..\angularprojectfolder\angularprojectname.esproj">
+       <ReferenceOutputAssembly>false</ReferenceOutputAssembly>
+   </ProjectReference>
+   ```
+
+1. Right-click the ASP.NET Core project and choose **Reload Project**.
+
+1. To publish, right click the ASP.NET Core project, choose **Publish**, and select options to match your desired publish scenario, such as Azure, publish to a folder, et al.
+
+   The publish process takes more time than it does for just an ASP.NET Core project, since the `npm run build command` gets invoked when publishing.
+
+   You can modify the `npm run build` command using the **Production Build Command** in the Angular project properties. To modify it, right-click the Angular project in Solution Explorer and choose **Properties**.
 
 ## Troubleshooting
 

diff --git a/docs/javascript/tutorial-asp-net-core-with-react.md b/docs/javascript/tutorial-asp-net-core-with-react.md
@@ -1,7 +1,7 @@
 ---
 title: "Create an ASP.NET Core app with React"
 description: In this tutorial, you create an app using ASP.NET Core and React
-ms.date: 06/17/2022
+ms.date: 08/17/2022
 ms.topic: tutorial
 ms.devlang: javascript
 author: mikejo5000
@@ -27,9 +27,6 @@ Starting in Visual Studio 2022 Preview 2, you can use the method described in th
 - Put the client app in a separate project, outside from the ASP.NET Core project
 - Create the client project based on the framework CLI installed on your computer
 
-> [!NOTE]
-> Currently, the front-end project must be published manually (not currently supported with the Publish tool). For additional information, see [https://github.com/MicrosoftDocs/visualstudio-docs/issues/7135](https://github.com/MicrosoftDocs/visualstudio-docs/issues/7135).
-
 ## Prerequisites
 
 Make sure to install the following:
@@ -122,7 +119,40 @@ Make sure to install the following:
    >[!NOTE]
    > Check console output for messages, such as a message instructing you to update your version of Node.js.
 
-You should see an React app appear, that is populated via the API.
+You should see a React app appear, that is populated via the API. If you don't see the app, see [Troubleshooting](#troubleshooting).
+
+## Publish the project
+
+Starting in Visual Studio 2022 version 17.3, you can publish the integrated solution using the Visual Studio Publish tool.
+
+>[!NOTE]
+> To use publish, create your JavaScript project using Visual Studio 2022 version 17.3 or later.
+
+1. In Solution Explorer, right-click the ASP.NET Core project and choose **Add** > **Project Reference**.
+
+1. Select the React project and choose **OK**.
+
+1. Right-click the ASP.NET Core project in Solution Explorer and choose **Unload project**.
+
+   This opens the *.csproj* file for the project.
+
+1. In the *.csproj* file, update the project reference and add `<ReferenceOutputAssembly>` with the value set to `false`.
+
+   When you've updated the reference, it should look like this (substituting your own project folder and project name).
+
+   ```xml
+   <ProjectReference Include="..\reactprojectfolder\reactprojectname.esproj">
+       <ReferenceOutputAssembly>false</ReferenceOutputAssembly>
+   </ProjectReference>
+   ```
+
+1. Right-click the ASP.NET Core project and choose **Reload Project**.
+
+1. To publish, right click the ASP.NET Core project, choose **Publish**, and select options to match your desired publish scenario, such as Azure, publish to a folder, et al.
+
+   The publish process takes more time than it does for just an ASP.NET Core project, since the `npm run build command` gets invoked when publishing.
+
+   You can modify the `npm run build` command using the **Production Build Command** in the React project properties. To modify it, right-click the React project in Solution Explorer and choose **Properties**.
 
 ## Troubleshooting
 

diff --git a/docs/javascript/tutorial-asp-net-core-with-vue.md b/docs/javascript/tutorial-asp-net-core-with-vue.md
@@ -1,7 +1,7 @@
 ---
 title: "Create an ASP.NET Core app with Vue"
 description: In this tutorial, you create an app using ASP.NET Core and Vue
-ms.date: 06/17/2022
+ms.date: 08/17/2022
 ms.topic: tutorial
 ms.devlang: javascript
 author: mikejo5000
@@ -27,9 +27,6 @@ Starting in Visual Studio 2022 Preview 2, you can use the method described in th
 - Put the client app in a separate project, outside from the ASP.NET Core project
 - Create the client project based on the framework CLI installed on your computer
 
-> [!NOTE]
-> Currently, the front-end project must be published manually (not currently supported with the Publish tool). For additional information, see [https://github.com/MicrosoftDocs/visualstudio-docs/issues/7135](https://github.com/MicrosoftDocs/visualstudio-docs/issues/7135).
-
 ## Prerequisites
 
 Make sure to install the following:
@@ -132,7 +129,40 @@ Once the project is created, you see some new and modified files:
    >[!NOTE]
    > Check console output for messages, such as a message instructing you to update your version of Node.js.
 
-You should see the Vue app appear, that is populated via the API.
+You should see the Vue app appear, that is populated via the API. If you don't see the app, see [Troubleshooting](#troubleshooting).
+
+## Publish the project
+
+Starting in Visual Studio 2022 version 17.3, you can publish the integrated solution using the Visual Studio Publish tool.
+
+>[!NOTE]
+> To use publish, create your JavaScript project using Visual Studio 2022 version 17.3 or later.
+
+1. In Solution Explorer, right-click the ASP.NET Core project and choose **Add** > **Project Reference**.
+
+1. Select the Vue project and choose **OK**.
+
+1. Right-click the ASP.NET Core project in Solution Explorer and choose **Unload project**.
+
+   This opens the *.csproj* file for the project.
+
+1. In the *.csproj* file, update the project reference and add `<ReferenceOutputAssembly>` with the value set to `false`.
+
+   When you've updated the reference, it should look like this (substituting your own project folder and project name).
+
+   ```xml
+   <ProjectReference Include="..\vueprojectfolder\vueprojectname.esproj">
+       <ReferenceOutputAssembly>false</ReferenceOutputAssembly>
+   </ProjectReference>
+   ```
+
+1. Right-click the ASP.NET Core project and choose **Reload Project**.
+
+1. To publish, right click the ASP.NET Core project, choose **Publish**, and select options to match your desired publish scenario, such as Azure, publish to a folder, et al.
+
+   The publish process takes more time than it does for just an ASP.NET Core project, since the `npm run build` command gets invoked when publishing.
+
+   You can modify the `npm run build` command using the **Production Build Command** in the Vue project properties. To modify it, right-click the Vue project in Solution Explorer and choose **Properties**.
 
 ## Troubleshooting
 

diff --git a/subscriptions/migrate-subscriptions.md b/subscriptions/migrate-subscriptions.md
@@ -4,7 +4,7 @@ author: evanwindom
 ms.author: amast
 manager: shve
 ms.assetid: 80e3b300-f2fc-40d4-bbb2-c831a2fa5d34
-ms.date: 07/11/2022
+ms.date: 08/18/2022
 ms.topic: how-to
 description:  This article describes how admins can migrate assigned subscriptions from one agreement to another.
 ---
@@ -107,14 +107,14 @@ Take these steps to open your exported subscriptions list and move the relevant
    | Downloads                  | Downloads          |
    | Country                    | Country            |
    | Language                   | Language           |
-   | Subscription GUID          | Subscription GUID  |
+
 
    > [!IMPORTANT] 
-   > Do not copy date from the **Subscription GUID** column into the bulk add template.  Including the GUIDs will cause the upload to fail.
+   > Do not copy data from the **Subscription GUID** column into the bulk add template.  Leave that column blank in the Bulk add template.  Including the GUIDs will cause the upload to fail.
 
    > [!TIP]
    > If you have a lot of subscribers, you might find it helpful to use keyboard shortcuts when you're copying and pasting data. 
-   > To select all the entries in a column like Subscriber Name, select the first entry in the column (not the column heading), select and hold **Ctrl+Shift**, and then select the Down arrow key. This will select all the data in that column. 
+   > To select all the entries in a column like "Subscriber Name", select the first entry in the column (not the column heading), select and hold **Ctrl+Shift**, and then select the Down arrow key. This will select all the data in that column. 
 
 
 4. When all your data is moved to the bulk add template, save the template and close it. This list is the subscription list that you'll upload to your new agreement.