MicrosoftDocs · ghogen · Feb 19, 2020 · Feb 18, 2020 · Feb 18, 2020 · Feb 19, 2020
diff --git a/docs/code-quality/ca1034.md b/docs/code-quality/ca1034.md
@@ -45,7 +45,7 @@ Protected types can be used in subclasses and nested types in advance customizat
 If you do not intend the nested type to be externally visible, change the type's accessibility. Otherwise, remove the nested type from its parent. If the purpose of the nesting is to categorize the nested type, use a namespace to create the hierarchy instead.
 
 ## When to suppress warnings
-Do not suppress a warning from this rule.
+Do not suppress a warning from this rule. The warning may be suppressed when a nested type follows the builder pattern.
 
 ## Example
 The following example shows a type that violates the rule.

diff --git a/docs/extensibility/debugger/reference/idebugengine3-setsymbolpath.md b/docs/extensibility/debugger/reference/idebugengine3-setsymbolpath.md
@@ -57,7 +57,7 @@ int SetSymbolPath(
  The symbol path can also contain one or more cache locations. Caches are listed in priority order, with the highest priority cache first, and separated by * symbols. For example:
 
 ```
-\\symbols\symbols;\\someotherserver\symbols;c:\symbols\httpsymbols*http://msdl.microsoft.com
+\\symbols\symbols;\\someotherserver\symbols;c:\symbols\httpsymbols*https://msdl.microsoft.com
 ```
 
  The [LoadSymbols](../../../extensibility/debugger/reference/idebugengine3-loadsymbols.md) method performs the actual load of the symbols.

diff --git a/docs/extensibility/troubleshooting-vspackages.md b/docs/extensibility/troubleshooting-vspackages.md
@@ -93,7 +93,7 @@ Following are common problems that you might have with your VSPackage and tips t
 
     2. Add this **Symbol file (.pdb) location**:
 
-         [http://msdl.microsoft.com/download/symbols](http://msdl.microsoft.com/download/symbols)
+         `https://msdl.microsoft.com/download/symbols`
 
     3. To improve performance, specify a symbol cache folder, for example:
 

diff --git a/docs/install/install-and-use-visual-studio-behind-a-firewall-or-proxy-server.md b/docs/install/install-and-use-visual-studio-behind-a-firewall-or-proxy-server.md
@@ -129,7 +129,7 @@ To make sure that you have access to everything you want when you use Visual Stu
 | Visual Studio Online | \*.online.visualstudio.com | https | 443 | Used to call Visual Studio Online APIs |
 | JavaScript Automatic Type Acquisition | registry.npmjs.org | https | 443 | Used to install TypeScript type definitions to provide Intellisense for popular JavaScript libraries |
 | Visual Studio Subscriptions Licensing Service | app.vssps.visualstudio.com/apis/Licensing/ClientRights | https | 443 | Licensing for online activation |
-| Debugger | 1. <br>vsdebugger.blob.core.windows.net <br>vsdebugger.azureedge.net <br><br>2. <br>download.visualstudio.com/\*/onecore.msvsmon.\*.zip<br><br> 3. referencesource.microsoft.com/symbols <br><br> 4. <br>symbols.nuget.org/download/symbols<br><br> 5. visualstudio.commsdl.microsoft.com/download/symbols | https | 443 | 1. <br>Used for downloading debugger bits for .NET Core debugging on Unix / MacOS over SSH <br><br>2. <br>Used for downloading debugger bits for remote Windows Docker container debugging<br><br> 3. Used for .NET framework source stepping <br><br> 4. <br>(If user opts-in) Used for downloading symbols published to nuget.org symbol server.<br><br> 5. (If user opts-in) Used for downloading MS symbols and binaries, might also be needed for debugging managed code in dumps |
+| Debugger | 1. <br>vsdebugger.blob.core.windows.net <br>vsdebugger.azureedge.net <br><br>2. <br>download.visualstudio.com/\*/onecore.msvsmon.\*.zip<br><br> 3. referencesource.microsoft.com/symbols <br><br> 4. <br>symbols.nuget.org/download/symbols<br><br> 5. visualstudio.com<br><br>6. msdl.microsoft.com/download/symbols | https | 443 | 1. <br>Used for downloading debugger bits for .NET Core debugging on Unix / MacOS over SSH <br><br>2. <br>Used for downloading debugger bits for remote Windows Docker container debugging<br><br> 3. Used for .NET framework source stepping <br><br> 4. <br>(If user opts-in) Used for downloading symbols published to nuget.org symbol server.<br><br> 5. (If user opts-in) Used for downloading MS symbols and binaries, might also be needed for debugging managed code in dumps |
 | Visual Studio Online| \*.online.visualstudio.com | https | 443 | Used to call Visual Studio Online APIs |
 | Xamarin Android App Publishing | \*.googleapis.com <br/> play.google.com <br/>accounts.google.com | https | 443 | Used to interact with Google Play Store service to publish/upload Xamarin Android Applications directly from Visual Studio. |
 | Azure Container Registry | *.azurecr.io | https | 443 | Access container registries hosted on Azure, for configuration of CICD pipelines |

diff --git a/docs/profiling/how-to-specify-symbol-file-locations-from-the-command-line.md b/docs/profiling/how-to-specify-symbol-file-locations-from-the-command-line.md
@@ -40,17 +40,19 @@ To display symbol information such as function names and line numbers, the VSPer
 
 2. Use the following syntax to set the **_NT_SYMBOL_PATH** environment variable or the VSPerfReport /SymbolPath option:
 
-    **srv\\*** *LocalStore* **\*http://msdl.microsoft.com/download/symbols**
+    `srv*<LocalStore>*https://msdl.microsoft.com/download/symbols`
 
-    where *LocalStore* is the path of the local directory that you created.
+    where *<LocalStore>* is the path of the local directory that you created.
 
 ## Specify component symbol files
  Profiling Tools searches for the.*pdb* files of the components that you want to profile in their original locations that are stored in the components or in the folder that contains the profiling data file. You can specify other locations to search by adding one or more paths to **_NT_SYMBOL_PATH** or to the **/SymbolPath** option. Separate paths with semi-colons.
 
 ## Example
  The following command line sets the **_NT_SYMBOL_PATH** environment variable to the Windows symbol server and the local directory to **C:\Symbols**.
 
- **set  _NT_SYMBOL_PATH=srv\*C:\symbols\*http://msdl.microsoft.com/download/symbols**
+ ```cmd
+  set  _NT_SYMBOL_PATH=srv*C:\symbols*https://msdl.microsoft.com/download/symbols
+ ```
 
  The following VSPerfReport command line adds the *C:\Projects\Symbols* directory to the search path by using the **/SymbolPath** option.
 

diff --git a/...a-tools/customize-how-visual-studio-creates-captions-for-data-bound-controls.md b/...a-tools/customize-how-visual-studio-creates-captions-for-data-bound-controls.md
@@ -49,8 +49,6 @@ When you drag items from the [Data Sources Window](https://msdn.microsoft.com/li
 
 > [!CAUTION]
 > You should be very careful when doing anything in the Registry Editor. Back up the registry before editing it. If you use the Registry Editor incorrectly, you can cause serious problems that may require you to reinstall your operating system. Microsoft does not guarantee that problems that you cause by using the Registry Editor incorrectly can be resolved. Use the Registry Editor at your own risk.
->
-> The following KnowledgeBase article contains instructions for backing up, editing, and restoring the registry: [Description of the Microsoft Windows registry](http://support.microsoft.com/default.aspx?scid=kb;en-us;256986) (http://support.microsoft.com/default.aspx?scid=kb;en-us;256986)
 
 ### To modify the smart captioning behavior of the Data Sources window
 

diff --git a/...s-2015/debugger/how-can-i-find-out-if-my-pointers-corrupt-a-memory-address-q.md b/...s-2015/debugger/how-can-i-find-out-if-my-pointers-corrupt-a-memory-address-q.md
@@ -33,7 +33,7 @@ Problem Description
 
 #### Check for heap corruption  
 
-- Most memory corruption is actually due to heap corruption. Try using the Global Flags Utility (gflags.exe) or pageheap.exe. See [http://support.microsoft.com/default.aspx?scid=kb;en-us;286470](http://support.microsoft.com/default.aspx?scid=kb;en-us;286470).  
+- Most memory corruption is actually due to heap corruption. Try using the Global Flags Utility (gflags.exe) or pageheap.exe. See [GFlags and PageHeap](/windows-hardware/drivers/debugger/gflags-and-pageheap) and [How to use the PageHeap utility to detect memory errors in a Microsoft Visual C++ project](https://support.microsoft.com/help/264471/how-to-use-the-pageheap-utility-to-detect-memory-errors-in-a-microsoft).
 
 #### To find where the memory address is modified  
 

diff --git a/docs/vs-2015/debugger/how-to-enable-debugging-for-aspnet-applications.md b/docs/vs-2015/debugger/how-to-enable-debugging-for-aspnet-applications.md
@@ -25,7 +25,7 @@ manager: jillfra
 To enable debugging, you must enable it in both the **Project Properties** page and in the application's web.config file.  
 
 > [!NOTE]  
-> The dialog boxes and menu commands you see might differ from those described in Help depending on your active settings or edition. To change your settings, choose **Import and Export Settings** on the **Tools** menu. For more information, see [Customizing Development Settings in Visual Studio](https://msdn.microsoft.com/library/22c4debb-4e31-47a8-8f19-16f328d7dcd3).  
+> The dialog boxes and menu commands you see might differ from those described in Help depending on your active settings or edition. To change your settings, choose **Import and Export Settings** on the **Tools** menu. For more information, see [Customizing Development Settings in Visual Studio](/previous-versions/zbhkx167(v=vs.140)).  
 
 ### To enable ASP.NET debugging in the project properties (Visual Basic/C#)  
 
@@ -77,7 +77,7 @@ The web.config file should look like the following example. Note that there can
 
 A Web site can contain multiple virtual directories and subdirectories, and Web.config files may exist in each one. [!INCLUDE[vstecasp](../includes/vstecasp-md.md)] applications inherit settings from Web.config files at higher levels in the URL path. Hierarchical configuration files allow you to change settings for several [!INCLUDE[vstecasp](../includes/vstecasp-md.md)] applications at the same time, such as for all applications below it in the hierarchy. However, if `debug` is set in a file lower in the hierarchy, it will override the higher value.  
 
-For example, you could specify `debug="true"` in www.microsoft.com/aaa/Web.config, and any application in the aaa folder or in any subfolder of aaa will inherit that setting. So if your [!INCLUDE[vstecasp](../includes/vstecasp-md.md)] application is at www.microsoft.com/aaa/bbb, it will inherit that setting, as will any [!INCLUDE[vstecasp](../includes/vstecasp-md.md)] applications in www.microsoft.com/aaa/ccc, www.microsoft.com/aaa/ddd, and so on. The only exception is if one of those applications overrides the setting by means of its own lower Web.config file.  
+For example, you could specify `debug="true"` in `www.microsoft.com/aaa/Web.config`, and any application in the aaa folder or in any subfolder of aaa will inherit that setting. So if your [!INCLUDE[vstecasp](../includes/vstecasp-md.md)] application is at `www.microsoft.com/aaa/bbb`, it will inherit that setting, as will any [!INCLUDE[vstecasp](../includes/vstecasp-md.md)] applications in `www.microsoft.com/aaa/ccc`, `www.microsoft.com/aaa/ddd`, and so on. The only exception is if one of those applications overrides the setting by means of its own lower Web.config file.  
 
 Enabling debug mode will greatly affect the performance of your [!INCLUDE[vstecasp](../includes/vstecasp-md.md)] application. Remember to disable debug mode before you deploy a release application or conduct performance measurements.  
 

diff --git a/docs/vs-2015/debugger/limitations-on-script-debugging.md b/docs/vs-2015/debugger/limitations-on-script-debugging.md
@@ -29,7 +29,7 @@ manager: jillfra
 
 - Breakpoints must be set inside `<script>` blocks. Breakpoints in inline script or `<% %>` blocks cannot be mapped.  
 
-- The browser URL for the page must contain the page name. For example, http://microsoft.com/default.apsx. Breakpoint mapping cannot recognize a redirection from an address such as http://microsoft.com to the default page.  
+- The browser URL for the page must contain the page name. For example, `http://microsoft.com/default.apsx`. Breakpoint mapping cannot recognize a redirection from an address such as `http://microsoft.com` to the default page.  
 
 - The breakpoint must be set in the page specified in the browser URL, not in an ASPX control (ascx) file, Master page, or other file included by that page. Breakpoints set in included pages cannot be mapped.  
 

diff --git a/...er/unable-to-connect-to-the-microsoft-visual-studio-remote-debugging-monitor.md b/...er/unable-to-connect-to-the-microsoft-visual-studio-remote-debugging-monitor.md
@@ -23,7 +23,7 @@ manager: jillfra
 This error message appears when you enter an invalid Visual Studio Remote Debugging Monitor name in the **Attach to Process** dialog box. The Remote Debugging Monitor name is usually the same as the machine you are attempting to connect to for remote debugging. This message may occur because the remote machine does not exist on the network, the remote debugging monitor is not properly set up on the remote machine, or the remote machine is inaccessible due to network problems or the presence of a firewall.  
 
 > [!IMPORTANT]
-> If you believe you have received this message because of a product bug, please report this issue to Visual Studio [Send a Smile](https://msdn.microsoft.com/library/5cc9b67a-54d0-41b0-aa8f-80dff4475a6b). If you need more help, see [Talk to Us](../ide/talk-to-us.md) for ways to contact Microsoft.  
+> If you need more help, see [Talk to Us](../ide/talk-to-us.md) for ways to contact Microsoft.  
 
 ## I got this message while I was debugging locally  
  If you are getting this message while you are debugging locally, your anti-virus software or a third-party firewall may be to blame. Visual Studio is a 32-bit application, so it uses the 64-bit version of the remote debugger to debug 64-bit applications. The two processes communicate using the local network within the local computer. No network traffic leaves the computer, but it is possible that third party security software may block the communication.  
@@ -42,9 +42,10 @@ This error message appears when you enter an invalid Visual Studio Remote Debugg
  Try to [ping](https://technet.microsoft.com/library/ee624059\(v=ws.10\).aspx) the remote machine. If it doesn’t reply to the ping, the remote tools won’t be able to connect either. Try rebooting the remote machine and otherwise making sure that it is correctly configured on the network.  
 
 ## The version of the remote debugger doesn’t match the version of Visual Studio  
- The version of Visual Studio that you are running locally needs to match the version of the remote debugging monitor that is running on the remote machine. To fix this, download and install the matching version of the remote debugging monitor. Go to the [Download Center](http://www.microsoft.com/download) to find the right version of the remote debugger.  
-  
+ The version of Visual Studio that you are running locally needs to match the version of the remote debugging monitor that is running on the remote machine. To fix this, download and install the matching version of the remote debugging monitor. Go to [Visual Studio subscriptions](https://my.visualstudio.com/Downloads?q=remote%20tools%20visual%20studio%202015) to find the right version of the remote debugger for your version of Visual Studio.
+
 ## The local and remote machines have different authentication modes  
+
  The local and remote machines need to use the same authentication mode. To fix this, make sure that both machines are using the same authentication mode. You can change the authentication mode on the remote debugger in the **Tools / Options** dialog.  
 
  For more information about authentication modes, see [Windows Authentication Overview](https://technet.microsoft.com/library/hh831472.aspx).  

diff --git a/...015/deployment/how-to-specify-the-location-where-end-users-will-install-from.md b/...015/deployment/how-to-specify-the-location-where-end-users-will-install-from.md
@@ -36,7 +36,7 @@ When publishing a [!INCLUDE[ndptecclick](../includes/ndptecclick-md.md)] applica
 
 2. Click the **Publish** tab.  
 
-3. In the Installation URL field, enter the installation location using a fully qualified URL using the format http://www.microsoft.com/ApplicationName, or a UNC path using the format \\\Server\ApplicationName.  
+3. In the Installation URL field, enter the installation location using a fully qualified URL using the format https://www.microsoft.com/ApplicationName, or a UNC path using the format \\\Server\ApplicationName.  
 
 ## See Also  
  [How to: Specify Where Visual Studio Copies the Files](../deployment/how-to-specify-where-visual-studio-copies-the-files.md)   

diff --git a/docs/vs-2015/extensibility/commandtable-element.md b/docs/vs-2015/extensibility/commandtable-element.md
@@ -21,7 +21,7 @@ CommandTable is the root element of the .vsct file. This is the file that define
 
 ## Syntax  
 
-```  
+```xml  
 <CommandTable xmlns="http://schemas.microsoft.com/VisualStudio/2005-10-18/CommandTable" xmlns:xs="http://www.w3.org/2001/XMLSchema" >  
   <Extern>... </Extern>  
   <Include>... </Include>  
@@ -42,7 +42,7 @@ CommandTable is the root element of the .vsct file. This is the file that define
 
 | Attribute |                                                                                                                   Description                                                                                                                   |
 |-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-|   xmlns   |                                   Required. XML namespaces:<br /><br /> xmlns="<http://schemas.microsoft.com/VisualStudio/2005-10-18/CommandTable>"<br /><br /> xmlns:xs="<http://www.w3.org/2001/XMLSchema>"                                   |
+|   xmlns   |                                   Required. XML namespaces:<br /><br /> `xmlns="<http://schemas.microsoft.com/VisualStudio/2005-10-18/CommandTable>"`<br /><br /> `xmlns:xs="<http://www.w3.org/2001/XMLSchema>"`                                   |
 | language  | Optional. The language attribute may be used to specify the default language of all \<Strings> elements in the command table.  If the language is not specified, the language of the current process will be used:<br /><br /> language="en-us" |
 
 ### Child Elements  

diff --git a/docs/vs-2015/extensibility/debugger/reference/idebugengine3-setsymbolpath.md b/docs/vs-2015/extensibility/debugger/reference/idebugengine3-setsymbolpath.md
@@ -53,7 +53,7 @@ int SetSymbolPath(
  The symbol path can also contain one or more cache locations. Caches are listed in priority order, with the highest priority cache first, and separated by * symbols. For example:  
 
 ```  
-\\symbols\symbols;\\someotherserver\symbols;c:\symbols\httpsymbols*http://msdl.microsoft.com  
+\\symbols\symbols;\\someotherserver\symbols;c:\symbols\httpsymbols*https://msdl.microsoft.com  
 ```  
 
  The [LoadSymbols](../../../extensibility/debugger/reference/idebugengine3-loadsymbols.md) method performs the actual load of the symbols.  

diff --git a/docs/vs-2015/extensibility/license-element-vsix-language-pack-schema.md b/docs/vs-2015/extensibility/license-element-vsix-language-pack-schema.md
@@ -51,12 +51,12 @@ Optional. The path of a localized version of the license file for the extension.
 
 |                 |                                                           |
 |-----------------|-----------------------------------------------------------|
-|    Namespace    | http://schemas.microsoft.com/developer/vsx-schema-lp/2010 |
+|    Namespace    | `http://schemas.microsoft.com/developer/vsx-schema-lp/2010` |
 |   Schema Name   |                 VSIX Language Pack Schema                 |
 | Validation File |                VSIXLanguagePackSchema.xsd                 |
 |  Can be Empty   |                      Not applicable                       |
 
 ## See Also  
  [VSX Language Pack Schema Reference](../extensibility/vsx-language-pack-schema-reference.md)   
  [Localizing VSIX Packages](../extensibility/localizing-vsix-packages.md)   
- [VSIX Extension Schema 1.0 Reference](https://msdn.microsoft.com/76e410ec-b1fb-4652-ac98-4a4c52e09a2b)
+ [VSIX Extension Schema 1.0 Reference](/previous-versions/dd393700(v=vs.110))
diff --git a/...vs-2015/extensibility/localizeddescription-element-vsix-language-pack-schema.md b/...vs-2015/extensibility/localizeddescription-element-vsix-language-pack-schema.md
@@ -48,12 +48,12 @@ Required. Provides a localized description of the extension.
 
 |                 |                                                           |
 |-----------------|-----------------------------------------------------------|
-|    Namespace    | http://schemas.microsoft.com/developer/vsx-schema-lp/2010 |
+|    Namespace    | `http://schemas.microsoft.com/developer/vsx-schema-lp/2010` |
 |   Schema Name   |                 VSIX Language Pack Schema                 |
 | Validation File |                VSIXLanguagePackSchema.xsd                 |
 |  Can be Empty   |                      Not applicable                       |
 
 ## See Also  
  [VSX Language Pack Schema Reference](../extensibility/vsx-language-pack-schema-reference.md)   
  [Localizing VSIX Packages](../extensibility/localizing-vsix-packages.md)   
- [VSIX Extension Schema 1.0 Reference](https://msdn.microsoft.com/76e410ec-b1fb-4652-ac98-4a4c52e09a2b)
+ [VSIX Extension Schema 1.0 Reference](/previous-versions/dd393700(v=vs.110))