Merged main into live

Author: mijacobs

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

@@ -206,7 +206,7 @@ When you build a **Toolbox** control, Visual Studio creates a file named *Projec
 
 ## Related content
 
-- [Extend other parts of Visual Studio](../extensibility/extending-other-parts-of-visual-studio.md)
+- [Extend other parts of Visual Studio](/previous-versions/visualstudio/visual-studio-2017/extensibility/extending-other-parts-of-visual-studio)
 - [Create a WPF Toolbox Control](../extensibility/creating-a-wpf-toolbox-control.md)
-- [Extend other parts of Visual Studio](../extensibility/extending-other-parts-of-visual-studio.md)
+- [Extend other parts of Visual Studio](/previous-versions/visualstudio/visual-studio-2017/extensibility/extending-other-parts-of-visual-studio)
 - [Windows Forms control development basics](/dotnet/framework/winforms/controls/windows-forms-control-development-basics)

docs/extensibility/creating-an-extension-with-a-menu-command.md

@@ -118,6 +118,6 @@ This walkthrough has shown you only a small part of what you can do with a Visua
 
 4. Add IntelliSense, code suggestions, and other features to existing code editors: [Extend the editor and language services](../extensibility/extending-the-editor-and-language-services.md)
 
-5. Add Options and Property pages and user settings to your extension: [Extend properties and the Property window](../extensibility/extending-properties-and-the-property-window.md) and [Extend user settings and options](../extensibility/extending-user-settings-and-options.md)
+5. Add Options and Property pages and user settings to your extension: [Extend properties and the Property window](/previous-versions/visualstudio/visual-studio-2017/extensibility/extending-properties-and-the-property-window) and [Extend user settings and options](../extensibility/extending-user-settings-and-options.md)
 
    Other kinds of extensions require a little more work, such as creating a new type of project ([Extend projects](../extensibility/extending-projects.md)), or creating a new type of editor ([Create custom editors and designers](../extensibility/creating-custom-editors-and-designers.md)).

docs/extensibility/creating-custom-editors-and-designers.md

@@ -89,10 +89,10 @@ Explains how to implement document data and document views in custom editors.
 - [Legacy interfaces in the editor](/previous-versions/visualstudio/visual-studio-2015/extensibility/legacy-interfaces-in-the-editor?preserve-view=true&view=vs-2015)\
 Explains how to access the core editor by means of the legacy API.
 
-- [Develop a legacy language service](../extensibility/internals/developing-a-legacy-language-service.md)\
+- [Develop a legacy language service](/previous-versions/visualstudio/visual-studio-2017/extensibility/internals/developing-a-legacy-language-service)\
 Explains how to implement a language service.
 
-- [Extend other parts of Visual Studio](../extensibility/extending-other-parts-of-visual-studio.md)\
+- [Extend other parts of Visual Studio](/previous-versions/visualstudio/visual-studio-2017/extensibility/extending-other-parts-of-visual-studio)\
 Explains how to create UI elements that match the rest of Visual Studio.
 
 - <xref:Microsoft.VisualStudio.Shell.Interop.IVsEditorFactory>

docs/extensibility/editor-and-language-service-extensions.md

@@ -24,6 +24,6 @@ You can extend most features of the Visual Studio code editor. The editor is bas
 |[Extend the editor and language services](../extensibility/extending-the-editor-and-language-services.md)|Links to documents that introduce the design and features of the core editor and show how to extend it.|
 |[Legacy interfaces in the editor](/previous-versions/visualstudio/visual-studio-2015/extensibility/legacy-interfaces-in-the-editor?preserve-view=true&view=vs-2015)|Links to documents that explain how to access the core editor from existing code.|
 |[Create custom editors and designers](../extensibility/creating-custom-editors-and-designers.md)|Links to documents that explain how to create custom editors.|
-|[Legacy language service extensibility](../extensibility/internals/legacy-language-service-extensibility.md)|Links to documents that describe how to integrate programming languages into Visual Studio.|
+|[Legacy language service extensibility](/previous-versions/visualstudio/visual-studio-2017/extensibility/internals/legacy-language-service-extensibility)|Links to documents that describe how to integrate programming languages into Visual Studio.|
 |[Managed Extensibility Framework (MEF)](/dotnet/framework/mef/index)|Introduces the Managed Extensibility Framework (MEF).|
 |[Windows Presentation Foundation](/dotnet/framework/wpf/index)|Introduces the Windows Presentation Foundation (WPF).|

docs/extensibility/exposing-properties-to-the-properties-window.md

@@ -263,4 +263,4 @@ Visual Studio tool windows persist between Visual Studio sessions. For more info
 
 ## Related content
 
-- [Extend properties and the Property window](../extensibility/extending-properties-and-the-property-window.md)
+- [Extend properties and the Property window](/previous-versions/visualstudio/visual-studio-2017/extensibility/extending-properties-and-the-property-window)

docs/extensibility/extending-and-customizing-tool-windows.md

