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

Author: DennisLee-DennisLee

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)

docs/extensibility/keybinding-element.md

@@ -36,9 +36,9 @@ The KeyBinding element specifies keyboard shortcuts for the commands.
 |guid|Required.|  
 |id|Required.|  
 |editor|Required. The editor GUID indicates the editing context for which this keyboard shortcut will be active. The global binding scope value is "guidVSStd97".|  
-|key1|Required. Valid values include all typable alphanumerics, and also two-digit hexadecimal values preceded by 0x and [VK_constants](https://msdn.microsoft.com/library/windows/desktop/dd375731.aspx).|  
+|key1|Required. Valid values include all typable alphanumerics, and also two-digit hexadecimal values preceded by 0x and [VK_constants](/windows/desktop/inputdev/virtual-key-codes).|  
 |mod1|Optional. Any combination of **Ctrl**, **Alt**, and **Shift** separated by space.|  
-|key2|Optional. Valid values include all typable alphanumerics, and also two-digit hexadecimal values preceded by 0x and [VK_constants](https://msdn.microsoft.com/library/windows/desktop/dd375731.aspx).|  
+|key2|Optional. Valid values include all typable alphanumerics, and also two-digit hexadecimal values preceded by 0x and [VK_constants](/windows/desktop/inputdev/virtual-key-codes).|  
 |mod2|Optional. Any combination of **Ctrl**, **Alt**, and **Shift** separated by space.|  
 |emulator|Optional.|  
 |Condition|Optional. See [Conditional attributes](../extensibility/vsct-xml-schema-conditional-attributes.md).|  

docs/extensibility/localizing-menu-commands.md

@@ -31,7 +31,7 @@ You can provide localized text for menu and toolbar commands by creating localiz
 
 2.  Make a copy of *filename.en-US.vsct* for each localized language.  
 
-     Name each copy *filename.{Locale}.vsct*, where *{Locale}* is a particular culture name. For a list of culture name values, see [Locale IDs assigned by Microsoft](https://msdn.microsoft.com/en-us/library/windows/apps/jj657969.aspx).  
+     Name each copy *filename.{Locale}.vsct*, where *{Locale}* is a particular culture name. For a list of culture name values, see [Locale IDs assigned by Microsoft](/windows/uwp/publish/supported-languages).  
 
      These *filename.Locale.vsct* files will contain the localized menu text for your package.  
 

docs/extensibility/locating-visual-studio.md

@@ -38,4 +38,4 @@ To find Visual Studio and other tools in build environments, PowerShell scripts,
 
 ## See also
 
-* [Changes to Visual Studio 2017 setup](https://blogs.msdn.microsoft.com/heaths/2016/09/15/changes-to-visual-studio-15-setup)
+* [Changes to Visual Studio 2017 setup](https://blogs.msdn.microsoft.com/heaths/2016/09/15/changes-to-visual-studio-15-setup/)

docs/extensibility/managing-universal-windows-projects.md

@@ -13,7 +13,7 @@ ms.workload:
   - "vssdk"
 ---
 # Manage Universal Windows projects
-Universal Windows apps are apps that target both Windows 8.1 and Windows Phone 8.1, allowing developers to use code and other assets on both platforms. The shared code and resources are kept in a shared project, while the platform-specific code and resources are kept in separate projects, one for Windows and the other for Windows Phone. For more information about universal Windows apps, see [Universal Windows apps](http://msdn.microsoft.com/library/windows/apps/dn609832.aspx). Visual Studio extensions that manage projects should be aware that universal Windows app projects have a structure that differs from single-platform apps. This walkthrough shows you how to navigate the shared project and manage the shared items.  
+Universal Windows apps are apps that target both Windows 8.1 and Windows Phone 8.1, allowing developers to use code and other assets on both platforms. The shared code and resources are kept in a shared project, while the platform-specific code and resources are kept in separate projects, one for Windows and the other for Windows Phone. For more information about universal Windows apps, see [Universal Windows apps](https://msdn.microsoft.com/library/windows/apps/dn609832.aspx). Visual Studio extensions that manage projects should be aware that universal Windows app projects have a structure that differs from single-platform apps. This walkthrough shows you how to navigate the shared project and manage the shared items.  
 
 ## Prerequisites  
  Starting in Visual Studio 2015, you do not install the Visual Studio SDK from the download center. It is included as an optional feature in Visual Studio setup. You can also install the VS SDK later on. For more information, see [Install the Visual Studio SDK](../extensibility/installing-the-visual-studio-sdk.md).  

docs/extensibility/ngen-support.md

@@ -20,7 +20,7 @@ Below is an excerpt from MSDN that explains what "ngen" does:
 
 >The Native Image Generator (*Ngen.exe*) is a tool that improves the performance of managed applications. *Ngen.exe* creates native images, which are files containing compiled processor-specific machine code, and installs them into the native image cache on the local computer. The runtime can use native images from the cache instead of using the just-in-time (JIT) compiler to compile the original assembly.
 >
->from [Ngen.exe (Native Image Generator)](https://msdn.microsoft.com/en-us/library/6t9t5wcf(v=vs.110).aspx)
+>from [Ngen.exe (Native Image Generator)](/dotnet/framework/tools/ngen-exe-native-image-generator)
 
 In order to "ngen" an assembly, the VSIX must be installed "per-instance per-machine". This can be enabled by checking the "all-users" checkbox in the `extension.vsixmanifest` designer:
 
@@ -39,7 +39,7 @@ There are 4 properties that can be set:
         b. X86
         c. X64
         d. All
-4. **Ngen Priority** (integer between 1 and 3) - The Ngen Priority level is documented at [Ngen.exe priority levels](https://msdn.microsoft.com/en-us/library/6t9t5wcf(v=vs.110).aspx#Anchor_3).
+4. **Ngen Priority** (integer between 1 and 3) - The Ngen Priority level is documented at [Ngen.exe priority levels](/dotnet/framework/tools/ngen-exe-native-image-generator#priority-levels).
 
 Here's a look at the **Properties** window in action: