Merge branch 'main' into patch-1

Author: ghogen

.github/workflows/stale-issues.yml

@@ -7,6 +7,7 @@ name: close-stale-issues
 on:
   schedule:
     - cron: "0 0 * * 4"
+  workflow_dispatch:
 
 permissions:
   contents: read
@@ -18,7 +19,7 @@ jobs:
       pull-requests: write  # for actions/stale to close stale PRs
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/stale@v4.0.0
+      - uses: actions/stale@v6
         with:
           repo-token: ${{ secrets.GITHUB_TOKEN }}
           stale-issue-message: 'Thanks for sharing your feedback. We apologize for our delayed response. Due to the sheer volume of feedback in our repo, we have decided to prioritize the newest issues and are automatically closing our oldest issues with an Issues bot. If you believe your feedback is still actionable, then either respond directly in this issue or open a new documentation issue and we’ll review. If no activity occurs in the next 14 days, this issue will be closed.'

.github/workflows/stale.yml

@@ -13,7 +13,7 @@ jobs:
       pull-requests: write
 
     steps:
-    - uses: actions/stale@v4.0.0
+    - uses: actions/stale@v6
       with:
         repo-token: ${{ secrets.GITHUB_TOKEN }}
         days-before-pr-stale: 14

CONTRIBUTING.md

@@ -1,8 +1,8 @@
 # Contribute to Visual Studio documentation
 
-Thank you for taking the time to contribute to the Visual Studio docs.
+Thank you for taking the time to contribute to the Visual Studio documentation.
 
