MicrosoftDocs · ghogen · Jan 7, 2021 · Dec 31, 2020 · Jan 5, 2021 · Jan 7, 2021
diff --git a/docs/containers/overview.md b/docs/containers/overview.md
@@ -113,9 +113,9 @@ Repeat the process with the other projects that you want to control using Docker
 To add Kubernetes support, install the [Visual Studio Tools for Kubernetes](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vs-tools-for-kubernetes).
 ::: moniker-end
 
-With Kubernetes support, you can enable a connection between your local project and a Kubernetes cluster running in [Azure Kubernetes Service (AKS)](/azure/aks), and thereby modify and debug your services running in AKS using Visual Studio.  This service is provided by [Azure Dev Spaces](/azure/dev-spaces/quickstart-netcore-visualstudio). Azure Dev Spaces also lets you set up separate branches of your Kubernetes services called *dev spaces* for development purposes, so you can efficiently isolate production services from working versions in development, and keep distinct modifications cleanly separated from each other.
+With Kubernetes support, you can enable a connection between your local project and a Kubernetes cluster running in [Azure Kubernetes Service (AKS)](/azure/aks), and thereby modify and debug your services running using Visual Studio.  This service is provided by [Bridge to Kubernetes](overview-bridge-to-kubernetes.md). Bridge to Kubernetes also lets you set up separate branches of your Kubernetes services for development purposes, so you can efficiently isolate production services from working versions in development, and keep distinct modifications cleanly separated from each other.
 
-To add Kubernetes support to your projects, choose **Kubernetes/Helm** when you add container orchestration support. Several files are added to your project, including *azds.yaml*, which configures Azure Dev Spaces, and Helm charts which describe the structure of your Kubernetes services.
+To add Kubernetes support to your projects, choose **Kubernetes/Helm** when you add container orchestration support. Several files are added to your project, including Helm charts which describe the structure of your Kubernetes services. To get started with Bridge to Kubernetes, see [Use Bridge to Kubernetes](bridge-to-kubernetes.md).
 
 ## Service Fabric support
 

diff --git a/docs/debugger/mfc-debugging-techniques.md b/docs/debugger/mfc-debugging-techniques.md
@@ -1,5 +1,7 @@
 ---
 title: "MFC Debugging Techniques | Microsoft Docs"
+description: "Learn techniques for debugging MFC programs, including: coded breakpoints, tracing, memory leak detection, object memory dumps, and program size reduction."
+ms.custom: SEO-VS-2020
 ms.date: "11/04/2016"
 ms.topic: "conceptual"
 f1_keywords:

diff --git a/docs/debugger/microsoft-visual-studio-debugger-exception-thrown-dialog-box.md b/docs/debugger/microsoft-visual-studio-debugger-exception-thrown-dialog-box.md
@@ -1,7 +1,8 @@
 ---
 title: "Microsoft Visual Studio Debugger (Exception Thrown) Dialog Box | Microsoft Docs"
 titleSuffix: ""
-ms.custom: "seodec18"
+description: "Learn what to do when an exception occurs that your program needs to handle. You can: 1) break into the debugger; 2) continue; or 3) ignore."
+ms.custom: "SEO-VS-2020, seodec18"
 ms.date: "11/04/2016"
 ms.topic: "reference"
 f1_keywords:

diff --git a/docs/debugger/mixed-code-and-missing-information-in-the-call-stack-window.md b/docs/debugger/mixed-code-and-missing-information-in-the-call-stack-window.md
@@ -1,5 +1,6 @@
 ---
 title: "Mixed code & missing info in Call Stack window"
+description: In mixed-mode programs (native and managed) the debugger can't always show the complete call stack. Learn the possible discrepancies when native code calls managed code.
 ms.custom: SEO-VS-2020
 ms.date: "11/04/2016"
 ms.topic: "troubleshooting"

diff --git a/docs/debugger/mixed-mode-debugging-for-ia64-processes-is-unsupported.md b/docs/debugger/mixed-mode-debugging-for-ia64-processes-is-unsupported.md
@@ -1,5 +1,7 @@
 ---
 title: "Mixed mode debugging for IA64 processes is unsupported"
+description: Visual Studio does not support mixed-mode debugging of managed and native code in IA64 (Itanium) processes. See this article for workarounds.
+ms.custom: SEO-VS-2020
 ms.date: "11/04/2016"
 ms.topic: "conceptual"
 f1_keywords:

diff --git a/...ocesses-is-only-supported-when-using-microsoft-dotnet-framework-4-or-greater.md b/...ocesses-is-only-supported-when-using-microsoft-dotnet-framework-4-or-greater.md
@@ -1,5 +1,7 @@
 ---
 title: "Mixed mode debugging for x64 processes is only supported when using Microsoft.NET Framework 4 or greater"
+description: .NET Framework versions earlier than 4 do not provide support for mixed-mode debugging of x64 processes. See this article for workarounds.
+ms.custom: SEO-VS-2020
 ms.date: "11/04/2016"
 ms.topic: "conceptual"
 f1_keywords:

diff --git a/...debugging-is-only-supported-when-using-microsoft-dotnet-framework-2-0-or-3-0.md b/...debugging-is-only-supported-when-using-microsoft-dotnet-framework-2-0-or-3-0.md
@@ -1,5 +1,7 @@
 ---
 title: "Mixed Mode Debugging Is Only Supported when Using Microsoft .NET Framework 2.0 or 3.0 | Microsoft Docs"
+description: Versions of the Microsoft .NET Framework earlier than 2.0 do not provide support for mixed-mode debugging of 64-bit processes. See this article for workarounds.
+ms.custom: SEO-VS-2020
 ms.date: "11/04/2016"
 ms.topic: "conceptual"
 f1_keywords:

diff --git a/docs/debugger/native-run-time-checks-customization.md b/docs/debugger/native-run-time-checks-customization.md
@@ -1,5 +1,7 @@
 ---
 title: "Native Run-Time Checks Customization | Microsoft Docs"
+description: "Learn ways to customize run-time checking, including: specifying a message destination, writing an error reporting function, and querying for error information."
+ms.custom: SEO-VS-2020
 ms.date: "11/04/2016"
 ms.topic: "conceptual"
 f1_keywords:

diff --git a/docs/debugger/navigating-through-code-with-the-debugger.md b/docs/debugger/navigating-through-code-with-the-debugger.md
@@ -1,6 +1,7 @@
 ---
-title: Navigate code with the debugger | Microsoft Docs
-ms.custom: seodec18
+title: "Navigate code with the debugger | Microsoft Docs"
+description: "Learn how to use Visual Studio debugger to troubleshoot your code. Topics include: getting into break mode, stepping through code, and running to a target."
+ms.custom: "SEO-VS-2020, seodec18"
 ms.date: 11/12/2018
 ms.topic: how-to
 f1_keywords: 

diff --git a/docs/debugger/no-source-available.md b/docs/debugger/no-source-available.md
@@ -1,5 +1,7 @@
 ---
 title: "No Source Available | Microsoft Docs"
+description: Learn what you can do when your project does not have source code for the code that you want to view.
+ms.custom: SEO-VS-2020
 ms.date: "11/04/2016"
 ms.topic: "conceptual"
 f1_keywords:

diff --git a/docs/debugger/other-dialog-boxes.md b/docs/debugger/other-dialog-boxes.md
@@ -1,5 +1,7 @@
 ---
 title: "Other Dialog Boxes | Microsoft Docs"
+description: "This section documents two dialog boxes: About Microsoft Spy++, and Copyright Notice for Spy++ Help."
+ms.custom: SEO-VS-2020
 ms.date: "11/04/2016"
 ms.topic: "conceptual"
 helpviewer_keywords:

diff --git a/docs/debugger/output-tab-message-options-dialog-box.md b/docs/debugger/output-tab-message-options-dialog-box.md
@@ -1,5 +1,7 @@
 ---
 title: "Output Tab, Message Options Dialog Box | Microsoft Docs"
+description: Use the Output tab of Message Options to specify what message data appears in Messages View. This article describes the available settings.
+ms.custom: SEO-VS-2020
 ms.date: "11/04/2016"
 ms.topic: "reference"
 helpviewer_keywords:

