Merge pull request #10521 from MicrosoftDocs/main638688710298526280sync_temp

For protected branch, push strategy should use PR and merge to target branch method to work around git push error

Author: learn-build-service-prod[bot]

docs/azure/overview-connected-services.md

@@ -5,7 +5,7 @@ author: ghogen
 manager: mijacobs
 ms.subservice: azure-development
 ms.topic: overview
-ms.date: 08/01/2022
+ms.date: 12/3/2024
 ms.author: ghogen
 monikerRange: ">=vs-2019"
 ---

docs/containers/container-tools.md

@@ -3,7 +3,7 @@ title: Visual Studio Container Tools with ASP.NET
 author: ghogen
 description: Use Visual Studio Container Tools and Docker for Windows to build and debug containerized apps and publish to a container registry, Docker Hub, or Azure App Service.
 ms.author: ghogen
-ms.date: 11/16/2023
+ms.date: 12/3/2024
 ms.subservice: container-tools
 ms.topic: quickstart
 ---
@@ -55,14 +55,13 @@ Visual Studio creates a *Dockerfile* in your project, which provides the recipe
 ```dockerfile
 #See https://aka.ms/customizecontainer to learn how to customize your debug container and how Visual Studio uses this Dockerfile to build your images for faster debugging.
 
-#Depending on the operating system of the host machines(s) that will build or run the containers, the image specified in the FROM statement may need to be changed.
-#For more information, please see https://aka.ms/containercompat
-
+# This stage is used when running from VS in fast mode (Default for Debug configuration)
 FROM mcr.microsoft.com/dotnet/aspnet:8.0-nanoserver-1809 AS base
 WORKDIR /app
 EXPOSE 8080
 EXPOSE 8081
 
+# This stage is used to build the service project
 FROM mcr.microsoft.com/dotnet/sdk:8.0-nanoserver-1809 AS build
 ARG BUILD_CONFIGURATION=Release
 WORKDIR /src
@@ -72,10 +71,12 @@ COPY . .
 WORKDIR "/src/MyWebApp"
 RUN dotnet build "./MyWebApp.csproj" -c %BUILD_CONFIGURATION% -o /app/build
 
+# This stage is used to publish the service project to be copied to the final stage
 FROM build AS publish
 ARG BUILD_CONFIGURATION=Release
 RUN dotnet publish "./MyWebApp.csproj" -c %BUILD_CONFIGURATION% -o /app/publish /p:UseAppHost=false
 
+# This stage is used in production or when running from VS in regular mode (Default when not using the Debug configuration)
 FROM base AS final
 WORKDIR /app
 COPY --from=publish /app/publish .
@@ -164,5 +165,6 @@ You can now pull the container from the registry to any host capable of running
 ## Additional resources
 
 - [Container development with Visual Studio](./index.yml)
+- [Create a multi-container app with Docker Compose](tutorial-multicontainer.md)
 - [Troubleshoot Visual Studio development with Docker](troubleshooting-docker-errors.md)
 - [Visual Studio Container Tools GitHub repository](https://github.com/Microsoft/DockerTools)

docs/data-tools/accessing-data-in-visual-studio.md

@@ -1,7 +1,7 @@
 ---
 title: Work with data in Visual Studio
 description: Work with data in Visual Studio and create apps that connect to data in other database products or services over local machines, LANs, and public or private clouds.
-ms.date: 09/14/2023
+ms.date: 12/3/2024
 ms.topic: conceptual
 helpviewer_keywords:
 - data [Visual Studio]
@@ -118,7 +118,7 @@ Most of the other SQL and NoSQL database products that are listed here can be ho
 :::moniker-end
 
 > [!NOTE]
-> Extended support for SQL Server 2005 ended on April 12, 2016. There is no guarantee that data tools in Visual Studio 2015 and later will continue to work with SQL Server 2005. For more information, see the [end of support announcement for SQL Server 2005](https://www.microsoft.com/sql-server/sql-server-2005).
+> Extended support for SQL Server 2005 ended on April 12, 2016. There is no guarantee that data tools in Visual Studio 2015 and later will continue to work with SQL Server 2005.
 
 ## .NET languages
 
@@ -130,13 +130,13 @@ For data-access documentation related to ASP.NET, see [Working with Data](https:
 
 Universal Windows Platform (UWP) apps in C# or Visual Basic can use the Microsoft Azure SDK for .NET to access Azure Storage and other Azure services. The Windows.Web.HttpClient class enables communication with any RESTful service. For more information, see [How to connect to an HTTP server using Windows.Web.Http](/previous-versions/windows/apps/dn469430(v=win.10)).
 
-For data storage on the local machine, the recommended approach is to use SQLite, which runs in the same process as the app. If an object-relational mapping (ORM) layer is required, you can use Entity Framework. For more information, see [Data access](/windows/uwp/data-access/index) in the Windows Developer Center.
+For data storage on the local machine, the recommended approach is to use SQLite, which runs in the same process as the app. If an object-relational mapping (ORM) layer is required, you can use Entity Framework. For more information, see [Data access](/windows/uwp/data-access/index).
 
 If you are connecting to Azure services, be sure to download the latest [Azure SDK tools](https://azure.microsoft.com/downloads/).
 
 ### Data providers
 
-For a database to be consumable in ADO.NET, it must have a custom *ADO.NET data provider* or else must expose an ODBC or OLE DB interface. Microsoft provides a [list of ADO.NET data providers](/dotnet/framework/data/adonet/ado-net-overview) for SQL Server products, as well as ODBC and OLE DB providers.
+For a database to be consumable in ADO.NET, it must have a custom *ADO.NET data provider* or else must expose an ODBC or OLE DB interface. Microsoft provides a [list of ADO.NET data providers](/dotnet/framework/data/adonet/data-providers) for SQL Server products, as well as ODBC and OLE DB providers.
 
 > [!NOTE]
 > If you're using Visual Studio to connect to databases using OLEDB or ODBC data providers, you will need to be aware that versions of Visual Studio prior to Visual Studio 2022 are all 32-bit processes. This means some of the data tools in Visual Studio will only be able to connect to OLEDB or ODBC databases using 32-bit data providers. This includes the Microsoft Access 32-bit OLEDB data provider as well as other third-party 32-bit providers.
@@ -165,15 +165,13 @@ C++ applications that connect to SQL Server should use the [Microsoft® ODBC Dri
 
 C++ programs that consume REST services can use the [C++ REST SDK](https://github.com/Microsoft/cpprestsdk).
 
-C++ programs that work with Microsoft Azure Storage can use the [Microsoft Azure Storage Client](https://www.nuget.org/packages/Microsoft.Azure.Storage.CPP).
-
 Data modeling—Visual Studio does not provide an ORM layer for C++. [ODB](https://www.codesynthesis.com/products/odb/) is a popular open-source ORM for C++.
 
-To learn more about connecting to databases from C++ apps, see [Visual Studio data tools for C++](../data-tools/visual-studio-data-tools-for-cpp.md). For more information about legacy Visual C++ data-access technologies, see [Data Access](/cpp/data/data-access-in-cpp).
+To learn more about connecting to databases from C++ apps, see [Visual Studio data tools for C++](../data-tools/visual-studio-data-tools-for-cpp.md).
 
 ## JavaScript
 
-[JavaScript in Visual Studio](/scripting/javascript/javascript-language-reference) is a first-class language for building cross-platform apps, UWP apps, cloud services, websites, and web apps. You can use Bower, Grunt, Gulp, npm, and NuGet from within Visual Studio to install your favorite JavaScript libraries and database products. Connect to Azure Storage and services by downloading SDKs from the [Azure website](https://azure.microsoft.com/). Edge.js is a library that connects server-side JavaScript (Node.js) to ADO.NET data sources.
+[JavaScript in Visual Studio](../javascript/index.yml) is a first-class language for building cross-platform apps, UWP apps, cloud services, websites, and web apps. You can use Bower, Grunt, Gulp, npm, and NuGet from within Visual Studio to install your favorite JavaScript libraries and database products. Connect to Azure Storage and services by downloading SDKs from the [Azure website](https://azure.microsoft.com/). Edge.js is a library that connects server-side JavaScript (Node.js) to ADO.NET data sources.
 
 ## Python
 
@@ -185,8 +183,6 @@ Install [Python support in Visual Studio](../python/overview-of-python-tools-for
 
 ## Related content
 
-[Microsoft AI platform](https://azure.microsoft.com/overview/ai-platform/?v=17.42w)—Provides an introduction to the Microsoft intelligent cloud, including Cortana Analytics Suite and support for Internet of Things.
-
 [Microsoft Azure Storage](/azure/storage/)—Describes Azure Storage, and how to create applications by using Azure blobs, tables, queues, and files.
 
 [Azure SQL Database](/azure/sql-database/)—Describes how to connect to Azure SQL Database, a relational database as a service.

docs/data-tools/entity-data-model-tools-in-visual-studio.md

@@ -1,7 +1,7 @@
 ---
 title: Overview of Entity Framework Tools
 description: Explore Entity Framework tools in Visual Studio, including the Entity Data Model Designer, Create Database Wizard, and Update Model Wizard.
-ms.date: 11/01/2023
+ms.date: 12/03/2024
 ms.topic: conceptual
 author: ghogen
 ms.author: ghogen
@@ -39,14 +39,11 @@ The tools generate or modify an `.edmx` file. This `.edmx` file contains informa
 
 [Entity Framework 6 Power Tools](https://marketplace.visualstudio.com/items?itemName=EntityFrameworkTeam.EntityFrameworkPowerToolsBeta4) help you build applications that use the Entity Data Model. The power tools can generate a conceptual model, validate an existing model, produce source-code files that contain object classes based on the conceptual model, and produce source-code files that contain views that the model generates. For detailed information, see [Pre-Generated Mapping Views](/ef/ef6/fundamentals/performance/pre-generated-views).
 
-## Related topics
+## Related content
 
 | Title | Description |
 | - | - |
 | [ADO.NET Entity Framework](/dotnet/framework/data/adonet/ef/index) | Describes how to use Entity Data Model Tools, which Entity Framework provides, to create applications. |
 | [Entity Data Model](/dotnet/framework/data/adonet/entity-data-model) | Provides links and information for working with data that is used by applications built on Entity Framework. |
 | [Entity Framework (EF) Documentation)](/ef/ef6/get-started) | Provides an index of videos, tutorials, and advanced documentation to help you make the most of Entity Framework. |
-
-## Related content
-
-- [Visual Studio data tools for .NET](../data-tools/visual-studio-data-tools-for-dotnet.md)
+| [Visual Studio data tools for .NET Framework development](../data-tools/visual-studio-data-tools-for-dotnet.md) | Provides an overview of .NET Framework data tools in Visual Studio. |

docs/data-tools/linq-to-sql-tools-in-visual-studio2.md

@@ -1,7 +1,7 @@
 ---
 title: LINQ to SQL O/R Designer overview
 description: Explore LINQ to SQL tools in Visual Studio for object-relational mapping, including the Object Relational Designer (O/R Designer).
-ms.date: 11/01/2023
+ms.date: 12/03/2024
 ms.topic: overview
 author: ghogen
 ms.author: ghogen
@@ -11,11 +11,11 @@ ms.subservice: data-tools
 
 # LINQ to SQL tools in Visual Studio
 
-LINQ to SQL was the first object-relational mapping technology released by Microsoft. It works well in basic scenarios and continues to be supported in Visual Studio, but it's no longer under active development. Use LINQ to SQL when maintaining a legacy application that's already using it, or in simple applications that use SQL Server and do not require multi-table mapping. In general, new applications should use the Entity Framework when an object-relational mapper layer is required.
+LINQ to SQL was the first object-relational mapping technology released by Microsoft. It works well in basic scenarios and continues to be supported in Visual Studio, but it's no longer under active development. Use LINQ to SQL when maintaining a legacy application that's already using it, or in simple applications that use SQL Server and do not require multi-table mapping. In general, new applications should use the Entity Framework when an object-relational mapping layer is required.
 
 ## Install the LINQ to SQL tools
 
-In Visual Studio, you create LINQ to SQL classes that represent SQL tables by using the **Object Relational Designer** (**O/R Designer**). The O/R designer is the UI for editing .dbml files. Editing .dbml files with a designer surface requires the LINQ to SQL tools which are not installed by default as part of any of the workloads of Visual Studio.
+In Visual Studio, you create LINQ to SQL classes that represent SQL tables by using the **Object Relational Designer** (**O/R Designer**). The O/R designer is the UI for editing `.dbml` files. Editing `.dbml` files with a designer surface requires the LINQ to SQL tools which are not installed by default as part of any of the workloads of Visual Studio.
 
 To install the LINQ to SQL tools, start the Visual Studio installer, choose **Modify**, then select the **Individual Components** tab, and then select **LINQ to SQL tools** under the **Code Tools** category.
 
@@ -29,15 +29,15 @@ The **O/R Designer** provides a visual design surface for creating [LINQ to SQL]
 
 To add a LINQ to SQL entity model to your project, choose **Project** > **Add New Item**, and then select **LINQ to SQL Classes** from the list of project items:
 
-![LINQ to SQL classes](../data-tools/media/raddata-linq-to-sql-classes.png)
+![Screenshot showing LINQ to SQL classes.](../data-tools/media/raddata-linq-to-sql-classes.png)
 
 Visual Studio creates a `.dbml` file and adds it to your solution. This is the XML mapping file and its related code files.
 
-![LINQ to SQL classes in Solution Explorer](../data-tools/media/raddata-linq-to-sql-classes-in-solution-explorer.png)
+![Screenshot showing LINQ to SQL classes in Solution Explorer.](../data-tools/media/raddata-linq-to-sql-classes-in-solution-explorer.png)
 
 When you select the `.dbml` file, Visual Studio shows the **O/R Designer** surface that enables you to visually create the model. The following illustration shows the designer after the Northwind `Customers` and `Orders` tables have been dragged from **Server Explorer**. Note the relationship between the tables.
 
-![LINQ to SQL Designer](../data-tools/media/raddata-linq-to-sql-designer.png)
+![Screenshot showing LINQ to SQL Designer.](../data-tools/media/raddata-linq-to-sql-designer.png)
 
 > [!IMPORTANT]
 > The **O/R Designer** is a simple object relational mapper because it supports only 1:1 mapping relationships. In other words, an entity class can have only a 1:1 mapping relationship with a database table or view. Complex mapping, such as mapping an entity class to a joined table, is not supported; use the Entity Framework for complex mapping. Additionally, the designer is a one-way code generator. This means that only changes that you make to the designer surface are reflected in the code file. Manual changes to the code file are not reflected in the **O/R Designer**. Any changes that you make manually in the code file are overwritten when the designer is saved and code is regenerated. For information about how to add user code and extend the classes generated by the **O/R Designer**, see [How to: Extend code generated by the O/R Designer](../data-tools/how-to-extend-code-generated-by-the-o-r-designer.md).

docs/deployment/tutorial-import-publish-settings-iis.md

@@ -1,7 +1,7 @@
 ---
 title: "Publish to IIS by importing publish settings"
 description: Create and import a publishing profile (.pubxml file) to deploy ASP.NET and ASP.NET Core web applications from Visual Studio to IIS.
-ms.date: 10/17/2023
+ms.date: 12/3/2024
 ms.topic: tutorial
 helpviewer_keywords:
   - "deployment, publish settings"
@@ -26,7 +26,7 @@ These steps apply to ASP.NET and ASP.NET Core web applications.
   * Install the latest updates in Visual Studio by selecting **Help** > **Check for Updates**.
   * Add the workload by selecting **Tools** > **Get Tools and Features**.
 
-* On your server, you must be running Windows Server 2012 or greater, and you must have the [IIS Web Server role](/iis/get-started/whats-new-in-iis-8/iis-80-using-aspnet-35-and-aspnet-45#solution) correctly installed (required to generate the publish settings file (*\*.publishsettings*)). Either ASP.NET 4.5 or ASP.NET Core must also be installed on the server. The steps in this tutorial were tested in Windows Server 2022.
+* On your server, you must be running Windows Server 2012 or greater, and you must have the [IIS Web Server role](/iis/get-started/whats-new-in-iis-8/iis-80-using-aspnet-35-and-aspnet-45#solution) correctly installed (required to generate the publish settings file (`.publishsettings`). Either ASP.NET 4.5 or ASP.NET Core must also be installed on the server. The steps in this tutorial were tested in Windows Server 2022.
 
   * To set up ASP.NET Core, see [Host ASP.NET Core on Windows with IIS](/aspnet/core/publishing/iis?tabs=aspnetcore2x#iis-configuration). For ASP.NET Core, make sure you configure the Application Pool to use **No Managed Code**, as described in the article.
 
@@ -58,4 +58,4 @@ First, check the Output window in Visual Studio for status information, and chec
 - For ASP.NET Core, in IIS you need to make sure that the Application pool field for the **DefaultAppPool** is set to **No Managed Code**.
 - Verify that the version of ASP.NET used in your app is the same as the version you installed on the server. For your app, you can view and set the version in the **Properties** page. To set the app to a different version, that version must be installed.
 - If the app tried to open, but you see a certificate warning, choose to trust the site. If you already closed the warning, you can edit the *.pubxml file in your project and add the following element: `<AllowUntrustedCertificate>true</AllowUntrustedCertificate>`. This setting is for testing only!
-- If the app does not start from Visual Studio, start the app in IIS to test that it deployed correctly.
+- If the app does not start from Visual Studio, start the app in IIS to test that it deployed correctly.

docs/extensibility/signing-vsix-packages.md

@@ -66,7 +66,7 @@ dotnet tool install --global --add-source D:\NuGetTools sign --version 99.0
 ```
 
 ### Using Sign CLI
