Merge pull request #2958 from DennisLee-DennisLee/v-dele-6-1329916

1329916: 1 file from docs/extensibility and 9 from docs/extensibility/internals.

Author: PRMerger14

docs/extensibility/image-service-and-catalog.md

@@ -656,7 +656,7 @@ b714fcf7-855e-4e4c-802a-1fd87144ccad,2,fda30684-682d-421c-8be4-650a2967058e,200
  Check [http://github.com/Microsoft/VSSDK-Extensibility-Samples](http://github.com/Microsoft/VSSDK-Extensibility-Samples) for the latest samples.  
   
 ### Tooling  
- A set of support tools for the Image Service was created to aid in creating/updating UI that works with the Image Service. For more information about each tool, check the documentation that comes with the tools. The tools are included as part of the [Visual Studio 2015 SDK.](http://msdn.microsoft.com/library/bb166441.aspx)  
+ A set of support tools for the Image Service was created to aid in creating/updating UI that works with the Image Service. For more information about each tool, check the documentation that comes with the tools. The tools are included as part of the [Visual Studio 2015 SDK](visual-studio-sdk.md).
 
  **ManifestFromResources**  
 

docs/extensibility/internals/automation-model-overview.md

@@ -23,7 +23,7 @@ The automation model consists of a set of objects against which you can write a
 
  ![Visual Studio automation object chart](../../extensibility/internals/media/vsvisualstudioautomationobjectchart.gif "vsVisualStudioAutomationObjectChart")  
 
- For more information, see [Extend the Visual Studio environment](http://msdn.microsoft.com/Library/4173a963-7ac7-4966-9bb7-e28a9d9f6792).  
+ For more information, see [Extend the Visual Studio environment](https://msdn.microsoft.com/Library/4173a963-7ac7-4966-9bb7-e28a9d9f6792).  
 
  The environment provides a model for different functional areas. For instance, there is a code model for various elements that you might find in code. There is a document model for various document elements. One area, the project area, is of particular interest to VSPackage providers. You will likely want your new project types to contribute to the automation model in much the same way as [!INCLUDE[vcprvc](../../code-quality/includes/vcprvc_md.md)] and [!INCLUDE[vbprvb](../../code-quality/includes/vbprvb_md.md)] contribute to the automation model. That process is outlined in [Provide automation for VSPackages](../../extensibility/internals/providing-automation-for-vspackages.md).  
 
@@ -38,7 +38,7 @@ The automation model consists of a set of objects against which you can write a
 -   Build  
 
 
-For more information on automation, see [Automation and extensibility for Visual Studio](http://msdn.microsoft.com/Library/f71a2253-3e68-4e5e-9a18-edbba816caf6). This document and the documents it provides links to, help you make decisions regarding how you should provide automation for your VSPackage.  
+For more information on automation, see [Automation and extensibility for Visual Studio](../extensibility-in-visual-studio.md). This document and the documents it provides links to, help you make decisions regarding how you should provide automation for your VSPackage.  
 
 ## See also  
- [How to: Create an add-in](http://msdn.microsoft.com/Library/50be56d2-e3a5-4cd2-8569-2a0666b268ce)
+ [How to: Create an add-in](https://msdn.microsoft.com/Library/50be56d2-e3a5-4cd2-8569-2a0666b268ce)

docs/extensibility/internals/best-practices-for-security-in-vspackages.md

@@ -25,8 +25,8 @@ To install the [!INCLUDE[vsipsdk](../../extensibility/includes/vsipsdk_md.md)] o
 
  Users should ensure that they install VSPackages only from trusted sources. Companies developing VSPackages should strongly name and sign them, to assure the user that tampering is prevented. Companies developing VSPackages should examine their external dependencies, such as web services and remote installation, to evaluate and correct any security issues.  
 
- For more information, see [Secure coding guidelines for the .NET Framework](http://msdn.microsoft.com/library/d55zzx87.aspx).  
+ For more information, see [Secure coding guidelines for the .NET Framework](/previous-versions/visualstudio/visual-studio-2008/d55zzx87(v=vs.90)).  
 
 ## See also  
- [Add-in security](http://msdn.microsoft.com/Library/44a5c651-6246-4310-b371-65378917c799)   
- [DDEX security](http://msdn.microsoft.com/en-us/44a52a70-5c98-450e-993d-4a3b32f69ba8)
+ [Add-in security](https://msdn.microsoft.com/Library/44a5c651-6246-4310-b371-65378917c799)   
+ [DDEX security](https://msdn.microsoft.com/library/44a52a70-5c98-450e-993d-4a3b32f69ba8)

docs/extensibility/internals/checklist-creating-new-project-types.md

@@ -30,7 +30,7 @@ You must complete several tasks to create a new project type. The following chec
 
     -   Project factory, to manage creating new projects and opening existing projects. For more information, see [Create project instances by using project factories](../../extensibility/internals/creating-project-instances-by-using-project-factories.md).  
 
-    -   Project hierarchy and command handling. For more information, see [Use HierUtil7 project classes to implement a project type (C++)](http://msdn.microsoft.com/en-us/a5c16a09-94a2-46ef-87b5-35b815e2f346), [Elements of a project model](../../extensibility/internals/elements-of-a-project-model.md), [Project model core components](../../extensibility/internals/project-model-core-components.md), and [MenuCommands vs. OleMenuCommands](../../extensibility/menucommands-vs-olemenucommands.md).  
+    -   Project hierarchy and command handling. For more information, see [Use HierUtil7 project classes to implement a project type (C++)](https://msdn.microsoft.com/library/a5c16a09-94a2-46ef-87b5-35b815e2f346), [Elements of a project model](../../extensibility/internals/elements-of-a-project-model.md), [Project model core components](../../extensibility/internals/project-model-core-components.md), and [MenuCommands vs. OleMenuCommands](../../extensibility/menucommands-vs-olemenucommands.md).  
 
     -   Project items management, including adding your project to the **New Project** dialog box. For more information, see [Add project and project item templates](../../extensibility/internals/adding-project-and-project-item-templates.md) and [Register project and item templates](../../extensibility/internals/registering-project-and-item-templates.md).  
 

docs/extensibility/internals/choosing-the-installation-directory-for-a-vspackage.md

@@ -60,4 +60,4 @@ If your VSPackage DLL includes resources and the **SatelliteDll\DllName** regist
 ## See also  
  [Choose between shared and versioned VSPackages](../../extensibility/choosing-between-shared-and-versioned-vspackages.md)   
  [Manage VSPackages](../../extensibility/managing-vspackages.md)   
- [Manage package registration](http://msdn.microsoft.com/en-us/f69e0ea3-6a92-4639-8ca9-4c9c210e58a1)
+ [Manage package registration](https://msdn.microsoft.com/library/f69e0ea3-6a92-4639-8ca9-4c9c210e58a1)

docs/extensibility/internals/context-parameters.md

@@ -61,4 +61,4 @@ In the [!INCLUDE[vsprvs](../../code-quality/includes/vsprvs_md.md)] integrated d
  [Custom parameters](../../extensibility/internals/custom-parameters.md)   
  [Wizards](../../extensibility/internals/wizards.md)   
  [Wizard (.vsz) file](../../extensibility/internals/wizard-dot-vsz-file.md)   
- [Context parameters for launching wizards](http://msdn.microsoft.com/Library/051a10f4-9e45-4604-b344-123044f33a24)
+ [Context parameters for launching wizards](https://msdn.microsoft.com/Library/051a10f4-9e45-4604-b344-123044f33a24)

docs/extensibility/internals/creating-project-instances-by-using-project-factories.md

@@ -22,7 +22,7 @@ Project types in [!INCLUDE[vsprvs](../../code-quality/includes/vsprvs_md.md)] us
 
  You can implement the <xref:Microsoft.VisualStudio.Shell.Interop.IVsProjectFactory> interface in a class in your project. Typically, it resides in its own module.  
 
- For an example of an implementation of the `IVsProjectFactory` interface, see *PrjFac.cpp*, which is contained in the [Basic project](http://msdn.microsoft.com/en-us/385fd2a3-d9f1-4808-87c2-a3f05a91fc36) sample directory.  
+ For an example of an implementation of the `IVsProjectFactory` interface, see *PrjFac.cpp*, which is contained in the [Basic project](https://www.microsoft.com/download/details.aspx?id=55984) sample directory.  
 
  Projects that support being aggregated by an owner must persist an owner key in their project file. When the <xref:Microsoft.VisualStudio.Shell.Interop.IVsProjectFactory.CreateProject%2A> method is called on a project with an owner key, the owned project converts its owner key to a project factory GUID then calls the `CreateProject` method on this project factory to do the actual creation.  
 

docs/extensibility/internals/elements-of-a-project-model.md

@@ -29,7 +29,7 @@ The interfaces and implementations of all projects in [!INCLUDE[vsprvs](../../co
 
 -   Each project must have a template file or wizard to initialize the new project file when a user creates a new project through the [!INCLUDE[vsprvs](../../code-quality/includes/vsprvs_md.md)] UI. For example, the [!INCLUDE[vcprvc](../../code-quality/includes/vcprvc_md.md)] templates initialize what eventually become .vcproj files.  
 
- The following illustration shows the primary interfaces, services, and objects that compose a typical project implementation. You can use the application helper, `HierUtil7`, to create the underlying objects and other programming boilerplate. For more information about the `HierUtil7` application helper, see [Use HierUtil7 project classes to implement a project type (C++)](http://msdn.microsoft.com/en-us/a5c16a09-94a2-46ef-87b5-35b815e2f346).  
+ The following illustration shows the primary interfaces, services, and objects that compose a typical project implementation. You can use the application helper, `HierUtil7`, to create the underlying objects and other programming boilerplate. For more information about the `HierUtil7` application helper, see [Use HierUtil7 project classes to implement a project type (C++)](https://msdn.microsoft.com/library/a5c16a09-94a2-46ef-87b5-35b815e2f346).  
 
  ![Visual Studio project model graphic](../../extensibility/internals/media/vsprojectmodel.gif "vsProjectModel")  
 Project model  
@@ -40,7 +40,7 @@ Project model
 
 ## See also  
  [Checklist: Create new project types](../../extensibility/internals/checklist-creating-new-project-types.md)   
- [Use HierUtil7 project classes to implement a project type (C++)](http://msdn.microsoft.com/en-us/a5c16a09-94a2-46ef-87b5-35b815e2f346)   
+ [Use HierUtil7 project classes to implement a project type (C++)](https://msdn.microsoft.com/library/a5c16a09-94a2-46ef-87b5-35b815e2f346)   
  [Project model core components](../../extensibility/internals/project-model-core-components.md)   
  [Create project instances by using project factories](../../extensibility/internals/creating-project-instances-by-using-project-factories.md)   
  [How to: Get a service](../../extensibility/how-to-get-a-service.md)   

docs/extensibility/internals/exposing-types-to-visual-designers.md

@@ -41,6 +41,6 @@ ms.workload:
      When a temporary PE is compiled, the only source file provided to the compiler is the custom tool output. Therefore, a custom tool that uses a temporary PE must generate output files that can be compiled independently of other files in the project.  
 
 ## See also  
- [Introduction to the BuildManager object](http://msdn.microsoft.com/en-us/50080ec2-c1c9-412c-98ef-18d7f895e7fa)   
+ [Introduction to the BuildManager object](https://msdn.microsoft.com/library/50080ec2-c1c9-412c-98ef-18d7f895e7fa)   
  [Implement single-file generators](../../extensibility/internals/implementing-single-file-generators.md)   
  [Register single-file generators](../../extensibility/internals/registering-single-file-generators.md)

docs/extensibility/internals/installing-vspackages-with-windows-installer.md

@@ -18,7 +18,7 @@ ms.workload:
 # Installing VSPackages With Windows Installer
 Integrating your VSPackage into [!INCLUDE[vsprvs](../../code-quality/includes/vsprvs_md.md)] requires more than just copying files to a user's computer. Your VSPackage's installer must install the VSPackage and its dependent files, and register and integrate them into [!INCLUDE[vsprvs](../../code-quality/includes/vsprvs_md.md)]. Your VSPackage can take advantage of integration features such as displaying an icon on the [!INCLUDE[vsprvs](../../code-quality/includes/vsprvs_md.md)] splash screen and About dialog box.  
 
- Microsoft Windows Installer files are the recommended way to distribute your VSPackages. Easy-to-use Windows Installer packages can run on any Windows operating system supported by [!INCLUDE[vsprvs](../../code-quality/includes/vsprvs_md.md)]. For more information, see [Windows Installer](http://msdn.microsoft.com/en-us/121be21b-b916-43e2-8f10-8b080516d2a0).  
+ Microsoft Windows Installer files are the recommended way to distribute your VSPackages. Easy-to-use Windows Installer packages can run on any Windows operating system supported by [!INCLUDE[vsprvs](../../code-quality/includes/vsprvs_md.md)]. For more information, see [Windows Installer](https://msdn.microsoft.com/library/121be21b-b916-43e2-8f10-8b080516d2a0).  
 
 ## In This Section  
  [Windows Installer Basics](../../extensibility/internals/windows-installer-basics.md)