diff --git a/docs/debugger/output-window-debugging-options-dialog-box.md b/docs/debugger/output-window-debugging-options-dialog-box.md
@@ -1,5 +1,7 @@
 ---
 title: "Output Window, Debugging, Options Dialog Box | Microsoft Docs"
+description: You can specify which types of debugging information appear in the Output window. Learn where to do this, and the types of information that you can control.
+ms.custom: SEO-VS-2020
 ms.date: "11/04/2016"
 ms.topic: "reference"
 f1_keywords:

diff --git a/docs/debugger/page-file-tab-process-properties-dialog-box.md b/docs/debugger/page-file-tab-process-properties-dialog-box.md
@@ -1,5 +1,7 @@
 ---
 title: "Page File Tab, Process Properties Dialog Box | Microsoft Docs"
+description: Use the Page File tab of Process Properties to examine the paging file of a process. This article describes the available settings.
+ms.custom: SEO-VS-2020
 ms.date: "11/04/2016"
 ms.topic: "reference"
 helpviewer_keywords:

diff --git a/docs/debugger/prefetch-content-for-windows-store-apps.md b/docs/debugger/prefetch-content-for-windows-store-apps.md
@@ -1,5 +1,7 @@
 ---
 title: Debug using prefetched content in UWP apps | Microsoft Docs
+description: To make your UWP app more responsive, use ContentPrefetcher to request Windows to prefetch web content. 
+ms.custom: SEO-VS-2020
 ms.date: 11/04/2016
 ms.topic: how-to
 dev_langs: 

diff --git a/docs/debugger/process-properties-dialog-box.md b/docs/debugger/process-properties-dialog-box.md
@@ -1,5 +1,7 @@
 ---
 title: "Process Properties Dialog Box | Microsoft Docs"
+description: "Use Process Properties to find out more about a process that you select in Processes View. There are four tabs: General, memory, Page File, and Space."
+ms.custom: SEO-VS-2020
 ms.date: "11/04/2016"
 ms.topic: "reference"
 helpviewer_keywords:

diff --git a/docs/debugger/process-search-dialog-box.md b/docs/debugger/process-search-dialog-box.md
@@ -1,5 +1,7 @@
 ---
 title: "Process Search Dialog Box | Microsoft Docs"
+description: Use Process Search to find and select the node for a specific process in Processes View. You can specify process ID, module string, and search direction.
+ms.custom: SEO-VS-2020
 ms.date: "11/04/2016"
 ms.topic: "reference"
 helpviewer_keywords:

diff --git a/docs/debugger/process-tab-window-properties-dialog-box.md b/docs/debugger/process-tab-window-properties-dialog-box.md
@@ -1,5 +1,7 @@
 ---
 title: "Process Tab, Window Properties Dialog Box | Microsoft Docs"
+description: Use the Process tab of Window Properties to view the ID of the thread that created the selected window, and the ID of the process that owns the thread.
+ms.custom: SEO-VS-2020
 ms.date: "11/04/2016"
 ms.topic: "reference"
 helpviewer_keywords:

diff --git a/docs/debugger/processes-view.md b/docs/debugger/processes-view.md
@@ -1,5 +1,7 @@
 ---
 title: "Processes View | Microsoft Docs"
+description: Processes view displays a tree of all active processes on your system. Learn about its contents and uses, and follow the links to additional information. 
+ms.custom: SEO-VS-2020
 ms.date: "11/04/2016"
 ms.topic: "conceptual"
 f1_keywords:

diff --git a/docs/debugger/project-settings-for-a-cpp-debug-configuration.md b/docs/debugger/project-settings-for-a-cpp-debug-configuration.md
@@ -1,6 +1,7 @@
 ---
 title: "Project settings for a C++ debug config"
-ms.custom: "seodec18"
+description: Configure C and C++ debugging in Property Pages. This article describes the settings and tells you their category.
+ms.custom: "SEO-VS-2020, seodec18"
 ms.date: "11/26/2018"
 ms.topic: "reference"
 f1_keywords: