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

1329916: 15 files from docs/extensibility/internals and 5 from docs/extensibility.

Author: GitHubber17

docs/extensibility/internals/microsoft-help-viewer-sdk.md

@@ -816,13 +816,13 @@ To test this as if deployed:
 ### Additional Resources  
 For the Runtime API, see [Windows Help API](/previous-versions/windows/desktop/helpapi/helpapi-portal).  
 
-For additional information on how to leverage the Help API, see [Help Viewer Code Examples](http://visualstudiogallery.msdn.microsoft.com/f08f296f-7076-4aec-8da3-8f0fbe04461e)  
+For additional information on how to leverage the Help API, see [Help Viewer Code Examples](https://marketplace.visualstudio.com/items?itemName=RobChandlerHelpMVP.HelpViewer20CodeExamples)  
 
 To provide feedback about these components, use [Microsoft Connect](http://connect.microsoft.com/).  
 
 Please submit feature suggestions to [Microsoft User Voice](http://visualstudio.uservoice.com/forums/121579-visual-studio)  
 
-To get additional help, try the [MSDN Developer Documentation and Help System forums](http://social.msdn.microsoft.com/Forums/devdocs/threads)  
+To get additional help, try the [MSDN Developer Documentation and Help System forums](https://social.msdn.microsoft.com/Forums)  
 
 Updates on breaking issue, please see the [Help Viewer Readme](http://go.microsoft.com/fwlink/?LinkID=231397&clcid=0x409)  
 

docs/extensibility/internals/project-model-core-components.md

@@ -99,6 +99,6 @@ The following tables expand on the project model. The tables present brief descr
 ## See Also  
  <xref:Microsoft.VisualStudio.OLE.Interop.IOleCommandTarget>   
  [Checklist: Creating New Project Types](../../extensibility/internals/checklist-creating-new-project-types.md)   
- [Not in Build: Using HierUtil7 Project Classes to Implement a Project Type (C++)](http://msdn.microsoft.com/en-us/a5c16a09-94a2-46ef-87b5-35b815e2f346)   
+ [Not in Build: Using HierUtil7 Project Classes to Implement a Project Type (C++)](https://msdn.microsoft.com/library/a5c16a09-94a2-46ef-87b5-35b815e2f346)   
  [Supporting Symbol-Browsing Tools](../../extensibility/internals/supporting-symbol-browsing-tools.md)   
  [Elements of a Project Model](../../extensibility/internals/elements-of-a-project-model.md)

docs/extensibility/internals/project-property-user-interface.md

@@ -49,9 +49,9 @@ To determine the CATIDs for the project scope, the project subtype retrieves the
 
 Because the project subtype aggregates the <xref:Microsoft.VisualStudio.Shell.Interop.IVsHierarchy> object, it can override the definition of these properties to control which **Property Pages** dialog boxes are displayed. The project subtype can retrieve these properties from the inner base project and then add or remove CLSIDs as necessary.
 
-New property pages added by a project subtype are handed a project configuration browse object from the base project implementation. This project configuration browse object supports Automation Extenders. For more information on AutomationExtenders, see [Implementing and Using Automation Extenders](http://msdn.microsoft.com/Library/0d5c218c-f412-4b28-ab0c-33a611f62356). The property pages implemented by the project subtype call <xref:EnvDTE.Project.Extender%2A> to retrieve their own project subtype configuration browse object that extends the configuration browse object of the base project.
+New property pages added by a project subtype are handed a project configuration browse object from the base project implementation. This project configuration browse object supports Automation Extenders. For more information on AutomationExtenders, see [Implementing and Using Automation Extenders](https://msdn.microsoft.com/Library/0d5c218c-f412-4b28-ab0c-33a611f62356). The property pages implemented by the project subtype call <xref:EnvDTE.Project.Extender%2A> to retrieve their own project subtype configuration browse object that extends the configuration browse object of the base project.
 
 ## See also
 
 - <xref:EnvDTE.IFilterProperties>
-- [Property Pages Dialog Box](http://msdn.microsoft.com/en-us/4a3d34ac-ed03-45e8-ae60-a0e1aad300e4)
+- [Property Pages Dialog Box](/previous-versions/visualstudio/visual-studio-2010/as5chysf(v=vs.100))

docs/extensibility/internals/project-type-essentials.md

@@ -49,7 +49,7 @@ ms.workload:
 
 -   Project types are objects in a VSPackage that implement the set of interfaces [!INCLUDE[vsprvs](../../code-quality/includes/vsprvs_md.md)] expects. If you are using C# to develop a project type, the Managed Package Framework project classes implement the necessary interfaces for you and let you inherit that implementation. For more information, see [Using the Managed Package Framework to Implement a Project Type (C#)](../../extensibility/internals/using-the-managed-package-framework-to-implement-a-project-type-csharp.md).  
 
--   For C++ developers, the classes in the HierUtil library work in a similar manner. For more information, see [Not in Build: Using HierUtil7 Project Classes to Implement a Project Type (C++)](http://msdn.microsoft.com/en-us/a5c16a09-94a2-46ef-87b5-35b815e2f346).  
+-   For C++ developers, the classes in the HierUtil library work in a similar manner. For more information, see [Not in Build: Using HierUtil7 Project Classes to Implement a Project Type (C++)](https://msdn.microsoft.com/library/a5c16a09-94a2-46ef-87b5-35b815e2f346).  
 
 -   Project types can support data other than typical source code files that build into an .exe or .dll assembly. For example, [!INCLUDE[vsprvs](../../code-quality/includes/vsprvs_md.md)] database projects contain references to script and query files stored on disk and add commands to **Solution Explorer** to execute the scripts and queries against a database, but the projects do not support build behavior. For more information, see [Opening and Saving Project Items](../../extensibility/internals/opening-and-saving-project-items.md).  
 

docs/extensibility/internals/registering-interop-assembly-command-handlers.md

@@ -22,7 +22,7 @@ A VSPackage must register with [!INCLUDE[vsprvs](../../code-quality/includes/vsp
 
  The Managed Package Framework (MPF) provides this functionality through the <xref:Microsoft.VisualStudio.Shell.ProvideMenuResourceAttribute> class.  
 
- [Command Table Format Reference](http://msdn.microsoft.com/en-us/09e9c6ef-9863-48de-9483-d45b7b7c798f) resources are located in unmanaged satellite UI dlls.  
+ [Command Table Format Reference](https://msdn.microsoft.com/library/09e9c6ef-9863-48de-9483-d45b7b7c798f) resources are located in unmanaged satellite UI dlls.  
 
 ## Command Handler Registration of a VSPackage  
  A VSPackage acting as a handler for user interface (UI)-based commands requires a registry entry named after the VSPackage `GUID`. This registry entry specifies the location of the VSPackage's UI resource file and the menu resource within that file. The registry entry itself is located under HKEY_LOCAL_MACHINE\Software\Microsoft\VisualStudio\\*\<Version>*\Menus, where *\<Version>* is the version of [!INCLUDE[vsprvs](../../code-quality/includes/vsprvs_md.md)], for example 9.0.  

docs/extensibility/internals/registering-single-file-generators.md

@@ -68,4 +68,4 @@ To make a custom tool available in [!INCLUDE[vsprvs](../../code-quality/includes
  <xref:Microsoft.VisualStudio.Shell.Interop.IVsSingleFileGenerator>   
  [Implementing Single-File Generators](../../extensibility/internals/implementing-single-file-generators.md)   
  [Exposing Types to Visual Designers](../../extensibility/internals/exposing-types-to-visual-designers.md)   
- [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)

docs/extensibility/internals/support-for-project-and-configuration-properties.md

@@ -18,14 +18,14 @@ ms.workload:
 # Support for Project and Configuration Properties
 The **Properties** window in the [!INCLUDE[vsprvs](../../code-quality/includes/vsprvs_md.md)] integrated development environment (IDE) can display project and configuration properties. You can provide a property page for your own project type so that the user can set properties for your application.  
 
- By selecting a project node in **Solution Explorer** and then clicking **Properties** on the **Project** menu, you can open a dialog box that includes project and configuration properties. In [!INCLUDE[csprcs](../../data-tools/includes/csprcs_md.md)] and [!INCLUDE[vbprvb](../../code-quality/includes/vbprvb_md.md)], and project types derived from these languages, this dialog box appears as a tabbed page in the [General, Environment, Options Dialog Box](../../ide/reference/general-environment-options-dialog-box.md). For more information, see [Not in Build: Walkthrough: Exposing Project and Configuration Properties (C#)](http://msdn.microsoft.com/en-us/d850d63b-25e2-4505-9f3d-eb038d7c1d0e).  
+ By selecting a project node in **Solution Explorer** and then clicking **Properties** on the **Project** menu, you can open a dialog box that includes project and configuration properties. In [!INCLUDE[csprcs](../../data-tools/includes/csprcs_md.md)] and [!INCLUDE[vbprvb](../../code-quality/includes/vbprvb_md.md)], and project types derived from these languages, this dialog box appears as a tabbed page in the [General, Environment, Options Dialog Box](../../ide/reference/general-environment-options-dialog-box.md). For more information, see [Not in Build: Walkthrough: Exposing Project and Configuration Properties (C#)](https://msdn.microsoft.com/library/d850d63b-25e2-4505-9f3d-eb038d7c1d0e).  
 
  The Managed Package Framework for Projects (MPFProj) provides helper classes for creating and managing new project system. You can find the source code and compilation instructions at [MPF for Projects - Visual Studio 2013](https://github.com/tunnelvisionlabs/MPFProj10).  
 
 ## Persistence of Project and Configuration Properties  
  Project and configuration properties are persisted in a project file that has any file name extension associated with the project type, for example, .csproj, .vbproj, and .myproj. Language projects typically use a template file to generate the project file. However, there are actually several ways to associate project types and templates. For more information, see [Template Directory Description (.Vsdir) Files](../../extensibility/internals/template-directory-description-dot-vsdir-files.md).  
 
- Project and configuration properties are created by adding items to the template file. These properties are then available to any project created by using the project type that uses this template. [!INCLUDE[csprcs](../../data-tools/includes/csprcs_md.md)] projects and the MPFProj both use the [Not in Build: MSBuild Overview](http://msdn.microsoft.com/en-us/b588fd73-a45b-4706-908f-cc131bccfbde) schema for template files. These files have a PropertyGroup section for each configuration. Properties of projects are typically persisted in the first PropertyGroup section, which has a Configuration argument set to a null string.  
+ Project and configuration properties are created by adding items to the template file. These properties are then available to any project created by using the project type that uses this template. [!INCLUDE[csprcs](../../data-tools/includes/csprcs_md.md)] projects and the MPFProj both use the [Not in Build: MSBuild Overview](/previous-versions/visualstudio/visual-studio-2008/ms171452(v=vs.90)) schema for template files. These files have a PropertyGroup section for each configuration. Properties of projects are typically persisted in the first PropertyGroup section, which has a Configuration argument set to a null string.  
 
  The following code shows the start of a basic MSBuild project file.  
 

docs/extensibility/internals/uninstalling-a-vspackage-with-windows-installer.md

@@ -36,5 +36,5 @@ For the most part, Windows Installer can uninstall your VSPackage just by "undoi
 >  `Installed` is the property Windows Installer sets when it detects that your VSPackage has already been installed on the system.  
   
 ## See Also  
- [Windows Installer](http://msdn.microsoft.com/en-us/187d8965-c79d-4ecb-8689-10930fa8b3b5)   
+ [Windows Installer](https://msdn.microsoft.com/library/187d8965-c79d-4ecb-8689-10930fa8b3b5)   
  [Detecting System Requirements](../../extensibility/internals/detecting-system-requirements.md)

docs/extensibility/internals/using-the-automation-model.md

@@ -18,7 +18,7 @@ ms.workload:
 After you have connected your VSPackage to automation, you can obtain the properties and methods by calling the <xref:EnvDTE.DTEClass.GetObject%2A> method on the <xref:EnvDTE._DTE> object, passing a string representing the object you wish to retrieve.  
 
 ## Obtaining Project Objects  
- The following are two code examples that show how an automation consumer obtains the project automation objects. For information about how to get the DTE object, see [How to: Get References to the DTE and DTE2 Objects](http://msdn.microsoft.com/Library/c92e3c8e-82e6-4a67-85da-e43c50ffd8e4).  
+ The following are two code examples that show how an automation consumer obtains the project automation objects. For information about how to get the DTE object, see [How to: Get References to the DTE and DTE2 Objects](https://msdn.microsoft.com/Library/c92e3c8e-82e6-4a67-85da-e43c50ffd8e4).  
 
 ```vb  
 Sub DoAutomation()  

docs/extensibility/internals/visual-studio-command-table-dot-vsct-files.md

@@ -31,7 +31,7 @@ A command table configuration file is a text file that describes the set of comm
  [VSCT XML Schema Reference](../../extensibility/vsct-xml-schema-reference.md)  
  Provides details about each section of the command table XML configuration file.  
 
- [Command Table Configuration (.Ctc) Files](http://msdn.microsoft.com/en-us/3413dda1-f372-4669-bcf0-c64d3463842c)  
+ [Command Table Configuration (.Ctc) Files](https://msdn.microsoft.com/library/3413dda1-f372-4669-bcf0-c64d3463842c)  
  Presents an overview of the deprecated .ctc file format.  
 
  [How VSPackages Add User Interface Elements](../../extensibility/internals/how-vspackages-add-user-interface-elements.md)  

docs/extensibility/internals/vsix-color-editor.md

@@ -183,7 +183,7 @@ namespace MyCustomColors
  To make the changes permanent, rebuild and redeploy the Visual Studio extension after adding the new colors to the .pkgdef file and writing the code that will use those colors. Rebuilding the Visual Studio extension will merge the registry values for the new colors into the rest of the themes. Then relaunch Visual Studio, view the UI, and verify that the new colors appear as expected.  
 
 ## Notes  
- This tool is intended to be used for creating custom colors for the preexisting Visual Studio themes, or for editing the colors of a custom Visual Studio theme. To create complete custom Visual Studio themes, download the [Visual Studio Color Theme Editor extension](http://visualstudiogallery.msdn.microsoft.com/6f4b51b6-5c6b-4a81-9cb5-f2daa560430b) from the Visual Studio Extensions Gallery.  
+ This tool is intended to be used for creating custom colors for the preexisting Visual Studio themes, or for editing the colors of a custom Visual Studio theme. To create complete custom Visual Studio themes, download the [Visual Studio Color Theme Editor extension](https://marketplace.visualstudio.com/items?itemName=VisualStudioProductTeam.VisualStudio2015ColorThemeEditor) from the Visual Studio Extensions Gallery.  
 
 ## Sample Output  
  **XML color output**  

docs/extensibility/internals/vspackage-registration.md

@@ -54,4 +54,4 @@ VSPackages must advise [!INCLUDE[vsprvs](../../code-quality/includes/vsprvs_md.m
 
 ## See Also  
  [Windows Installer](/windows/desktop/Msi/windows-installer-portal)   
- [Managed Package Registration](http://msdn.microsoft.com/en-us/f69e0ea3-6a92-4639-8ca9-4c9c210e58a1)
+ [Managed Package Registration](https://msdn.microsoft.com/library/f69e0ea3-6a92-4639-8ca9-4c9c210e58a1)

docs/extensibility/internals/vspackage-setup-scenarios.md

@@ -25,7 +25,7 @@ The scenarios discussed in this topic are not your only choices, but they are pr
 
 ### Make your components independent
 
-Once you identify and populate a component, assign a `GUID`, and deploy the component, you cannot change its composition. If you do change a component's composition, the resulting component must be a new component with a new `GUID`. Given these facts, the greatest versioning flexibility is afforded by making each component independent, self-reliant unit. For more information about rules governing components, see [Changing the Component Code](/windows/desktop/Msi/changing-the-component-code) and [What Happens if the Component Rules Are Broken?](http://msdn.microsoft.com/library/aa372795\(VS.85\).aspx).
+Once you identify and populate a component, assign a `GUID`, and deploy the component, you cannot change its composition. If you do change a component's composition, the resulting component must be a new component with a new `GUID`. Given these facts, the greatest versioning flexibility is afforded by making each component independent, self-reliant unit. For more information about rules governing components, see [Changing the Component Code](/windows/desktop/Msi/changing-the-component-code) and [What Happens if the Component Rules Are Broken?](/windows/desktop/Msi/what-happens-if-the-component-rules-are-broken).
 
 ### Do not mix shared and private resources in a component
 
@@ -71,7 +71,7 @@ In this case, the VSPackage is a managed VSPackage installed in the global assem
 
 ![VS Side-by-Side VS Package Update installer](../../extensibility/internals/media/vs_sbys_packageupdate.gif "VS_SbyS_PackageUpdate")
 
-For more information on deployment of side-by-side assemblies, see [Simplifying Deployment and Solving DLL Hell with the .NET Framework](http://msdn.microsoft.com/library/ms973843.aspx).
+For more information on deployment of side-by-side assemblies, see [Simplifying Deployment and Solving DLL Hell with the .NET Framework](https://msdn.microsoft.com/library/ms973843.aspx).
 
 ## See Also
 

docs/extensibility/internals/when-to-create-project-types.md

@@ -47,14 +47,14 @@ Creating a new project type provides a basis for customizing [!INCLUDE[vsprvs](.
 |Task|Description|  
 |----------|-----------------|  
 |Handling commands|Any VSPackage can handle commands.|  
-|Building an editor|Custom editors can be registered. For more information, see [Document Windows and Editors](http://msdn.microsoft.com/en-us/603625e1-62b6-413a-bc44-089346e166bc).|  
+|Building an editor|Custom editors can be registered. For more information, see [Document Windows and Editors](https://msdn.microsoft.com/library/603625e1-62b6-413a-bc44-089346e166bc).|  
 |Owning windows|You can create both tool and document windows without adding a new project type.|  
 |Exposing properties in the Properties window|All objects can expose properties.|  
 
 ## Create a Project Subtype  
  You can use project subtypes to extend a managed project type without having to create a new project type. Project subtypes use COM aggregation to extend managed projects written in Microsoft [!INCLUDE[vbprvb](../../code-quality/includes/vbprvb_md.md)] or [!INCLUDE[csprcs](../../data-tools/includes/csprcs_md.md)]. With COM aggregation, you can reuse much of the managed project system implementation and  still customize for a particular scenario through aggregation and the use of supporting interfaces. For more information about project subtypes, see [Project Subtypes](../../extensibility/internals/project-subtypes.md).  
 
 ## See Also  
- [Document Windows and Editors](http://msdn.microsoft.com/en-us/603625e1-62b6-413a-bc44-089346e166bc)   
+ [Document Windows and Editors](https://msdn.microsoft.com/library/603625e1-62b6-413a-bc44-089346e166bc)   
  [Checklist: Creating New Project Types](../../extensibility/internals/checklist-creating-new-project-types.md)   
  [Hierarchies in Visual Studio](../../extensibility/internals/hierarchies-in-visual-studio.md)

docs/extensibility/internals/windows-installer-basics.md

@@ -69,4 +69,4 @@ The Windows Installer installs and uninstalls applications or software products
 -   No versioned resource should ever ship in more than one WIC.  
 
 ## See Also  
- [What Happens if the Component Rules Are Broken?](http://msdn.microsoft.com/library/aa372795\(VS.85\).aspx)
+ [What Happens if the Component Rules Are Broken?](/windows/desktop/Msi/what-happens-if-the-component-rules-are-broken)