Merge branch 'resources' of github.com:ghogen/vsdocs into resources

Author: ghogen

.openpublishing.redirection.mac.json

@@ -55,6 +55,11 @@
       "redirect_url": "/visualstudio/gamedev/unity/get-started/getting-started-with-visual-studio-tools-for-unity",
       "redirect_document_id": false
     },
+    {
+      "source_path_from_root": "/mac/what-happened-to-vs-for-mac.md",
+      "redirect_url": "/visualstudio/releases/2022/what-happened-to-vs-for-mac",
+      "redirect_document_id": false
+    },
     {
       "source_path": "mac/2017/accessibility-keyboard.md",
       "redirect_url": "/previous-versions/visualstudio/mac/accessibility-keyboard",

docs/azure/how-to-sign-in-with-azure-subscription.md

@@ -23,7 +23,7 @@ Visual Studio also gives you the opportunity to [create a new, free Azure accoun
 Visual Studio allows you to sign in with multiple accounts and it let's you work with Azure resources across multiple Azure subscriptions so no need to sign-out of one in order to sign-in with another!
 
 > [!NOTE]
-> When using Azure CLI, be aware that the sign-in from the Azure CLI is separate from the sign-in used in Visual Studio, so even if you're signed in to Azure by using `az login` on the same machine where you're running Visual Studio, you still need to provide credentials within Visual Studio.
+> When using the Azure CLI, be aware that the sign-in from the Azure CLI is separate from the sign-in used in Visual Studio, so even if you're signed in to Azure by using `az login` on the same machine where you're running Visual Studio, you still need to provide credentials within Visual Studio.
 
 ## To sign in to Azure from a dialog or wizard screen
 

docs/azure/includes/vs-2019/create-aspnet5-app-2019.md

@@ -5,16 +5,23 @@ author: ghogen
 ms.subservice: azure-development
 ms.author: ghogen
 ms.topic: include
-ms.date: 03/08/2021
+ms.date: 08/22/2024
 ---
 
 1. In the Visual Studio start window, select **Create a new project**.
+
 1. Select **ASP.NET Core Web App**, and then select **Next**.
+
 1. Enter a name for your new application (or use the default name), specify the location on disk, and then select **Next**.
-1. Choose the .NET version you want to target. If you don't know, [choose the LTS (long-term support) release](https://dotnet.microsoft.com/download/dotnet).
 
-   ![Create a web project - Additional information screen](../../media/create-aspnet5-app/net-core-50-enable-docker-support-visual-studio.png)
+1. Select the .NET version you want to target. If you're not sure, [choose the LTS (long-term support) release](https://dotnet.microsoft.com/download/dotnet).
+
+   :::image type="content" source="../../media/create-aspnet5-app/net-core-50-enable-docker-support-visual-studio.png" border="false" alt-text="Screenshot that shows how to create a new ASP.NET Core web app project in Visual Studio 2019.":::
 
 1. Choose whether you want SSL support by selecting or clearing the **Configure for HTTPS** checkbox.
+
 1. Select the **Enable Docker Support** checkbox.
-1. Select the type of container you want (Windows or Linux), and then select **Create**.
+
+1. Use the dropdown list to select the type of container you want: **Windows** or **Linux**.
+
+1. Select **Create** to complete the process.

docs/azure/includes/vs-2022/create-aspnet5-app-2022.md

@@ -5,16 +5,23 @@ author: ghogen
 ms.subservice: azure-development
 ms.author: ghogen
 ms.topic: include
-ms.date: 10/25/2021
+ms.date: 08/22/2024
 ---
 
 1. In the Visual Studio start window, select **Create a new project**.
+
 1. Select **ASP.NET Core Web App**, and then select **Next**.
+
 1. Enter a name for your new application (or use the default name), specify the location on disk, and then select **Next**.
-1. Choose the .NET version you want to target. If you don't know, [choose the LTS (long-term support) release](https://dotnet.microsoft.com/download/dotnet).
 
-   ![Create a web project - Additional information screen](../../media/create-aspnet5-app/asp-net-enable-docker-support-visual-studio.png)
+1. Select the .NET version you want to target. If you're not sure, [choose the LTS (long-term support) release](https://dotnet.microsoft.com/download/dotnet).
+
+   :::image type="content" source="../../media/create-aspnet5-app/asp-net-enable-docker-support-visual-studio.png" border="false" alt-text="Screenshot that shows how to create a new ASP.NET Core web app project in Visual Studio 2022.":::
 
 1. Choose whether you want SSL support by selecting or clearing the **Configure for HTTPS** checkbox.
+
 1. Select the **Enable Docker** checkbox.
-1. In the **Docker OS** textbox, select the type of container you want (Windows or Linux), and then select **Create**.
+
+1. Use the **Docker OS** dropdown list to select the type of container you want: **Windows** or **Linux**.
+
+1. Select **Create** to complete the process.

docs/azure/media/vs-azure-tools-optimizing-azure-code-in-visual-studio/IC796660.png

@@ -41,7 +41,7 @@ You can configure an Azure cloud service project, depending on your requirements
 
 1. Set **Treat warnings as errors** to **True** to make sure you cannot publish if there are package validation errors.
 
-1. Set **Use web project ports** to **True** to make sure that your web role uses the same port each time it starts locally in IIS Express.
+1. Set **Use web project ports** to **True** to make sure that your web role uses the same port each time it starts locally in Internet Information Services (IIS) Express.
 
 1. From the Visual Studio toolbar, select **Save**.
 

docs/azure/media/vs-azure-tools-publishing-a-cloud-service/IC744134.png

@@ -27,7 +27,7 @@ When you create an Azure project, Emulator Express is automatically used. For ex
 
     ![Properties for an Azure cloud service project](./media/vs-azure-tools-emulator-express-debug-run/web-properties.png)
 
-1. Under **Local Development Server**, select **Use IIS Express option**.
+1. Under **Local Development Server**, select **Use Internet Information Services (IIS) Express option**.
 
 1. Under **Emulator**, select **Use Emulator Express**.
 

docs/azure/vs-azure-tools-configuring-an-azure-project.md

@@ -78,7 +78,7 @@ Affects the project file .NET references and NuGet package references.
 
 ### launchsettings.json changes for ASP.NET Core
 
-- Added the following environment variable entries to both the IIS Express profile and the profile that matches your web project name:
+- Added the following environment variable entries to both the Internet Information Services (IIS) Express profile and the profile that matches your web project name:
 
     ```json
       "environmentVariables": {

docs/azure/vs-azure-tools-emulator-express-debug-run.md

@@ -66,6 +66,53 @@ ENTRYPOINT ["dotnet", "WebApplication43.dll"]
 
 The final stage starts again from `base`, and includes the `COPY --from=publish` to copy the published output to the final image. This process makes it possible for the final image to be a lot smaller, since it doesn't need to include all of the build tools that were in the `sdk` image.
 
+The following table summarize the stages used in the typical Dockerfile created by Visual Studio:
+
+| Stage | Description |
+| - | - |
+| base | Creates the base runtime image where the built app is published. Settings that need to be available at runtime go here, such as ports and environment variables. This stage is used when running from VS in fast mode (Default for Debug configuration). |
+| build | The project is built in this stage. The .NET SDK base image is used, which has the components required to build your project. |
+| publish | This stage derives from the build stage and publishes your project, which will be copied to the final stage. |
+| final | This stage configures how to start the app and is used in production or when running from VS in regular mode (Default when not using the Debug configuration). |
+| aotdebug | This stage is used as the base for the final stage when launching from VS to support debugging in regular mode (Default when not using the Debug configuration). |
+
+> [!NOTE]
+> The `aotdebug` stage is only supported for Linux containers. It is used in Visual Studio 2022 17.11 and later if [native Ahead Of Time (AOT) deployment](/dotnet/core/deploying/native-aot) is enabled on the project.
+
+::: moniker range=">=vs-2022"
+### Customize the image for debugging
+
+To support native AOT deployment, the GNU debugger (GDB) is installed, but only on the image used when debugging, not the final runtime image. The Dockerfile includes a build argument `LAUNCHING_FROM_VS` which can be `true` or `false`. If `true`, the `aotdebug` stage is used, which is where GDB is installed. Note that Visual Studio only supports native AOT and GDB for Linux containers.
+
+```Dockerfile
+# These ARGs allow for swapping out the base used to make the final image when debugging from VS
+ARG LAUNCHING_FROM_VS
+# This sets the base image for final, but only if LAUNCHING_FROM_VS has been defined
+ARG FINAL_BASE_IMAGE=${LAUNCHING_FROM_VS:+aotdebug}
+
+# ... (other stages omitted)
+
+# This stage is used as the base for the final stage when launching from VS to support debugging in regular mode (Default when not using the Debug configuration)
+FROM base as aotdebug
+USER root
+# Install GDB to support native debugging
+RUN apt-get update \
+    && apt-get install -y --no-install-recommends \
+    gdb
+USER app
+
+# This stage is used in production or when running from VS in regular mode (Default when not using the Debug configuration)
+FROM ${FINAL_BASE_IMAGE:-mcr.microsoft.com/dotnet/runtime-deps:8.0} AS final
+WORKDIR /app
+EXPOSE 8080
+COPY --from=publish /app/publish .
+ENTRYPOINT ["./WebApplication1"]
+```
+
+You can use `aotstage` in the Dockerfile to customize the image used at debug time, without affecting the final image used when not launching from Visual Studio, or in production. For example, you could install a tool for use only during debugging.
+
+:::moniker-end
+
 ### MSBuild
 
 ::: moniker range=">=vs-2022"