Merged main into live

Author: mijacobs

docs/extensibility/creating-a-windows-forms-toolbox-control.md

@@ -14,7 +14,7 @@ ms.subservice: extensibility-integration
 ---
 # Create a Windows Forms Toolbox Control
 
-The Windows Forms Toolbox Control item template that is included in the Visual Studio Extensibility Tools (VS SDK), lets you create a **Toolbox** control that is automatically added when the extension is installed. This walkthrough shows how to use the template to create a simple counter control that you can distribute to other users.
+The Windows Forms Toolbox Control item template that is included in the Visual Studio Extensibility Tools (VSSDK), lets you create a **Toolbox** control that is automatically added when the extension is installed. This walkthrough shows how to use the template to create a simple counter control that you can distribute to other users.
 
 ## Create the Toolbox Control
 

docs/extensibility/how-to-diagnose-ui-delays-caused-by-extensions.md

@@ -148,7 +148,7 @@ PerfView has detailed guidance under the **Help** menu that you can use to ident
 * [`https://github.com/Microsoft/vs-threading/blob/master/doc/index.md`](https://github.com/Microsoft/vs-threading/blob/master/doc/index.md)
 * [`https://github.com/Microsoft/vs-threading/blob/master/doc/cookbook_vs.md`](https://github.com/Microsoft/vs-threading/blob/master/doc/cookbook_vs.md)
 
-You can also use the new Visual Studio static analyzers for extensions (NuGet package [here](https://www.nuget.org/packages/microsoft.visualstudio.sdk.analyzers)), that provide guidance on best practices for writing efficient extensions. See a list of [VS SDK analyzers](https://github.com/Microsoft/VSSDK-Analyzers/blob/master/doc/index.md) and [threading analyzers](https://github.com/Microsoft/vs-threading/blob/master/doc/analyzers/index.md).
+You can also use the new Visual Studio static analyzers for extensions (NuGet package [here](https://www.nuget.org/packages/microsoft.visualstudio.sdk.analyzers)), that provide guidance on best practices for writing efficient extensions. See a list of [VSSDK analyzers](https://github.com/Microsoft/VSSDK-Analyzers/blob/master/doc/index.md) and [threading analyzers](https://github.com/Microsoft/vs-threading/blob/master/doc/analyzers/index.md).
 
 > [!NOTE]
 > If you are unable to address the unresponsiveness due to dependencies you do not have control over (for example, if your extension has to call synchronous VS services on the UI thread), we would like to know about it. If you are a member of our Visual Studio Partner program, you can contact us by submitting a developer support request. Otherwise, use the 'Report a Problem' tool to submit your feedback and include `"Extension UI Delay Notifications"` in the title. Please also include a detailed description of your analysis.

docs/extensibility/how-to-roundtrip-VSIXs.md

@@ -9,7 +9,7 @@ manager: "justinclareburt"
 ---
 # Make extensions compatible with Visual Studio 2019/2017 and Visual Studio 2015
 
-This document explains how to make extensibility projects round-trip between Visual Studio 2015 and Visual Studio 2019 or Visual Studio 2017. After completing this upgrade, a project will be able to open, build, install, and run in both Visual Studio 2015 and Visual Studio 2019 or 2017. As a reference, some extensions that can round-trip between Visual Studio 2015 and Visual Studio 2019 or 2017 can be found in the [VS SDK extensibility samples](https://github.com/Microsoft/VSSDK-Extensibility-Samples).
+This document explains how to make extensibility projects round-trip between Visual Studio 2015 and Visual Studio 2019 or Visual Studio 2017. After completing this upgrade, a project will be able to open, build, install, and run in both Visual Studio 2015 and Visual Studio 2019 or 2017. As a reference, some extensions that can round-trip between Visual Studio 2015 and Visual Studio 2019 or 2017 can be found in the [VSSDK extensibility samples](https://github.com/Microsoft/VSSDK-Extensibility-Samples).
 
 If you only intend to build in Visual Studio 2019/2017, but want the output VSIX to run in both Visual Studio 2015 and Visual Studio 2019/2017, then refer to the [Extension migration document](how-to-migrate-extensibility-projects-to-visual-studio-2017.md).
 
@@ -34,7 +34,7 @@ Here is an outline of the steps you'll complete in this document to round-trip a
 
 This document assumes that you have the following installed on your machine:
 
-* Visual Studio 2015 with the VS SDK installed
+* Visual Studio 2015 with the VSSDK installed
 * Visual Studio 2019 or 2017 with the Extensibility workload installed
 
 ## Recommended approach

docs/extensibility/installing-the-visual-studio-sdk.md

@@ -10,19 +10,19 @@ ms.subservice: extensibility-integration
 ---
 # Install the Visual Studio SDK
 
-The Visual Studio SDK (Software Development Kit) is an optional feature in Visual Studio setup. You can also install the VS SDK later on.
+The Visual Studio SDK (Software Development Kit) is an optional feature in Visual Studio setup. You can also install the VSSDK later on.
 
 ## Install the Visual Studio SDK as part of a Visual Studio installation
 
-To include the VS SDK in your Visual Studio installation, install the **Visual Studio extension development** workload under **Other Toolsets**. This workload will install the Visual Studio SDK and the necessary prerequisites. You can further tune the installation by selecting or unselecting components from the **Summary** view.
+To include the VSSDK in your Visual Studio installation, install the **Visual Studio extension development** workload under **Other Toolsets**. This workload will install the Visual Studio SDK and the necessary prerequisites. You can further tune the installation by selecting or unselecting components from the **Summary** view.
 
 ## Install the Visual Studio SDK after installing Visual Studio
 
 To install the Visual Studio SDK after completing your Visual Studio installation, rerun the Visual Studio installer and select the **Visual Studio extension development** workload.
 
 ## Install the Visual Studio SDK from a solution
 
-If you open a solution with an extensibility project without first installing the VS SDK, you'll be prompted by an **Install Missing Feature** dialog to install the **Visual Studio extension development** workload:
+If you open a solution with an extensibility project without first installing the VSSDK, you'll be prompted by an **Install Missing Feature** dialog to install the **Visual Studio extension development** workload:
 
 ::: moniker range="vs-2019"
 :::image type="content" source="media/install-extension-development.png" alt-text="Screenshot showing the Visual studio dialog to Install extension development workload.":::

docs/extensibility/internals/image-service-tools.md

@@ -10,7 +10,7 @@ ms.subservice: extensibility-integration
 ---
 # Image Service Tools
 
-The VS SDK includes several tools to help extension builders use the Visual Studio image service.
+The VSSDK includes several tools to help extension builders use the Visual Studio image service.
 
 - The [Manifest from Resources](../../extensibility/internals/manifest-from-resources.md) tool takes a list of image resources (.png or .xaml files) and generates an image manifest file.
 

docs/extensibility/migration/migrated-assemblies.md

@@ -1,6 +1,6 @@
 ---
-title: VS SDK NuGet packages
-description: Learn about VS SDK metapackage and other NuGet packages that you might need when migrating a Visual Studio extension to Visual Studio 2022.
+title: VSSDK NuGet packages
+description: Learn about VSSDK metapackage and other NuGet packages that you might need when migrating a Visual Studio extension to Visual Studio 2022.
 ms.date: 06/08/2021
 ms.topic: conceptual
 author: maiak
@@ -16,7 +16,7 @@ The easiest way to author Visual Studio extensions is with a reference to the
 [`Microsoft.VisualStudio.Sdk` NuGet package](https://www.nuget.org/packages/microsoft.visualstudio.sdk).
 This package is available for targeting Visual Studio 2017 (15.0), Visual Studio 2019 (16.0, 16.9), and now Visual Studio 2022.
 
-Depending on your extension, adding extra VS SDK packages that are not included in the above meta-package may be necessary.
+Depending on your extension, adding extra VSSDK packages that are not included in the above meta-package may be necessary.
 When referencing specific other SDK packages, these packages may vary across major VS versions.
 
 Note that many interop assemblies were embeddable prior to Visual Studio 2022. Beginning in Visual Studio 2022, embedding is no longer required or supported.

docs/extensibility/migration/removed-api-list.md

@@ -1,6 +1,6 @@
 ---
 title: APIs removed in Visual Studio 2022
-description: Learn about VS SDK APIs removed in Visual Studio 2022, for extension authors updating their extensions to work with Visual Studio 2022.
+description: Learn about VSSDK APIs removed in Visual Studio 2022, for extension authors updating their extensions to work with Visual Studio 2022.
 ms.date: 06/08/2021
 ms.topic: reference
 author: maiak

docs/extensibility/migration/target-previous-versions.md

@@ -36,7 +36,7 @@ Follow these steps on the VSIX project that should target Visual Studio 2019:
 
     Review the file for any other updates that may be necessary.
 
-1. Change the versions of the VS SDK packages that you reference in your project file:
+1. Change the versions of the VSSDK packages that you reference in your project file:
 
     ```diff
     -<PackageReference Include="Microsoft.VisualStudio.SDK" Version="17.0.0-preview.1" />

docs/extensibility/support-for-the-visual-studio-sdk.md

@@ -31,7 +31,7 @@ Several support options are available for customers who have questions about how
 
 ### Visual Studio SDK Samples
 
-You can find open source examples of VS SDK extensions on GitHub at [Visual Studio Samples](https://github.com/Microsoft/VSSDK-Extensibility-Samples). This GitHub repository contains samples that illustrate various extensible features in Visual Studio.
+You can find open source examples of VSSDK extensions on GitHub at [Visual Studio Samples](https://github.com/Microsoft/VSSDK-Extensibility-Samples). This GitHub repository contains samples that illustrate various extensible features in Visual Studio.
 
 ## Included Support
 

docs/extensibility/toc.yml

@@ -29,7 +29,7 @@
       href: migration/migrated-assemblies.md
     - name: ARM64 support
       href: arm64/target-arm64-visual-studio-extension.md
-    - name: VS SDK messages
+    - name: VSSDK messages
       href: vssdk-messages/index.md
   - name: What's New Visual Studio 2019 SDK
     items: