Merge pull request #2062 from corob-msft/cr-https-mostly

Bulk update all http links to https, where supported.

Author: tfosmark

docs/assembler/arm/arm-assembler-diagnostic-messages.md

@@ -17,7 +17,7 @@ The Microsoft ARM assembler (*armasm*) emits diagnostic warnings and errors when
 
 > A2193: this instruction generates unpredictable behavior
 
-The ARM architecture cannot guarantee what happens when this instruction is executed.  For details about the well-defined forms of this instruction, consult the [ARM Architecture Reference Manual](http://go.microsoft.com/fwlink/p/?linkid=246464).
+The ARM architecture cannot guarantee what happens when this instruction is executed.  For details about the well-defined forms of this instruction, consult the [ARM Architecture Reference Manual](https://go.microsoft.com/fwlink/p/?linkid=246464).
 
 ```asm
     ADD r0, r8, pc         ; A2193: this instruction generates unpredictable behavior
@@ -93,7 +93,7 @@ In ARM mode, there is an alternate syntax for specifying constants.  Instead of
 
 > A4509: This form of conditional instruction is deprecated
 
-This form of conditional instruction has been deprecated by ARM in the ARMv8 architecture. We recommend that you change the code to use conditional branches. To see which conditional instructions are still supported, consult the [ARM Architecture Reference Manual](http://go.microsoft.com/fwlink/p/?linkid=246464).
+This form of conditional instruction has been deprecated by ARM in the ARMv8 architecture. We recommend that you change the code to use conditional branches. To see which conditional instructions are still supported, consult the [ARM Architecture Reference Manual](https://go.microsoft.com/fwlink/p/?linkid=246464).
 
 This warning is not emitted when the **-oldit** command-line switch is used.
 

docs/build/arm-exception-handling.md

@@ -15,7 +15,7 @@ The ARM EABI (embedded application binary interface) specifies an exception unwi
 
 ### Assumptions
 
-Executable images for Windows on ARM use the Portable Executable (PE) format. For more information, see [Microsoft PE and COFF Specification](http://go.microsoft.com/fwlink/p/?linkid=84140). Exception handling information is stored in the .pdata and .xdata sections of the image.
+Executable images for Windows on ARM use the Portable Executable (PE) format. For more information, see [Microsoft PE and COFF Specification](https://go.microsoft.com/fwlink/p/?linkid=84140). Exception handling information is stored in the .pdata and .xdata sections of the image.
 
 The exception handling mechanism makes certain assumptions about code that follows the ABI for Windows on ARM:
 

docs/build/reference/hlsl-property-pages.md

@@ -20,10 +20,10 @@ You can use the HLSL compiler (fxc.exe) property pages to configure how individu
 
    Provides properties to specify how files are output by the HLSL compiler.
 
-You can specify command-line arguments to the HLSL compiler by using the **Additional Options** property of the **Command Line** property page; this includes arguments that can't be configured by using other properties of the HLSL property pages. For information about the HLSL compiler, see [Effect-Compiler Tool](http://go.microsoft.com/fwlink/p/?LinkID=258285&clcid=0x409)
+You can specify command-line arguments to the HLSL compiler by using the **Additional Options** property of the **Command Line** property page; this includes arguments that can't be configured by using other properties of the HLSL property pages. For information about the HLSL compiler, see [Effect-Compiler Tool](https://go.microsoft.com/fwlink/p/?LinkID=258285&clcid=0x409)
 
 ## See also
 
 [C++ project property page reference](property-pages-visual-cpp.md)<br>
 [Command Line Property Pages](command-line-property-pages.md)<br>
-[Compiling Shaders](http://go.microsoft.com/fwlink/p/?LinkID=258284&clcid=0x409)
+[Compiling Shaders](https://go.microsoft.com/fwlink/p/?LinkID=258284&clcid=0x409)

docs/cppcx/codesnippet/CPP/clientapp/app.xaml.cpp

@@ -22,7 +22,7 @@ using namespace Windows::UI::Xaml::Interop;
 using namespace Windows::UI::Xaml::Media;
 using namespace Windows::UI::Xaml::Navigation;
 
-// The Blank Application template is documented at http://go.microsoft.com/fwlink/p/?linkid=234227
+// The Blank Application template is documented at https://go.microsoft.com/fwlink/p/?linkid=234227
 
 /// <summary>
 /// Initializes the singleton application object.  This is the first line of authored code

docs/cppcx/codesnippet/CPP/clientapp/mainpage.xaml.cpp

@@ -22,7 +22,7 @@ using namespace Windows::UI::Xaml::Navigation;
 
 using namespace DelegatesEvents;
 
-// The Blank Page item template is documented at http://go.microsoft.com/fwlink/p/?linkid=234238
+// The Blank Page item template is documented at https://go.microsoft.com/fwlink/p/?linkid=234238
 
 MainPage::MainPage()
 {

docs/cppcx/codesnippet/CPP/eventsupportinvs/app.xaml.cpp

@@ -22,7 +22,7 @@ using namespace Windows::UI::Xaml::Interop;
 using namespace Windows::UI::Xaml::Media;
 using namespace Windows::UI::Xaml::Navigation;
 
-// The Blank Application template is documented at http://go.microsoft.com/fwlink/p/?linkid=234227
+// The Blank Application template is documented at https://go.microsoft.com/fwlink/p/?linkid=234227
 
 /// <summary>
 /// Initializes the singleton application object.  This is the first line of authored code

docs/cppcx/codesnippet/CPP/eventsupportinvs/mainpage.xaml.cpp

@@ -19,7 +19,7 @@ using namespace Windows::UI::Xaml::Input;
 using namespace Windows::UI::Xaml::Media;
 using namespace Windows::UI::Xaml::Navigation;
 
-// The Blank Page item template is documented at http://go.microsoft.com/fwlink/p/?linkid=234238
+// The Blank Page item template is documented at https://go.microsoft.com/fwlink/p/?linkid=234238
 
 MainPage::MainPage()
 {

docs/error-messages/compiler-errors-2/compiler-error-c2659.md

@@ -9,7 +9,7 @@ ms.assetid: b0883600-4d27-4ca7-a931-8ca6bd48654d
 
 'operator' : function as left operand
 
-A function was on the left side of the specified operator. The most common reason for this error is that the compiler has parsed the identifier on the left side of the operator as a function when the developer intended it to be a variable. For more information, see Wikipedia article [Most vexing parse](http://en.wikipedia.org/wiki/Most_vexing_parse). This example shows a function declaration and a variable definition that are easily confused:
+A function was on the left side of the specified operator. The most common reason for this error is that the compiler has parsed the identifier on the left side of the operator as a function when the developer intended it to be a variable. For more information, see Wikipedia article [Most vexing parse](https://en.wikipedia.org/wiki/Most_vexing_parse). This example shows a function declaration and a variable definition that are easily confused:
 
 ```
 // C2659a.cpp

docs/error-messages/compiler-errors-2/compiler-error-c3872.md

@@ -11,7 +11,7 @@ ms.assetid: 519e95be-5641-40cc-894c-da4819506604
 
 The C++ compiler follows the C++11 standard on characters allowed in an identifier. Only certain ranges of characters and universal character names are allowed in an identifier. Additional restrictions apply to the initial character of an identifier. For more information and a list of allowed characters and universal character name ranges, see [Identifiers](../../cpp/identifiers-cpp.md).
 
-The range of characters allowed in an identifier is less restrictive when compiling C++/CLI code. Identifiers in code compiled by using /clr should follow  [Standard ECMA-335: Common Language Infrastructure (CLI)](http://www.ecma-international.org/publications/standards/Ecma-335.htm).
+The range of characters allowed in an identifier is less restrictive when compiling C++/CLI code. Identifiers in code compiled by using /clr should follow  [Standard ECMA-335: Common Language Infrastructure (CLI)](https://www.ecma-international.org/publications/standards/Ecma-335.htm).
 
 The following sample generates C3872:
 

docs/error-messages/compiler-errors-2/compiler-error-c3873.md

@@ -11,7 +11,7 @@ ms.assetid: e68fd3be-2391-492b-ac3f-d2428901b2e9
 
 The C++ compiler follows the C++11 standard on characters allowed in an identifier. Only certain ranges of characters and universal character names are allowed in an identifier. Additional restrictions apply to the initial character of an identifier. For more information and a list of allowed characters and universal character name ranges, see [Identifiers](../../cpp/identifiers-cpp.md).
 
-The range of characters allowed in an identifier is less restrictive when compiling C++/CLI code. Identifiers in code compiled by using /clr should follow  [Standard ECMA-335: Common Language Infrastructure (CLI)](http://www.ecma-international.org/publications/standards/Ecma-335.htm).
+The range of characters allowed in an identifier is less restrictive when compiling C++/CLI code. Identifiers in code compiled by using /clr should follow  [Standard ECMA-335: Common Language Infrastructure (CLI)](https://www.ecma-international.org/publications/standards/Ecma-335.htm).
 
 The following sample generates C3873:
 

docs/error-messages/includes/error-boilerplate.md

@@ -6,6 +6,6 @@ To get help on a particular diagnostic message in Visual Studio, select it in th
 > [!NOTE]
 > Not every Visual Studio error or warning is documented. In many cases, the diagnostic message provides all of the information that's available. If you landed on this page when you used **F1** and you think the error or warning message needs additional explanation, let us know. You can use the feedback buttons on this page to raise a documentation issue on [GitHub](https://github.com/MicrosoftDocs/cpp-docs/issues), or a product issue on the [Developer Community](https://developercommunity.visualstudio.com/spaces/8/index.html) site. You can also send feedback and enter bugs within the IDE. In Visual Studio, go to the menu bar and choose **Help > Send Feedback > Report a Problem**, or submit a suggestion by using **Help > Send Feedback > Send a Suggestion**.
 
-You may find additional assistance for errors and warnings in Microsoft's public forums. Or, search for the error or warning number on the Visual Studio C++ [Developer Community](https://developercommunity.visualstudio.com/spaces/8/index.html) site. You can also search for errors and warnings and ask questions on [Stack Overflow](http://stackoverflow.com/) to find solutions.
+You may find additional assistance for errors and warnings in Microsoft's public forums. Or, search for the error or warning number on the Visual Studio C++ [Developer Community](https://developercommunity.visualstudio.com/spaces/8/index.html) site. You can also search for errors and warnings and ask questions on [Stack Overflow](https://stackoverflow.com/) to find solutions.
 
 For links to additional help and community resources, see [Visual C++ Help and Community](../../overview/visual-cpp-help-and-community.md).

docs/error-messages/tool-errors/linker-tools-error-lnk1104.md

@@ -73,7 +73,7 @@ When you specify individual libraries in the **Additional Dependencies** propert
 
 You may see this error when the path for *filename* expands to more than 260 characters. Change the names or rearrange your directory structure if needed to shorten the paths to the required files.
 
-This error can occur because the file is too large. Libraries or object files more than a gigabyte in size may cause problems for the 32-bit linker. A possible fix for this issue is to use the 64-bit toolset. For more information on how to do this at the command line, see [How to: Enable a 64-Bit Visual C++ Toolset on the Command Line](../../build/how-to-enable-a-64-bit-visual-cpp-toolset-on-the-command-line.md). For information on how to do this in the IDE, see [Using MSBuild with the 64-bit Compiler and Tools](../../build/walkthrough-using-msbuild-to-create-a-visual-cpp-project.md#using-msbuild-to-build-your-project)  and this Stack Overflow post: [How to make Visual Studio use the native amd64 toolchain](http://stackoverflow.com/questions/19820718/how-to-make-visual-studio-use-the-native-amd64-toolchain/23793055).
+This error can occur because the file is too large. Libraries or object files more than a gigabyte in size may cause problems for the 32-bit linker. A possible fix for this issue is to use the 64-bit toolset. For more information on how to do this at the command line, see [How to: Enable a 64-Bit Visual C++ Toolset on the Command Line](../../build/how-to-enable-a-64-bit-visual-cpp-toolset-on-the-command-line.md). For information on how to do this in the IDE, see [Using MSBuild with the 64-bit Compiler and Tools](../../build/walkthrough-using-msbuild-to-create-a-visual-cpp-project.md#using-msbuild-to-build-your-project)  and this Stack Overflow post: [How to make Visual Studio use the native amd64 toolchain](https://stackoverflow.com/questions/19820718/how-to-make-visual-studio-use-the-native-amd64-toolchain/23793055).
 
 This error can occur if you have insufficient file permissions to access *filename*. This can happen if you use an ordinary user account and attempt to access library files in protected system directories, or use files copied from other users that have their original permissions set. To fix this issue, move the file to a writeable project directory. If the file is in a writeable directory but has inaccessible permissions, you can use an Administrator command prompt and run the takeown.exe command to take ownership of the file.
 

docs/error-messages/tool-errors/linker-tools-error-lnk1168.md

@@ -13,10 +13,10 @@ The linker can’t write to `filename`. The file may be in use and its file hand
 
 To fix this issue, verify that the `filename` file handle is not locked, and that you have write permission for the file. If it is an executable, verify that it is not already running.
 
-You can use the Windows SysInternals utilities [Handle](http://technet.microsoft.com/sysinternals/bb896655.aspx) or [Process Explorer](http://technet.microsoft.com/sysinternals/bb896653) to determine which process has a file handle lock on `filename`. You can also use Process Explorer to release locks on open file handles. For information about how to use these utilities, see the Help files that come with them.
+You can use the Windows SysInternals utilities [Handle](/sysinternals/downloads/handle) or [Process Explorer](/sysinternals/downloads/process-explorer) to determine which process has a file handle lock on `filename`. You can also use Process Explorer to release locks on open file handles. For information about how to use these utilities, see the Help files that come with them.
 
 If the file is locked by an anti-virus program, you can fix this issue by excluding your build output directories from automatic scanning by the anti-virus program. Anti-virus scanners are often triggered by the creation of new files in the file system, and they hold locks on the files while the scan proceeds. Consult your anti-virus program documentation for details about how to exclude specific directories from scanning.
 
-If the file is locked by a search indexing service, you can fix this issue by excluding your build output directories from automatic indexing. Consult the documentation for the indexing service for more information. To change the Windows search indexing service, use **Indexing Options** in the Windows **Control Panel**. For more information, see [Improve Windows searches using the index: frequently asked questions](http://windows.microsoft.com/windows/improve-windows-searches-using-index-faq#1TC=windows-7).
+If the file is locked by a search indexing service, you can fix this issue by excluding your build output directories from automatic indexing. Consult the documentation for the indexing service for more information. To change the Windows search indexing service, use **Indexing Options** in the Windows **Control Panel**. For more information, see [Search indexing in Windows 10: FAQ](https://support.microsoft.com/help/4098843/windows-10-search-indexing-faq).
 
 If your executable can’t be overwritten by the build process, it may be locked by File Explorer. If the **Application Experience** service has been disabled, File Explorer may hold on to an executable file handle lock for an extended time. To fix this issue, run **services.msc** and then open the **Properties** dialog box for the **Application Experience** service. Change the **Startup type** from **Disabled** to **Manual**.

docs/error-messages/tool-errors/linker-tools-error-lnk2001.md

@@ -93,5 +93,5 @@ In some cases, the linker can only report the decorated name for a symbol. You c
 
 ## Additional resources
 
-For more information about possible causes and solutions for LNK2001, see the Stack Overflow question [What is an undefined reference/unresolved external symbol error and how do I fix it?](http://stackoverflow.com/q/12573816/2002113).
+For more information about possible causes and solutions for LNK2001, see the Stack Overflow question [What is an undefined reference/unresolved external symbol error and how do I fix it?](https://stackoverflow.com/q/12573816/2002113).
 

docs/error-messages/tool-errors/linker-tools-error-lnk2019.md

@@ -207,5 +207,5 @@ To fix this error, change `unsigned short` to `wchar_t` or `WCHAR`, or compile L
 
 ## Additional resources
 
-For more information about possible causes and solutions for LNK2001, see the Stack Overflow question [What is an undefined reference/unresolved external symbol error and how do I fix it?](http://stackoverflow.com/q/12573816/2002113).
+For more information about possible causes and solutions for LNK2001, see the Stack Overflow question [What is an undefined reference/unresolved external symbol error and how do I fix it?](https://stackoverflow.com/q/12573816/2002113).
 

docs/error-messages/tool-errors/project-build-error-prj0003.md

@@ -13,7 +13,7 @@ The *command line* command formed from input in the **Property Pages** dialog bo
 
 Possible reasons for this error include:
 
-- Your project depends on ATL Server. Beginning in Visual Studio 2008, ATL Server is no longer included as part of Visual Studio, but has been released as a shared-source project at CodePlex. To download the ATL Server source code and tools, go to [ATL Server Library and Tools](http://go.microsoft.com/fwlink/p/?linkid=81979).
+- Your project depends on ATL Server. Beginning in Visual Studio 2008, ATL Server is no longer included as part of Visual Studio, but has been released as a shared-source project at CodePlex. To download the ATL Server source code and tools, go to [ATL Server Library and Tools](https://go.microsoft.com/fwlink/p/?linkid=81979).
 
 - Low system resources. Close some applications to resolve this.
 

docs/extensions/partial-cpp-component-extensions.md

@@ -58,7 +58,7 @@ Templates: A partial class cannot be a template.
 
 Generics: A partial class can be a generic if the full definition could be generic. But every partial and full class must have exactly the same generic parameters, including formal parameter names.
 
-For more information about how to use the **partial** keyword, see [Partial Classes (C++/CX)](http://go.microsoft.com/fwlink/p/?LinkId=249023).
+For more information about how to use the **partial** keyword, see [Partial Classes (C++/CX)](https://go.microsoft.com/fwlink/p/?LinkId=249023).
 
 ### Requirements
 
@@ -70,4 +70,4 @@ Compiler option: `/ZW`
 
 ## See also
 
-[Partial Classes (C++/CX)](http://go.microsoft.com/fwlink/p/?LinkId=249023)
+[Partial Classes (C++/CX)](https://go.microsoft.com/fwlink/p/?LinkId=249023)