delete vs-2015 see also links

Author: gewarren

docs/extensibility/document-data-and-document-view-in-custom-editors.md

@@ -31,12 +31,12 @@ A custom editor consists of two parts: a document data object and a document vie
  There are two options for creating a view for a custom editor. One is the in-place activation model, where the view is hosted in a window using either an ActiveX control or a document data object. The second is the simplified embedding model, where the view is hosted by [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] and <xref:Microsoft.VisualStudio.Shell.Interop.IVsWindowPane> is implemented to handle window commands. For information about the in-place activation model, see [In-place activation](../extensibility/in-place-activation.md). For information about the simplified embedding model, see [Simplified embedding](../extensibility/simplified-embedding.md).
 
 ## See also
+
 - [Support multiple document views](../extensibility/supporting-multiple-document-views.md)
 - [Simplified embedding](../extensibility/simplified-embedding.md)
 - [How to: Attach views to document data](../extensibility/how-to-attach-views-to-document-data.md)
 - [Document lock holder management](../extensibility/document-lock-holder-management.md)
 - [Single and multi-tab views](../extensibility/single-and-multi-tab-views.md)
 - [Save a standard document](../extensibility/internals/saving-a-standard-document.md)
 - [Persistence and the running document table](../extensibility/internals/persistence-and-the-running-document-table.md)
-- [Determine which editor opens a file in a project](../extensibility/internals/determining-which-editor-opens-a-file-in-a-project.md)
-- [Editor factories](/visualstudio/extensibility/editor-factories?view=vs-2015)
+- [Determine which editor opens a file in a project](../extensibility/internals/determining-which-editor-opens-a-file-in-a-project.md)

docs/extensibility/internals/guids-and-ids-of-visual-studio-commands.md

@@ -55,6 +55,6 @@ The GUID and ID values of the commands included in the Visual Studio integrated
      There is no reliable way to search on dynamic text. Instead, find a group that hosts the desired command by consulting [GUIDs and IDs of Visual Studio menus](../../extensibility/internals/guids-and-ids-of-visual-studio-menus.md) or [GUIDs and IDs of Visual Studio toolbars](../../extensibility/internals/guids-and-ids-of-visual-studio-toolbars.md), and search on the ID of that group. If the command definition does not have the group as its [Parent element](../../extensibility/parent-element.md), search *SharedCmdPlace.vsct* and *ShellCmdPlace.vsct* (or *VsDbgCmdPlace.vsct* for debugger commands) for a `<CommandPlacement>` element that sets the parent of the command. *SharedCmdPlace.vsct*, *ShellCmdPlace.vsct*, and *VsDbgCmdPlace.vsct* are in the *\<Visual Studio SDK installation path\>\VisualStudioIntegration\Common\Inc\\* folder.
 
 ## See also
-- [MenuCommands vs. OleMenuCommands](/visualstudio/extensibility/menucommands-vs-olemenucommands?view=vs-2015)
+
 - [Visual Studio command table (.vsct) files](../../extensibility/internals/visual-studio-command-table-dot-vsct-files.md)
 - [VSCT XML schema reference](../../extensibility/vsct-xml-schema-reference.md)

docs/extensibility/internals/ide-defined-commands-for-extending-project-systems.md

@@ -64,6 +64,6 @@ When you want to extend project systems, you can use commands and command groups
 |IDG_VS_CTXT_PROJECT_PROPERTIES|Commands that provide access to the **Project Properties** dialog box.|
 
 ## See also
+
 - [How VSPackages Add User Interface Elements](../../extensibility/internals/how-vspackages-add-user-interface-elements.md)
-- [MenuCommands Vs. OleMenuCommands](/visualstudio/extensibility/menucommands-vs-olemenucommands?view=vs-2015)
 - [Creating Reusable Groups of Buttons](../../extensibility/creating-reusable-groups-of-buttons.md)

docs/extensibility/internals/making-commands-available.md

@@ -144,7 +144,6 @@ Also notice that every UI context must be given in a separate `VisibilityItem` e
 ## See also
 
 - [Add a command to the Solution Explorer toolbar](../../extensibility/adding-a-command-to-the-solution-explorer-toolbar.md)
-- [MenuCommands Vs. OleMenuCommands](/visualstudio/extensibility/menucommands-vs-olemenucommands?view=vs-2015)
 - [How VSPackages Add User Interface Elements](../../extensibility/internals/how-vspackages-add-user-interface-elements.md)
 - [Command Routing in VSPackages](../../extensibility/internals/command-routing-in-vspackages.md)
 - [Dynamically Adding Menu Items](../../extensibility/dynamically-adding-menu-items.md)

docs/extensibility/internals/syntax-coloring-in-a-legacy-language-service.md

@@ -67,8 +67,4 @@ Visual Studio uses a coloring service to identify elements of the language and d
 
 - [Custom Colorable Items](../../extensibility/internals/custom-colorable-items.md)
 
- Discusses how to implement custom colorable items.
-
-## See also
-
-- [Using Fonts and Colors](/visualstudio/extensibility/using-fonts-and-colors?view=vs-2015)
+ Discusses how to implement custom colorable items.

docs/extensibility/localizing-menu-commands.md

@@ -160,6 +160,6 @@ You must modify the *assemblyinfo.cs* file and the project file to incorporate t
      This creates a main assembly, and resource assemblies for each language. For information on localizing the deployment process, see [Localize VSIX packages](../extensibility/localizing-vsix-packages.md)
 
 ## See also
+
 - [Extend menus and commands](../extensibility/extending-menus-and-commands.md)
-- [MenuCommands vs. OleMenuCommands](/visualstudio/extensibility/menucommands-vs-olemenucommands?view=vs-2015)
 - [Globalize and Localize applications](../ide/globalizing-and-localizing-applications.md)

docs/extensibility/visual-studio-sdk.md

@@ -68,6 +68,7 @@ The Visual Studio SDK helps you extend Visual Studio features or integrate new f
 - [Extending Visual Studio](https://blog.slaks.net/2013-10-18/extending-visual-studio-part-1-getting-started/)
 
 ## See also
+
 - [Create an extension with a menu command](../extensibility/creating-an-extension-with-a-menu-command.md)
 - [How to: Migrate extensibility projects to Visual Studio 2017](../extensibility/how-to-migrate-extensibility-projects-to-visual-studio-2017.md)
 - [FAQ: Converting add-ins to VSPackage extensions](../extensibility/faq-converting-add-ins-to-vspackage-extensions.md)
@@ -87,5 +88,4 @@ The Visual Studio SDK helps you extend Visual Studio features or integrate new f
 - [Ship Visual Studio extensions](../extensibility/shipping-visual-studio-extensions.md)
 - [Inside the Visual Studio SDK](../extensibility/internals/inside-the-visual-studio-sdk.md)
 - [Support for the Visual Studio SDK](../extensibility/support-for-the-visual-studio-sdk.md)
-- [Archive](/visualstudio/extensibility/archive?view=vs-2015)
 - [Visual Studio SDK reference](../extensibility/visual-studio-sdk-reference.md)

docs/extensibility/vscodewindowmanager-object.md

@@ -15,13 +15,11 @@ ms.workload:
   - "vssdk"
 ---
 # VSCodeWindowManager object
+
 The language service implements the code window manager and is responsible for managing adornments (for example, the drop-down bar). For more information, see [Customizing Code Windows by Using the Legacy API](/visualstudio/extensibility/customizing-code-windows-by-using-the-legacy-api?view=vs-2015).
 
- The following table shows the interfaces in the `VSCodeWindowManager` object.
+The following table shows the interfaces in the `VSCodeWindowManager` object.
 
 |Interface|Description|
 |---------------|-----------------|
-|<xref:Microsoft.VisualStudio.TextManager.Interop.IVsCodeWindowManager>|Allows adornments (such as drop-down bars) to be added to or removed from a code window.|
-
-## See also
-- [Customizing code windows by using the legacy API](/visualstudio/extensibility/customizing-code-windows-by-using-the-legacy-api?view=vs-2015)
+|<xref:Microsoft.VisualStudio.TextManager.Interop.IVsCodeWindowManager>|Allows adornments (such as drop-down bars) to be added to or removed from a code window.|

docs/extensibility/vstextview-object.md

@@ -15,9 +15,10 @@ ms.workload:
   - "vssdk"
 ---
 # VSTextView object
+
 The text view is a window that lets users view and edit the Unicode text of the text buffer. Essentially, the view is what most users refer to as the editor. Because the view is separated from the buffer by various text layers (word wrap, outlining text, and so on), the view is not guaranteed to be an exact representation of the text in the buffer. For more information about the text view, see [Accessing theText view by using the legacy API](/visualstudio/extensibility/accessing-thetext-view-by-using-the-legacy-api?view=vs-2015).
 
- The following table shows the interfaces in the <xref:Microsoft.VisualStudio.TextManager.Interop.VsTextView> object.
+The following table shows the interfaces in the <xref:Microsoft.VisualStudio.TextManager.Interop.VsTextView> object.
 
 |Interface|Description|
 |---------------|-----------------|
@@ -32,6 +33,6 @@ The text view is a window that lets users view and edit the Unicode text of the
 |<xref:Microsoft.VisualStudio.TextManager.Interop.IVsThreadSafeTextView>|Performs operations on the view from a different thread.|
 
 ## See also
+
 - [Figures edit](https://www.microsoft.com/download/details.aspx?id=55984)
-- [VSTextBuffer object](../extensibility/vstextbuffer-object.md)
-- [Accessing theText view by using the legacy API](/visualstudio/extensibility/accessing-thetext-view-by-using-the-legacy-api?view=vs-2015)
+- [VSTextBuffer object](../extensibility/vstextbuffer-object.md)

docs/extensibility/walkthrough-adding-features-to-a-custom-editor.md

@@ -147,5 +147,5 @@ After you create a custom editor, you can add more features to it.
   - `Window.Object`
 
 ## See also
-- [Contribute to the automation model](../extensibility/internals/contributing-to-the-automation-model.md)
-- [How to: Provide context for editors](/visualstudio/extensibility/how-to-provide-context-for-editors?view=vs-2015)
+
+- [Contribute to the automation model](../extensibility/internals/contributing-to-the-automation-model.md)