Merge pull request #2959 from MicrosoftDocs/master

9/19 AM Publish

Author: Taojunshen

docs/docfx.json

@@ -84,7 +84,6 @@
       "defaultDevLang": "csharp",
       "ms.prod": "visual-studio-dev15",
       "searchScope": ["VS IDE"],
-      "hideScope": true,
       "uhfHeaderId": "MSDocsHeader-VisualStudio",
       "titleSuffix": "Visual Studio",
       "featureFlags": [

docs/extensibility/debugger/roadmap-for-extending-the-debugger.md

@@ -40,7 +40,7 @@ This documentation provides guide and reference information for extending the [!
 
      [Create a custom debug engine](../../extensibility/debugger/creating-a-custom-debug-engine.md)  
 
-     [Tutorial: Build a debug engine using ATL COM](http://msdn.microsoft.com/en-us/9097b71e-1fe7-48f7-bc00-009e25940c24)  
+     [Tutorial: Build a debug engine using ATL COM](https://msdn.microsoft.com/library/9097b71e-1fe7-48f7-bc00-009e25940c24)  
 
      [Implement a port supplier](../../extensibility/debugger/implementing-a-port-supplier.md)  
 

docs/extensibility/debugger/sample-implementation-of-locals.md

@@ -61,7 +61,7 @@ ms.workload:
  [Evaluation context](../../extensibility/debugger/evaluation-context.md)  
  Provides the arguments that are passed when the DE calls the expression evaluator (EE).  
 
- [MyCEE sample](http://msdn.microsoft.com/en-us/624a018b-9179-402f-9d48-3aec87b48f4f)  
+ [MyCEE sample](https://msdn.microsoft.com/library/624a018b-9179-402f-9d48-3aec87b48f4f)  
  Demonstrates one implementation approach to creating an expression evaluator for the MyC language.  
 
 ## See also  

docs/extensibility/debugger/visual-studio-debugger-extensibility.md

@@ -22,7 +22,7 @@ Visual Studio includes a fully interactive source code debugger, providing a pow
 
  The [!INCLUDE[vsipsdk](../../extensibility/includes/vsipsdk_md.md)] includes a complete reference to all [!INCLUDE[vsprvs](../../code-quality/includes/vsprvs_md.md)] elements required to create a new DE. In addition, there are samples and tutorials that will help get you started.  
 
- For a complete sample of a language project system with debugging support, see the [IronPython sample](http://msdn.microsoft.com/en-us/4c41695c-12c1-4670-b43b-d8d84c9e4089).  
+ For a complete sample of a language project system with debugging support, see the [IronPython sample](https://www.microsoft.com/download/details.aspx?id=55984).  
 
  The following sections describe how to extend the debugger by using the [!INCLUDE[vsipsdk](../../extensibility/includes/vsipsdk_md.md)].  
 

docs/extensibility/designer-initialization-and-metadata-configuration.md

@@ -94,4 +94,4 @@ Manipulation of the metadata and filter attributes associated with a designer or
  <xref:Microsoft.VisualStudio.Shell.Design.DesignSurfaceExtension>   
  <xref:Microsoft.VisualStudio.Shell.Design.DesignSurfaceExtensionAttribute>   
  <xref:System.ComponentModel.ToolboxItemFilterType>   
- [Extend dDesign-time support](http://msdn.microsoft.com/Library/d6ac8a6a-42fd-4bc8-bf33-b212811297e2)
+ [Extend design-time support](https://msdn.microsoft.com/Library/d6ac8a6a-42fd-4bc8-bf33-b212811297e2)

docs/extensibility/error-handling-and-return-values.md

@@ -52,6 +52,6 @@ VSPackages and COM use the same architecture for errors. The `SetErrorInfo` and
 
 ## See also  
  <xref:Microsoft.VisualStudio.OLE.Interop.IOleCommandTarget>   
- [SetErrorInfo (Component Automation)](http://msdn.microsoft.com/8eaacfac-fc37-4eaa-870b-10b99d598d66)   
+ [SetErrorInfo (Component Automation)](/previous-versions/windows/desktop/api/oleauto/nf-oleauto-seterrorinfo)   
  [GetErrorInfo](/previous-versions/windows/desktop/api/oleauto/nf-oleauto-geterrorinfo)   
  [ISupportErrorInfo Interface](/previous-versions/windows/desktop/api/oaidl/nn-oaidl-isupporterrorinfo)

docs/extensibility/getting-font-and-color-information-for-text-colorization.md

@@ -44,4 +44,4 @@ After you have obtained font and color information, parse the text to be display
 - <xref:Microsoft.VisualStudio.Shell.Interop.IVsFontAndColorDefaults>
 - [Use fonts and text](/dotnet/framework/winforms/advanced/using-fonts-and-text)
 - [Work with color](/cpp/windows/working-with-color-image-editor-for-icons)
-- [GDI (graphics device interface)](http://msdn.microsoft.com/en-us/7e1d4540-bb2e-4257-8eee-eee376acba83)
+- [GDI (graphics device interface)](https://msdn.microsoft.com/library/7e1d4540-bb2e-4257-8eee-eee376acba83)

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

@@ -20,13 +20,13 @@ With live, project-based code analyzers in Visual Studio, API authors can ship d
 
 [Add code fixes Walkthrough: Provide users fixes for analyzer issues](https://msdn.microsoft.com/magazine/dn904670.aspx)
 
-[Introduction and walkthrough of real world analyzer talk](http://channel9.msdn.com/events/Build/2015/3-725)
+[Introduction and walkthrough of real world analyzer talk](https://channel9.msdn.com/events/Build/2015/3-725)
 
-[Real world Roslyn analyzer](../extensibility/roslyn-analyzers-and-code-aware-library-for-immutablearrays.md) that you can also watch as a [talk](http://channel9.msdn.com/events/Build/2015/3-725)
+[Real world Roslyn analyzer](../extensibility/roslyn-analyzers-and-code-aware-library-for-immutablearrays.md) that you can also watch as a [talk](https://channel9.msdn.com/events/Build/2015/3-725)
 
 [Several examples on github, grouped into three kinds of analyzers](https://github.com/dotnet/roslyn/blob/master/docs/analyzers/Analyzer%20Samples.md)
 
-[Introduction and tour of a few analyzers talk](http://channel9.msdn.com/Events/dotnetConf/2015/NET-Compiler-Platform-Roslyn-Analyzers-and-the-Rise-of-Code-Aware-Libraries)
+[Introduction and tour of a few analyzers talk](https://channel9.msdn.com/Events/dotnetConf/2015/NET-Compiler-Platform-Roslyn-Analyzers-and-the-Rise-of-Code-Aware-Libraries)
 
 ## See also
 

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

@@ -46,6 +46,6 @@ The VSIXInstaller will detect earlier versions of Visual Studio and inform the u
 
 ## See also
 
- [VSIX extension schema 1.0 reference](http://msdn.microsoft.com/en-us/76e410ec-b1fb-4652-ac98-4a4c52e09a2b)   
+ [VSIX extension schema 1.0 reference](https://msdn.microsoft.com/library/76e410ec-b1fb-4652-ac98-4a4c52e09a2b)   
  [Anatomy of a VSIX package](../extensibility/anatomy-of-a-vsix-package.md)   
  [Prepare extensions for Windows Installer deployment](../extensibility/preparing-extensions-for-windows-installer-deployment.md)

docs/extensibility/how-to-clear-the-undo-stack.md

@@ -19,7 +19,7 @@ The following procedure below explains how to clear the undo stack.
 
 ## To clear the undo stack  
 
-1.  To clear the undo stack use the [IOleUndoManager::DiscardFrom](http://msdn.microsoft.com/library/windows/desktop/ms693799) method. The following is an example of this:  
+1.  To clear the undo stack use the [IOleUndoManager::DiscardFrom](/windows/desktop/api/ocidl/nf-ocidl-ioleundomanager-discardfrom) method. The following is an example of this:  
 
     ```  
     HRESULT CCmdWindow::ClearUndoStack()  

docs/extensibility/how-to-use-linked-undo-management.md

@@ -21,7 +21,7 @@ Linked undo allows the user to simultaneously undo the same edits in multiple fi
 
 1.  Call `QueryService` on `SVsLinkedUndoManager` to get a pointer to `IVsLinkedUndoTransactionManager`.  
 
-2.  Create the initial parent linked undo unit by calling <xref:Microsoft.VisualStudio.TextManager.Interop.IVsLinkedUndoTransactionManager.OpenLinkedUndo%2A>. This sets the starting point for a set of undo stacks to be grouped into linked undo stacks. In the `OpenLinkedUndo` method you will also need to specify whether you want the linked undo to be strict or non-strict. Non-strict linked undo behavior means that some of the documents with linked undo siblings can close and still leave the other linked undo siblings on their stacks. Strict linked undo behavior specifies that all the linked undo sibling stacks have to be undone together or not at all. Add the subsequent linked undo stacks by calling [IOleUndoManager::Add](http://msdn.microsoft.com/library/windows/desktop/ms680135) method.  
+2.  Create the initial parent linked undo unit by calling <xref:Microsoft.VisualStudio.TextManager.Interop.IVsLinkedUndoTransactionManager.OpenLinkedUndo%2A>. This sets the starting point for a set of undo stacks to be grouped into linked undo stacks. In the `OpenLinkedUndo` method you will also need to specify whether you want the linked undo to be strict or non-strict. Non-strict linked undo behavior means that some of the documents with linked undo siblings can close and still leave the other linked undo siblings on their stacks. Strict linked undo behavior specifies that all the linked undo sibling stacks have to be undone together or not at all. Add the subsequent linked undo stacks by calling [IOleUndoManager::Add](/windows/desktop/api/ocidl/nf-ocidl-ioleundomanager-add) method.  
 
 3.  Call <xref:Microsoft.VisualStudio.TextManager.Interop.IVsLinkedUndoTransactionManager.CloseLinkedUndo%2A> to roll back all of the linked undo units as one.  
 
@@ -30,6 +30,6 @@ Linked undo allows the user to simultaneously undo the same edits in multiple fi
   
 ## See also  
  <xref:Microsoft.VisualStudio.TextManager.Interop.IVsCompoundAction>   
- [IOleParentUndoUnit](http://msdn.microsoft.com/library/windows/desktop/ms682151)   
- [IOleUndoUnit](http://msdn.microsoft.com/library/windows/desktop/ms678476)   
+ [IOleParentUndoUnit](/windows/desktop/api/ocidl/nn-ocidl-ioleparentundounit)   
+ [IOleUndoUnit](/windows/desktop/api/ocidl/nn-ocidl-ioleundounit)   
  [How to: Implement undo management](../extensibility/how-to-implement-undo-management.md)

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)