-This guide covers some general topics around contributing and refers out to the docs.microsoft.com [contributors guide](https://docs.microsoft.com/contribute) for more detailed explanations.
+This guide covers some general topics around contributing and refers to the [Microsoft Docs contributor guide](https://learn.microsoft.com/contribute) for more detailed explanations.
 
 ## Code of conduct
 
@@ -20,11 +20,11 @@ Please use the feedback tool at the bottom of any article to submit bugs and sug
 
 ### Quick edit in GitHub
 
-Follow the guidance for [quick edits to existing documents](https://docs.microsoft.com/contribute/#quick-edits-to-existing-documents) in the contributors guide.
+Follow the guidance for [quick edits to existing documents](https://learn.microsoft.com/contribute/#quick-edits-to-existing-documents) in the contributors guide.
 
 ### Larger edits
 
-Review the guidance for [pull requests](https://docs.microsoft.com/contribute/how-to-write-workflows-major#pull-request-processing) in the contributors guide.
+Review the guidance for [pull requests](https://learn.microsoft.com/contribute/how-to-write-workflows-major#pull-request-processing) in the contributors guide.
 
 **NOTE**
 

README.md

@@ -1,6 +1,6 @@
 # Visual Studio documentation
 
-Welcome! This repo contains source files for the Visual Studio technical documentation. The topics are published on [docs.microsoft.com](https://docs.microsoft.com/visualstudio).
+Welcome! This repo contains source files for the Visual Studio technical documentation. The topics are published at [Visual Studio product family documentation](https://learn.microsoft.com/visualstudio).
 
 This repo was moved on June 23, 2017 from https://github.com/Microsoft/vsdocs.
 

bridge/articles/bridge-to-kubernetes-sample.md

@@ -44,7 +44,7 @@ minikube start --vm-driver hyperv --hyperv-virtual-switch "Primary Virtual Switc
 
 ## Deploy the application
 
-Clone the [mindaro repo](https://github.com/Microsoft/mindaro) and open a command window with the current working folder to *samples/todo-app*.
+Clone the [Bridge to Kubernetes repo](https://github.com/Azure/Bridge-To-Kubernetes) and open a command window with the current working folder to *samples/todo-app*.
 
 Create a namespace for the sample.
 

bridge/articles/bridge-to-kubernetes-vs.md

@@ -30,9 +30,9 @@ In this tutorial, you learn how to:
 
 - A Kubernetes cluster. You can create one in the [Azure portal](https://azure.microsoft.com/free/).  If you don't have an Azure subscription, you can [create an account for free](https://azure.microsoft.com/free/).
 - The [kubectl](https://kubernetes.io/docs/reference/kubectl/kubectl/) executable installed on your system.
-- [Visual Studio 2019](https://www.visualstudio.com/vs/) version 16.7 or later running on Windows 10 or later.
-- The Bridge to Kubernetes extension for [Visual Studio 2019](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.mindaro) or [Visual Studio 2022](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.mindaro2022).
-- An application to troubleshoot, such as this [TODO App sample application](https://github.com/Microsoft/mindaro).
+- [Visual Studio 2019](https://www.visualstudio.com/vs/) version 16.7 or later running on Windows 10 or later or [Visual Studio 2022](https://www.visualstudio.com/vs/).
+- The [Bridge to Kubernetes extension for Visual Studio 2019](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.mindaro) or [Bridge to Kubernetes extension for Visual Studio 2022](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.mindaro2022).
+- An application to troubleshoot, such as this [TODO App sample application](https://github.com/Azure/Bridge-To-Kubernetes/tree/main/samples/todo-app).
 
 ## Set up a service
 
@@ -51,7 +51,7 @@ The sample application has a frontend to interact and a backend that provides pe
 1. Clone the sample repo.
 
    ```bash
-   git clone https://github.com/Microsoft/mindaro
+   git clone https://github.com/Azure/Bridge-To-Kubernetes
    ```
 
 1. Change directory to *samples/todo-app* and then create a namespace for the sample.
@@ -163,6 +163,16 @@ In this section, you set a breakpoint in your service.
 
 1. To remove the breakpoint, select that line and then select **Debug** > **Toggle Breakpoint** or select **F9**.
 
+## Edit launch profile
+
+If you need to change how Bridge to Kubernetes connects to your cluster, in this section, you'll edit the launch profile settings.
+
+1. Click on the arrow next to the **Bridge to Kubernetes** button, then click on **databaseApi Debug Properties**.
+ ![Screenshot shows the Bridge to Kubernetes drop down menu.](media/bridge-to-kubernetes-vs/change-bridge-properties.png)
+
+1. Click on the **Edit profile for Bridge to Kubernetes** link in the **Launch Profiles** dialog.
+ ![Screenshot shows Launch Profiles dialog with a link to edit the Bridge to Kubernetes profile](media/bridge-to-kubernetes-vs/bridge-launch-profiles.png)
+
 ## Clean up resources
 
 If you used the sample todo app for this tutorial, you can remove it from your cluster by using the Azure portal.

bridge/articles/media/bridge-to-kubernetes-vs/bridge-launch-profiles.png

@@ -8,7 +8,6 @@ ms.workload: azure-vs
 ms.topic: conceptual
 ms.date: 08/17/2020
 ms.author: angelpe
-monikerRange: ">= vs-2019"
 ---
 # Add Azure Application Insights by using Visual Studio Connected Services
 

bridge/articles/media/bridge-to-kubernetes-vs/change-bridge-properties.png

@@ -6,7 +6,7 @@ manager: jmartens
 ms.technology: vs-azure
 ms.workload: azure-vs
 ms.topic: conceptual
-ms.date: 08/17/2020
+ms.date: 09/16/2022
 ms.author: angelpe
 monikerRange: ">= vs-2019"
 ---
@@ -83,6 +83,51 @@ The connected service functionality adds all the needed references and connectio
 
    ![Service dependencies](./media/azure-sql-database-add-connected-service/service-dependencies-after.png)
 
+## Entity Framework migrations
+
+It might be convenient to work with a local data store during early development, but with Entity Framework Core, when you're ready to move to the cloud, you can use Visual Studio's support for Entity Framework migration to move your database, or merge changes with a remote data store. See [Migrations overview](/ef/core/managing-schemas/migrations/?tabs=vs).
+
+On the **Connected Services** tab, you can find the migration commands by clicking on the three dots, as shown in the screenshot:
+
+![Screenshot showing migration commands.](./media/vs-2022/add-migration-light-theme.png)
+
+Commands are available there to create new migrations, apply them directly, or generate SQL scripts that apply the migrations.
+
+:::moniker range=">=vs-2022"
+
+### Add migration
+
+When a data model change is introduced, you can use Entity Framework Core tools to add a corresponding migration that describes in code the updates necessary to keep the database schema in sync. Entity Framework Core compares the current model against a snapshot of the old model to determine the differences, and generates migration source files. The files are added to your project, usually in a folder called *Migrations* and can be tracked in your project's source control like any other source file.
+
+When you choose this option, you're asked to provide the context class name that represents the database schema you want to migrate.
+
+![Screenshot showing adding an Entity Framework migration.](./media/vs-2022/entity-framework-migration-context.png)
+
+### Update database
+
+After a migration has been created, it can be applied to a database. Entity Framework updates your database and your schema with the changes specified in the migration code. When you choose this option, you're asked to provide the context class name that represents the database schema you want to migrate.
+
+### Generate SQL script
+
+The recommended way to deploy migrations to a production database is by generating SQL scripts. The advantages of this strategy include the following:
+
+- SQL scripts can be reviewed for accuracy; this is important since applying schema changes to production databases is a potentially dangerous operation that could involve data loss.
+- In some cases, the scripts can be tuned to fit the specific needs of a production database.
+- SQL scripts can be used in conjunction with a deployment technology, and can even be generated as part of your CI process.
+- SQL scripts can be provided to a DBA, and can be managed and archived separately.
+
+When you use this option, you're asked the database context class and the location for the script file.
+
+![Screenshot showing the Generate SQL script option.](./media/vs-2022/entity-framework-generate-sql-script.png)
+
+### Open in SQL Server Object Explorer
+
+For convenience, this command lets you jump to the SQL Server Object Explorer, so you can view tables and other database entities, and work directly with your data. See [Object explorer](/sql/ssms/object/object-explorer).
+
+![Screenshot showing SQL Server Object Explorer.](./media/vs-2022/sql-server-object-explorer-2.png)
+
+:::moniker-end
+
 ## See also
 
 - [Azure SQL Database product page](https://azure.microsoft.com/services/sql-database/)

docs/azure/azure-app-insights-add-connected-service.md

@@ -1,10 +1,10 @@
 ### YamlMime:Landing
 
-title: Analyze code in Visual Studio
+title: Code analysis documentation - Visual Studio (Windows)
 summary: Visual Studio provides several different tools to analyze and improve code quality.
 
 metadata:
-  title: Code analyzers
+  title: Code analysis documentation - Visual Studio (Windows)
   description: Learn how Visual Studio can help you analyze code quality.
   ms.prod: visual-studio-windows
   ms.technology: vs-ide-code-analysis

docs/azure/azure-sql-database-add-connected-service.md

@@ -13,7 +13,7 @@ With Visual Studio, you can easily build, debug, and run containerized ASP.NET C
 ## Prerequisites
 
 * [Docker Desktop](https://hub.docker.com/editions/community/docker-ce-desktop-windows)
-* [Visual Studio 2017](https://visualstudio.microsoft.com/vs/older-downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=vs+2017+download) with the **Web Development**, **Azure Tools** workload, and/or **.NET Core cross-platform development** workload installed
+* [Visual Studio 2017](https://visualstudio.microsoft.com/vs/older-downloads/?utm_medium=microsoft&utm_source=learn.microsoft.com&utm_campaign=vs+2017+download) with the **Web Development**, **Azure Tools** workload, and/or **.NET Core cross-platform development** workload installed
 * To publish to Azure Container Registry, an Azure subscription. [Sign up for a free trial](https://azure.microsoft.com/free/dotnet/).
 
 ## Installation and setup

docs/azure/media/vs-2022/add-migration-light-theme.png

@@ -4,7 +4,7 @@ description: Get to know the tools available in Visual Studio for working with D
 author: ghogen
 ms.author: ghogen
 ms.topic: overview
-ms.date: 10/27/2021
+ms.date: 10/07/2022
 ms.technology: vs-container-tools
 ---
 # Visual Studio Container Tools for Docker
@@ -31,7 +31,7 @@ The support for Docker in Visual Studio has changed over a number of releases in
 With Visual Studio 2019, you can use Docker Compose, Kubernetes, and Service Fabric as container orchestration services.
 
 > [!NOTE]
-> When creating a .NET Framework or .NET Core console project, there is no option to **Add Docker support**. After a .NET Core console application project is created, the **Add Docker support** option is available. .Net Framework console application projects do not support the **Add Docker support** option after the project is created. After creation both .NET Framework or .NET Core console projects support the **Add Container Orchestrator Support** option using Service Fabric or Docker Compose.
+> When creating a .NET Framework or .NET Core console project, there is no option to **Add Docker support**. After a .NET Core console application project is created, the **Add Docker support** option is available. .NET Framework console application projects do not support the **Add Docker support** option after the project is created. After creation both .NET Framework or .NET Core console projects support the **Add Container Orchestrator Support** option using Service Fabric or Docker Compose.
 
 In Visual Studio 2019 version 16.4 and later, the **Containers** window is available, which lets you view running containers, browse available images, view environment variables, logs, and port mappings, inspect the filesystem, attach a debugger, or open a terminal window inside the container environment. See [Use the Containers window](view-and-diagnose-containers.md).
 

docs/azure/media/vs-2022/add-migration.png

@@ -9,7 +9,7 @@ ms.assetid: 346f70b9-7b52-4688-a8e8-8f53869618d3
 ms.devlang: dotnet
 ms.topic: troubleshooting
 ms.workload: multiple
-ms.date: 11/12/2021
+ms.date: 10/12/2022
 ms.author: ghogen
 ---
 # Troubleshoot Visual Studio development with Docker
@@ -28,7 +28,7 @@ File sharing only needs to be managed if you are using Hyper-V with Docker. If y
     ![Shared drives](media/troubleshooting-docker-errors/docker-settings-image.png)
 
 > [!TIP]
-> Visual Studio versions later than Visual Studio 2017 version 15.6 will prompt when **Shared Drives** aren't configured.
+> Visual Studio prompts you when **Shared Drives** aren't configured.
 
 ## Unable to start debugging
 
@@ -89,18 +89,12 @@ Click **Apply & Restart**. These steps modify the configuration file at *%Progra
 
 ## Container type mismatch
 
-When adding Docker support to a project, you choose either a Windows or a Linux container. If the Docker Server host is not configured to run the same container type as the project target, you will likely see an error similar to the one below:
+When adding Docker support to a project, you choose either a Windows or a Linux container. If the Docker Server host is not configured to run the same container type as the project target, you see an error similar to:
 
   ![Screenshot of Docker Host and Project Mismatch](media/troubleshooting-docker-errors/docker-host-config-change-linux-to-windows.png)
 
-To resolve this issue:
+To resolve this issue, right-click the Docker for Windows icon in the System Tray and choose **Switch to Windows containers...** or **Switch to Linux containers...**.
 
-- Right-click the Docker for Windows icon in the System Tray and choose **Switch to Windows containers...** or **Switch to Linux containers...**.
+## Other issues
 
-## Microsoft/DockerTools GitHub repo
-
-For any other issues you encounter, see  [Microsoft/DockerTools](https://github.com/microsoft/dockertools/issues) issues.
-
-## See also
-
-- [Visual Studio troubleshooting](/troubleshoot/visualstudio/welcome-visual-studio/)
+For any other issues, see the [Microsoft/DockerTools](https://github.com/microsoft/dockertools/issues) repo.