Merge pull request #8353 from MicrosoftDocs/main637958558782649868sync_temp

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

Author: ghogen

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

@@ -6,7 +6,7 @@ manager: jmartens
 ms.technology: bridge
 ms.custom: "contperf-fy22q1"
 title: Use Bridge to Kubernetes to run and debug locally with Kubernetes with AKS in Azure
-ms.date: 11/12/2020
+ms.date: 08/11/2022
 description: Learn how to use Bridge to Kubernetes to connect your development computer to an AKS Kubernetes cluster
 ---
 

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

@@ -6,7 +6,7 @@ manager: jmartens
 ms.technology: bridge
 ms.custom: "contperf-fy22q1"
 title: Learn how to use Bridge to Kubernetes to run and debug locally with Kubernetes, using a TODO sample app.
-ms.date: 10/20/2020
+ms.date: 08/11/2022
 description: Use a todo sample app to learn how to use Bridge to Kubernetes to develop, debug, and test a Kubernetes application locally in Visual Studio Code
 ---
 # Use Bridge to Kubernetes with a sample

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

@@ -6,7 +6,7 @@ manager: jmartens
 ms.technology: bridge
 ms.custom: "contperf-fy22q1"
 title: Use Bridge to Kubernetes to run and debug locally with Kubernetes (VS Code)
-ms.date: 04/14/2021
+ms.date: 08/11/2022
 description: Learn how to use Bridge to Kubernetes to connect your development computer to a Kubernetes cluster and use local tunnel debugging to debug Kubernetes services on your local machine.
 ---
 

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

@@ -8,7 +8,7 @@ manager: jmartens
 ms.technology: bridge
 ms.custom: "contperf-fy22q1"
 ms.topic: tutorial 
-ms.date: 02/22/2022
+ms.date: 08/11/2022
 ---
 
 # Tutorial: Run and debug locally with Bridge to Kubernetes on Visual Studio

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

@@ -1,6 +1,6 @@
 ---
 title: "Configure Bridge to Kubernetes"
-ms.date: 07/28/2020
+ms.date: 08/11/2022
 ms.topic: "conceptual"
 description: "Describes the additional configuration options for Bridge to Kubernetes using KubernetesLocalProcessConfig.yaml"
 keywords: "Bridge to Kubernetes, Azure Dev Spaces, Dev Spaces, Docker, Kubernetes, Azure, containers"

bridge/articles/index.yml

@@ -6,7 +6,7 @@ metadata:
   author: ghogen
   manager: jmartens
   ms.topic: landing-page
-  ms.date: 01/25/2022
+  ms.date: 08/11/2022
   ms.author: ghogen
   ms.technology: bridge
   ms.custom: "contperf-fy22q1"

bridge/articles/kubernetes-environment-variables.md

@@ -1,6 +1,6 @@
 ---
 title: Use Kubernetes service environment variables for service to service communication
-ms.date: 02/12/2021
+ms.date: 08/11/2022
 description: Learn how to use Kubernetes service environment variables with Bridge to Kubernetes to enable service-to-service communication as a non-elevated user in a Kubernetes cluster
 ms.author: ghogen
 author: ghogen

bridge/articles/managed-identity.md

@@ -2,7 +2,7 @@
 title: "How to use managed identity with Bridge to Kubernetes"
 ms.technology: bridge
 ms.custom: "contperf-fy22q1"
-ms.date: 04/28/2021
+ms.date: 08/11/2022
 ms.topic: "conceptual"
 description: "Learn how to use Azure Active Directory (Azure AD) managed identity in an AKS cluster with Bridge to Kubernetes"
 manager: jmartens

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

@@ -2,7 +2,7 @@
 title: What is Bridge to Kubernetes?
 ms.technology: bridge
 ms.custom: "contperf-fy22q1"
-ms.date: 01/19/2022
+ms.date: 08/11/2022
 ms.topic: overview
 description: "Describes the processes for using Bridge to Kubernetes to connect your development computer to your Kubernetes cluster"
 keywords: "Bridge to Kubernetes, Docker, Kubernetes, Azure, containers"

bridge/articles/parallel-services.md

@@ -1,6 +1,6 @@
 ---
 title: Debug multiple services at the same time with Bridge to Kubernetes
-ms.date: 6/2/2021
+ms.date: 08/11/2022
 description: Learn how to use Bridge to Kubernetes to connect your development computer to a Kubernetes cluster and debug multiple services at the same time with local tunnel debugging, with Visual Studio Code.
 author: ghogen
 ms.author: ghogen

docs/ide/managing-references-in-a-project.md

@@ -2,7 +2,7 @@
 title: Manage references in a project
 description: Learn how to manage references to external components and connected services in a project.
 ms.custom: SEO-VS-2020
-ms.date: 10/26/2021
+ms.date: 08/11/2022
 ms.topic: conceptual
 f1_keywords:
 - vs.ProjectPropertiesReferencePaths
@@ -31,9 +31,9 @@ ms.workload:
 
 Before you write code against an external component or connected service, your project must first contain a reference to it. A reference is essentially an entry in a project file that contains the information that Visual Studio needs to locate the component or the service.
 
-To add a reference, right click on the **References** or **Dependencies** node in **Solution Explorer** and choose **Add Reference**. You can also right-click on the project node and select **Add** > **Reference**. For more information, see [How to: Add or remove references](../ide/how-to-add-or-remove-references-by-using-the-reference-manager.md).
+To add a reference, right-click on the **References** or **Dependencies** node in **Solution Explorer** and choose **Add Project Reference**. You can also right-click on the project node and select **Add** > **Project Reference**. For more information, see [How to: Add or remove references](../ide/how-to-add-or-remove-references-by-using-the-reference-manager.md).
 
-![Add a reference in Visual C++](../ide/media/vs2015_cpp_add_reference.png)
+:::image type="content" source="media/add-project-reference.png" alt-text="Screenshot of the Add Project Reference option from the right-click context menu.":::
 
 You can add a reference to the following types of components and services:
 
@@ -53,15 +53,15 @@ You can add a reference to the following types of components and services:
 
 ### Project references
 
-Universal Windows Platform (UWP) projects can create references to other UWP projects in the solution, or to Windows 8.1 projects or binaries, provided that these projects do not use APIs that have been deprecated in Windows 10 and later. For more information, see [Move from Windows Runtime 8 to UWP](/windows/uwp/porting/w8x-to-uwp-root).
+Universal Windows Platform (UWP) projects can create references to other UWP projects in the solution, or to Windows 8.1 projects or binaries, provided that these projects don't use APIs that have been deprecated in Windows 10 and later. For more information, see [Move from Windows Runtime 8 to UWP](/windows/uwp/porting/w8x-to-uwp-root).
 
 If you choose to retarget Windows 8.1 projects to Windows 10 and later, see [Port, migrate, and upgrade Visual Studio projects](../porting/port-migrate-and-upgrade-visual-studio-projects.md).
 
 ### Extension SDK references
 
-Visual Basic, C#, C++ and JavaScript Universal Windows Platform (UWP) apps can reference Extension SDKs that target Windows 8.1, as long as these Extension SDKs do not use APIs that have been deprecated in Windows 10 and later. Please check the Extension SDK vendor site to find out whether it can be referenced by UWP apps.
+Visual Basic, C#, C++ and JavaScript Universal Windows Platform (UWP) apps can reference Extension SDKs that target Windows 8.1, as long as these Extension SDKs don't use APIs that have been deprecated in Windows 10 and later. Check the Extension SDK vendor site to find out whether it can be referenced by UWP apps.
 
-If you determine that the Extension SDK being referenced by your app is not supported, then you need to perform the following steps:
+If you determine that the Extension SDK being referenced by your app isn't supported, then you need to perform the following steps:
 
 1. Look at the name of the project that is causing the error. The platform your project is targeting is noted in parentheses next to the project name. For example, **MyProjectName (Windows 8.1)** means that your project **MyProjectName** is targeting platform version Windows 8.1.
 
@@ -96,30 +96,30 @@ When you make a reference to an assembly in your project, Visual Studio searches
 
 ## References to shared components at run time
 
-At run time, components must be either in the output path of the project or in the Global Assembly Cache (GAC). If the project contains a reference to an object that is not in one of these locations, you must copy the reference to the output path of the project when you build the project. The <xref:Microsoft.VisualStudio.VCProjectEngine.VCProjectReference.CopyLocal%2A> property indicates whether this copy has to be made. If the value is **True**, the reference is copied to the project directory when you build the project. If the value is **False**, the reference is not copied.
+At run time, components must be either in the output path of the project or in the Global Assembly Cache (GAC). If the project contains a reference to an object that isn't in one of these locations, you must copy the reference to the output path of the project when you build the project. The <xref:Microsoft.VisualStudio.VCProjectEngine.VCProjectReference.CopyLocal%2A> property indicates whether this copy has to be made. If the value is **True**, the reference is copied to the project directory when you build the project. If the value is **False**, the reference isn't copied.
 