-Once installed, Sign CLI can be accessed in a Developer PowerShell instance using `sign code <command> <options>`. For a breakdown of the options see [Sign CLI Reference for VSIX Packages](../extensibility/dotnet-sign-CLI-reference-vsix.md).
+Once installed, Sign CLI can be accessed in a Developer PowerShell instance using `sign code <command> <options>`. For a breakdown of the options see [Sign CLI Reference for VSIX Packages](../extensibility/dotnet-sign-CLI-reference-vsix.md). You can get help from command line by typing `sign code -h`.
 
 > [!IMPORTANT]
 > Sign CLI only supports `SHA-256`, `SHA-384`, and `SHA-512` as valid fingerprint algorithms. You can use PowerShell to get fingerprints using: `Get-FileHash -Algorithm SHA256 <path to .cer file> | Format-Table -AutoSize`

docs/ide/how-to-substitute-parameters-in-a-template.md

@@ -1,7 +1,7 @@
 ---
 title: Add name parameters to project and item templates
 description: Modify template parameters in Visual Studio to replace identifiers like class names and namespaces in existing templates or your own templates.
-ms.date: 01/02/2018
+ms.date: 12/03/2024
 ms.topic: how-to
 helpviewer_keywords:
 - template parameters
@@ -22,6 +22,8 @@ The following section shows you how to modify a template to replace the name of
 
 ## Example - namespace name
 
+To follow this procedure, you need an existing template. If you don't have one, see [Create project templates](how-to-create-project-templates.md) to learn how to export a project or solution to a template, or [Create item templates](how-to-create-item-templates.md).
+
 1. Insert the parameter in one or more of the code files in the template. For example:
 
     ```csharp