Repo sync for protected branch

.openpublishing.redirection.json

@@ -990,6 +990,11 @@
       "redirect_url": "/visualstudio/ide/how-to-configure-projects-to-target-platforms",
       "redirect_document_id": false
     },
+    {
+      "source_path": "docs/debugger/error-mixed-mode-debugging-for-ia64-processes-is-unsupported.md",
+      "redirect_url": "/visualstudio/debugger/mixed-mode-debugging-for-ia64-processes-is-unsupported",
+      "redirect_document_id": false
+    },
     {
       "source_path": "docs/debugger/how-to-use-edit-and-continue-csharp.md",
       "redirect_url": "/visualstudio/debugger/edit-and-continue-visual-csharp",

docs/azure/overview.md

@@ -89,6 +89,8 @@ Data providers are making services available via standard protocols, such as ODa
 
 ASP.NET Core provides a comprehensive solution for simple web sites and complex web applications. Azure services can help address many of the needs and solve many of the challenges that arise in web site and web application development. ASP.NET Core web applications frequently use client-side JavaScript.
 
+:::image type="content" source="./media/overview-azure-integration/scalable-ecommerce-web-app.png" alt-text="Diagram of web application example architecture." lightbox="./media/overview-azure-integration/scalable-ecommerce-web-app-high-res.png" :::
+
 ### Connect to Azure Cache for Redis
 
 Azure Cache for Redis provides an in-memory data store for Azure services, web sites, and web applications. You can use Azure Cache for Redis as a distributed data or content cache, a session store, a message broker, and more. Supported scenarios include:

docs/debugger/index.yml

@@ -82,6 +82,27 @@ landingContent:
           - text: Set a watch on variables
             url: watch-and-quickwatch-windows.md
 
+  - title: Measure performance
+    linkLists:
+      - linkListType: tutorial
+        links:
+          - text: Get started analyzing CPU usage
+            url: ../profiling/beginners-guide-to-performance-profiling.md
+          - text: Get started measuring memory usage
+            url: ../profiling/memory-usage.md
+      - linkListType: overview
+        links:
+          - text: First look at profiling tools
+            url: ../profiling/profiling-feature-tour.md
+          - text: Which tool should I use?
+            url: ../profiling/choose-performance-tool.md
+          - text: Ways to run profiling tools
+            url: ../profiling/running-profiling-tools-with-or-without-the-debugger.md
+      - linkListType: concept
+        links:
+         - text: Understanding performance collection methods
+           url: ../profiling/understanding-performance-collection-methods-perf-profiler.md
+
   # Card
   - title: Collaborate
     linkLists:

docs/debugger/toc.yml

@@ -311,7 +311,7 @@
       - name: Mixed mode debugging is supported only when using Microsoft .NET Framework 2.0 or greater
         href: error-mixed-mode-debugging-is-supported-only-when-using-microsoft-dotnet-framework-2-0-or-greater.md
       - name: Mixed mode debugging for IA64 processes is unsupported
-        href: error-mixed-mode-debugging-for-ia64-processes-is-unsupported.md
+        href: mixed-mode-debugging-for-ia64-processes-is-unsupported.md
       - name: Mixed-mode debugging for x64 processes is supported only when using Microsoft .NET Framework 4 or greater
         href: error-mixed-mode-debugging-for-x64-processes-is-supported-only-when-using-microsoft-dotnet-framework-4-or-greater.md
       - name: Remote machine does not appear in a Remote Connections dialog
@@ -704,7 +704,7 @@
         href: source-server-security-alert.md
       - name: Mixed mode debugging for x64 processes is only supported when using Microsoft.NET Framework 4 or greater
         href: mixed-mode-debugging-for-x64-processes-is-only-supported-when-using-microsoft-dotnet-framework-4-or-greater.md
-      - name: Mixed mode debugging for IA64 processes is unsupported.
+      - name: Mixed mode debugging for IA64 processes is unsupported
         href: mixed-mode-debugging-for-ia64-processes-is-unsupported.md
       - name: Mixed Mode Debugging Is Only Supported when Using Microsoft .NET Framework 2.0 or 3.0
         href: mixed-mode-debugging-is-only-supported-when-using-microsoft-dotnet-framework-2-0-or-3-0.md

docs/deployment/index.yml

@@ -95,6 +95,21 @@ landingContent:
             url: ../azure/azure-deployment-using-github-actions.md
           - text: Deploy Entity Framework Core app with GitHub Actions
             url: ../azure/end-to-end-deployment-entity-framework-core-github-actions.md
+
+  # Card
+  - title: Deploy Docker containers
+    linkLists:
+      - linkListType: how-to-guide
+        links:
+          - text: Deploy to Azure Container Registry
+            url: ../containers/hosting-web-apps-in-docker.md
+          - text: Deploy to Azure App Service
+            url: ../containers/deploy-app-service.md
+          - text: Deploy to Docker Hub
+            url: ../containers/deploy-docker-hub.md
+          - text: Deploy without a Dockerfile
+            url: ../containers/deploy-containerized.md
+
   # Card
   - title: Additional deployment types
     linkLists:

docs/ide/index.yml

@@ -56,7 +56,7 @@ landingContent:
           - text: Publish a web site
             url: ../deployment/quickstart-deploy-to-a-web-site.md
           - text: Access data
-            url: ../data-tools/create-a-simple-data-application-by-using-adonet.md
+            url: ../data-tools/accessing-data-in-visual-studio.md
           - text: Personalize the IDE
             url: ../ide/quickstart-personalize-the-ide.md
           - text: Productivity features

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: 04/25/2023
+ms.date: 10/16/2023
 ms.topic: tutorial
 ms.devlang: javascript
 author: mikejo5000
@@ -18,7 +18,7 @@ monikerRange: '>= vs-2022'
 
 In this article, you learn how to build an ASP.NET Core project to act as an API backend and an Angular project to act as the UI.
 
-Currently, Visual Studio includes ASP.NET Core Single Page Application (SPA) templates that support Angular and React. The templates provide a built-in Client App folder in your ASP.NET Core projects that contains the base files and folders of each framework.
+Visual Studio includes ASP.NET Core Single Page Application (SPA) templates that support Angular and React. The templates provide a built-in Client App folder in your ASP.NET Core projects that contains the base files and folders of each framework.
 
 You can use the method described in this article to create ASP.NET Core Single Page Applications that:
 
@@ -43,13 +43,13 @@ Make sure to install the following:
 
 1. Search for Angular in the search bar at the top and then select **Angular and ASP.NET Core (Preview)**.
 
-   :::image type="content" source="media/vs-2022/angular-choose-template.png" alt-text="Screenshot showing choosing a template":::
+   :::image type="content" source="media/vs-2022/angular-choose-template.png" alt-text="Screenshot showing choosing a template.":::
 
-1. Give your project and solution a name, and choose **Create**.
+1. Name the project **AngularWithASP** and then choose **Create**.
 
-   Once the project is created, Solution Explorer should look like this:
+   Solution Explorer shows the following::
 
-   :::image type="content" source="media/vs-2022/asp-net-core-with-angular-solution-explorer.png" alt-text="Screenshot showing Solution Explorer":::
+   :::image type="content" source="media/vs-2022/asp-net-core-with-angular-solution-explorer.png" alt-text="Screenshot showing Solution Explorer.":::
 
    Compared to the [standalone Angular template](../javascript/tutorial-create-angular-app.md), you see some new and modified files for integration with ASP.NET Core:
 
@@ -62,30 +62,30 @@ Make sure to install the following:
 
 ## Set the project properties
 
-1. In Solution Explorer, right-click the ASP.NET Core project and choose **Properties**.
+1. In Solution Explorer, right-click the **AngularWithASP.Server** project and choose **Properties**.
 
-   :::image type="content" source="media/vs-2022/asp-net-core-project-properties.png" alt-text="Screenshot showing Open project properties"::: 
+   :::image type="content" source="media/vs-2022/asp-net-core-project-properties-angular.png" alt-text="Screenshot showing Open project properties."::: 
 
-1. In the Properties page, open the **Debug** tab and select **Open debug launch profiles UI** option. Uncheck the **Launch Browser** option.
+1. In the Properties page, open the **Debug** tab and select **Open debug launch profiles UI** option. Uncheck the **Launch Browser** option for the profile named after the ASP.NET Core project (or https, if present).
 
-   :::image type="content" source="media/vs-2022/asp-net-core-deselect-launch-browser.png" alt-text="Screenshot showing Debug launch profiles UI"::: 
+   :::image type="content" source="media/vs-2022/asp-net-core-deselect-launch-browser-angular.png" alt-text="Screenshot showing Debug launch profiles UI."::: 
 
-   This prevents opening the web page with the source weather data.
+   This value prevents opening the web page with the source weather data.
 
    >[!NOTE]
-   > In Visual Studio, *launch.json* stores the startup settings associated with the **Start** button in the Debug toolbar. Currently, *launch.json* must be located under the *.vscode* folder.
+   > In Visual Studio, *launch.json* stores the startup settings associated with the **Start** button in the Debug toolbar. *launch.json* must be located under the *.vscode* folder.
 
 ## Start the project
 
-To start the project, press **F5** or select the **Start** button at the top of the window. You see two command prompts appear:
+Press **F5** or select the **Start** button at the top of the window to start the app. Two command prompts appear:
 
 - The ASP.NET Core API project running
 - The Angular CLI running the ng start command
 
 >[!NOTE]
-> Check console output for messages, such as a message instructing you to update your version of Node.js.
+> Check console output for messages. For example there might be a message to update Node.js.
 
-You see an Angular app appear, populated using the API. If you don't see the app, see [Troubleshooting](#troubleshooting).
+The Angular app appears and is populated via the API. If you don't see the app, see [Troubleshooting](#troubleshooting).
 
 ## Publish the project
 
@@ -94,25 +94,29 @@ Starting in Visual Studio 2022 version 17.3, you can publish the integrated solu
 >[!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. In Solution Explorer, right-click the **AngularWithASP.Server** project and select **Add** > **Project Reference**.
 
-1. Select the Angular project and choose **OK**.
+   The **angularwithasp.client*** project is selected.
 
-1. Right-click the ASP.NET Core project in Solution Explorer and choose **Unload Project**.
+1. Choose **OK**.
+
+1. Right-click the ASP.NET Core project again and select **Edit Project File**.
 
    This opens the *.csproj* file for the project.
 
+   Notice the `<ReferenceOutputAssembly>` has the value set to `false`.
+
 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).
+   When you've updated the reference, it should look like the following.
 
    ```xml
-   <ProjectReference Include="..\angularprojectfolder\angularprojectname.esproj">
-       <ReferenceOutputAssembly>false</ReferenceOutputAssembly>
-   </ProjectReference>
+    <ProjectReference Include="..\angularwithasp.client\angularwithasp.client.esproj">
+      <ReferenceOutputAssembly>false</ReferenceOutputAssembly>
+    </ProjectReference>
    ```
 
-1. Right.click the ASP.NET Core project and choose **Reload Project**.
+1. Right-click the ASP.NET Core project and choose **Reload Project**.
 
 1. In *Program.cs*, update the check for `Environment.IsDevelopment` so it looks like the following.
 
@@ -130,7 +134,7 @@ Starting in Visual Studio 2022 version 17.3, you can publish the integrated solu
    }
    ```
 
-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.
+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, etc.
 
    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.
 
@@ -150,7 +154,7 @@ If you see this issue, most likely the frontend started before the backend. Once
 
 ### Verify port
 
-If the weather data does not load correctly, you may also need to verify that your ports are correct.
+If the weather data doesn't load correctly, you may also need to verify that your ports are correct.
 
 1. Go to the *launchSettings.json* file in your ASP.NET Core project (in the *Properties* folder). Get the port number from the `applicationUrl` property.
 
@@ -164,4 +168,4 @@ If the weather data does not load correctly, you may also need to verify that yo
 
 ## Next steps
 
-For more information about SPA applications in ASP.NET Core, see the Angular section under [Developing Single Page Apps](/aspnet/core/client-side/spa/intro#developing-single-page-apps). The linked article provides additional context for project files such as *aspnetcore-https.js* and *proxy.conf.js*, although details of the implementation are different due to project template differences. For example, instead of a ClientApp folder, the Angular files are contained in a separate project.
+For more information about SPA applications in ASP.NET Core, see the Angular section under [Developing Single Page Apps](/aspnet/core/client-side/spa/intro#developing-single-page-apps). The linked article provides additional context for project files such as *aspnetcore-https.js* and *proxy.conf.js*, although details of the implementation are different due to project template differences. For example, instead of a ClientApp folder, the Angular files are contained in a separate project.