-If you deploy an application that contains a reference to a custom component that is registered in the GAC, the component will not be deployed with the application, regardless of the <xref:Microsoft.VisualStudio.VCProjectEngine.VCProjectReference.CopyLocal%2A> setting. In earlier versions of Visual Studio, you could set the <xref:Microsoft.VisualStudio.VCProjectEngine.VCProjectReference.CopyLocal%2A> property on a reference to ensure that the assembly was deployed. Now, you must manually add the assembly to the \Bin folder. This puts all custom code under scrutiny, reducing the risk of publishing custom code with which you are not familiar.
+If you deploy an application that contains a reference to a custom component that is registered in the GAC, the component will not be deployed with the application, regardless of the <xref:Microsoft.VisualStudio.VCProjectEngine.VCProjectReference.CopyLocal%2A> setting. In earlier versions of Visual Studio, you could set the <xref:Microsoft.VisualStudio.VCProjectEngine.VCProjectReference.CopyLocal%2A> property on a reference to ensure that the assembly was deployed. Now, you must manually add the assembly to the \Bin folder. This puts all custom code under scrutiny, reducing the risk of publishing custom code with which you aren't familiar.
 
 By default, the <xref:Microsoft.VisualStudio.VCProjectEngine.VCProjectReference.CopyLocal%2A> property is set to **False** if the assembly or component is in the global assembly cache or is a framework component. Otherwise, the value is set to **True**. Project-to-project references are always set to **True**.
 
 ## Reference a project or assembly that targets a different version of .NET
 
-You can create applications that reference projects or assemblies that target a different version of the .NET. For example, you could create an application that targets .NET Framework 4.6, that references an assembly that targets .NET Framework 4.5. If you create a project that targets an earlier version of .NET, you cannot set a reference in that project to a project or assembly that targets a newer version.
+You can create applications that reference projects or assemblies that target a different version of the .NET. For example, you could create an application that targets .NET Framework 4.6, that references an assembly that targets .NET Framework 4.5. If you create a project that targets an earlier version of .NET, you can't set a reference in that project to a project or assembly that targets a newer version.
 
 For more information, see [Framework targeting overview](../ide/visual-studio-multi-targeting-overview.md).
 
 ## Project-to-project references
 
 Project-to-project references are references to projects that contain assemblies; you add project references by using the **Projects** tab of the Reference Manager dialog box. Visual Studio can find an assembly when given a path to the project.
 
-When you have a project that produces an assembly, you should reference the project and not use a file reference (see below). The advantage of a project-to-project reference is that it creates a dependency between the projects in the build system. The dependent project will be built if it has changed since the last time the referencing project was built. A file reference does not create a build dependency, so it is possible to build the referencing project without building the dependent project, and the reference can become obsolete. (That is, the project can reference a previously built version of the project.) This can result in several versions of a single DLL being required in the *bin* directory, which is not possible. When this conflict occurs, you will see a message such as "Warning: the dependency 'file' in project 'project' cannot be copied to the run directory because it would overwrite the reference 'file.'". For more information, see [Troubleshoot broken references](../ide/troubleshooting-broken-references.md) and [How to: Create and remove project dependencies](../ide/how-to-create-and-remove-project-dependencies.md).
+When you have a project that produces an assembly, you should reference the project and not use a file reference (see below). The advantage of a project-to-project reference is that it creates a dependency between the projects in the build system. The dependent project will be built if it has changed since the last time the referencing project was built. A file reference doesn't create a build dependency, so it's possible to build the referencing project without building the dependent project, and the reference can become obsolete. (That is, the project can reference a previously built version of the project.) This can result in several versions of a single DLL being required in the *bin* directory, which isn't possible. When this conflict occurs, you'll see a message such as "Warning: the dependency 'file' in project 'project' can't be copied to the run directory because it would overwrite the reference 'file.'". For more information, see [Troubleshoot broken references](../ide/troubleshooting-broken-references.md) and [How to: Create and remove project dependencies](../ide/how-to-create-and-remove-project-dependencies.md).
 
 > [!NOTE]
 > A file reference instead of a project-to-project reference is created if the target version of the .NET Framework of one project is version 4.5, and the target version of the other project is version 2, 3, 3.5, or 4.0.
 
 ## Shared project references
 
-Unlike most other project types, a *shared project* does not have any binary output. Instead, the code is compiled into each project that references it. [Shared Projects](/xamarin/cross-platform/app-fundamentals/shared-projects?tabs=windows) let you write common code that's referenced by a number of different application projects. The code is compiled as part of each referencing project and can include compiler directives to help incorporate platform-specific functionality into the shared code base. Add a reference to a shared project on the **Shared Projects** tab of the Reference Manager dialog box.
+Unlike most other project types, a *shared project* doesn't have any binary output. Instead, the code is compiled into each project that references it. [Shared Projects](/xamarin/cross-platform/app-fundamentals/shared-projects?tabs=windows) let you write common code that's referenced by a number of different application projects. The code is compiled as part of each referencing project and can include compiler directives to help incorporate platform-specific functionality into the shared code base. Add a reference to a shared project on the **Shared Projects** tab of the Reference Manager dialog box.
 
 ## File references