@@ -43,4 +43,4 @@ Visual Studio provides several different types of windows, for example tool wind
 ## Related content
 - [Create an extension with a tool window](../extensibility/creating-an-extension-with-a-tool-window.md)
 - [Extend projects](../extensibility/extending-projects.md)
-- [Extend solutions](../extensibility/extending-solutions.md)
+- [Extend solutions](/previous-versions/visualstudio/visual-studio-2017/extensibility/extending-solutions)

docs/extensibility/extending-the-editor-and-language-services.md

@@ -31,7 +31,7 @@ You can add language service features (such as IntelliSense) to your own editor,
 |[Walkthrough: Create a view adornment, commands, and settings (column guides)](../extensibility/walkthrough-creating-a-view-adornment-commands-and-settings-column-guides.md)|Walks through and explains building a view adornment that draws column guide lines to help you keep code to a certain display width.  Also shows reading and writing settings as well as declaring and implementing commands that you can invoke from the Command Window.|
 |[Editor imports](../extensibility/editor-imports.md)|Lists the services that an extension can import.|
 |[Adapt legacy code to the editor](/previous-versions/visualstudio/visual-studio-2015/extensibility/adapting-legacy-code-to-the-editor?preserve-view=true&view=vs-2015)|Explains different ways to adapt legacy code (pre-Visual Studio 2010) to extend the editor.|
-|[Migrate a legacy language service](../extensibility/internals/migrating-a-legacy-language-service.md)|Explains how to migrate a VSPackage based language service.|
+|[Migrate a legacy language service](/previous-versions/visualstudio/visual-studio-2017/extensibility/internals/migrating-a-legacy-language-service)|Explains how to migrate a VSPackage based language service.|
 |[Walkthrough: Link a content type to a file name extension](../extensibility/walkthrough-linking-a-content-type-to-a-file-name-extension.md)|Shows how to link a content type to a file name extension.|
 |[Walkthrough: Create a margin glyph](../extensibility/walkthrough-creating-a-margin-glyph.md)|Shows how to add an icon to a margin.|
 |[Walkthrough: Highlight text](../extensibility/walkthrough-highlighting-text.md)|Shows how to use *tags* to highlight text.|

docs/extensibility/extensibility-hello-world.md

@@ -119,6 +119,6 @@ You should see the output from your new custom command, in this case, the dialog
 Now that you know the basics of working with Visual Studio Extensibility, here's where you can learn more:
 
 * [Start to develop Visual Studio extensions](starting-to-develop-visual-studio-extensions.md) - Samples, tutorials. and publishing your extension
-* [What's new in the Visual Studio 2017 SDK](what-s-new-in-the-visual-studio-2017-sdk.md) - New extensibility features in Visual Studio 2017
+* [What's new in the Visual Studio 2017 SDK](/previous-versions/visualstudio/visual-studio-2017/extensibility/what-s-new-in-the-visual-studio-2017-sdk) - New extensibility features in Visual Studio 2017
 * [What's new in the Visual Studio 2019 SDK](whats-new-visual-studio-2019-sdk.md) - New extensibility features in Visual Studio 2019
 * [Inside the Visual Studio SDK](internals/inside-the-visual-studio-sdk.md) - Learn the details of Visual Studio Extensibility

docs/extensibility/getting-started-with-roslyn-analyzers.md

@@ -28,4 +28,4 @@ With live, project-based code analyzers in Visual Studio, API authors can ship d
 
 - [.NET compiler platform package version reference](roslyn-version-support.md)
 - [More docs on the GitHub OSS site](https://github.com/dotnet/roslyn/tree/main/docs/analyzers)
-- [FxCop rules implemented with Roslyn analyzers](../code-quality/fxcop-rule-port-status.md)
+- [FxCop rules implemented with Roslyn analyzers](/previous-versions/visualstudio/visual-studio-2019/code-quality/fxcop-rule-port-status)

docs/extensibility/how-to-add-a-dependency-to-a-vsix-package.md

@@ -27,7 +27,7 @@ You can set up a VSIX package deployment that installs any dependencies that are
 
 ## Require a specific Visual Studio release
 
-If your extension requires a specific version of Visual Studio 2017, for example, it depends on a feature released in 15.3, you can specify the build number in your VSIX **InstallationTarget**. For example, release 15.3 has a build number of '15.0.26730.3'. You can see the mapping of releases to build numbers [here](../install/visual-studio-build-numbers-and-release-dates.md). Note that using the release number '15.3' will not work correctly.
+If your extension requires a specific version of Visual Studio 2017, for example, it depends on a feature released in 15.3, you can specify the build number in your VSIX **InstallationTarget**. For example, release 15.3 has a build number of '15.0.26730.3'. You can see the mapping of releases to build numbers [here](/visualstudio/releases/2022/release-history#release-dates-and-build-numbers). Note that using the release number '15.3' will not work correctly.
 
 If your extension requires 15.3 or higher, you would declare the **InstallationTarget Version** as [15.0.26730.3, 16.0):