Merge branch 'master' of https://github.com/MicrosoftDocs/visualstudio-docs-pr into mikejo-157p1

Author: Mikejo5000

.openpublishing.publish.config.json

@@ -38,6 +38,7 @@
       "build_source_folder": "docs",
       "build_output_subfolder": "vsdocsdocs",
       "locale": "en-us",
+      "xref_query_tags": ["/dotnet"],
       "monikers": [],
       "open_to_public_contributors": true,
       "type_mapping": {

.openpublishing.redirection.json

@@ -1159,7 +1159,7 @@
         },
         {
             "source_path": "docs/install/install-visual-studio-in-offline-environment.md",
-            "redirect_url": "/visualstudio/install/install-certificates-for-visual-studio-offline",
+            "redirect_url": "/visualstudio/install/create-an-offline-installation-of-visual-studio",
             "redirect_document_id": false
         },
         {
@@ -1842,6 +1842,11 @@
             "redirect_url": "/visualstudio/test/unit-test-your-code",
             "redirect_document_id": false
         },
+        {
+            "source_path": "docs/test/lab-management/upgrade-scvmm-2008-r2-scvmm-2012.md",
+            "redirect_url": "/visualstudio/test/lab-management/using-a-lab-environment-for-your-application-lifecycle",
+            "redirect_document_id": false
+        },
         {
             "source_path": "docs/test/using-microsoft-visualstudio-testtools-cppunittestframework.md",
             "redirect_url": "/visualstudio/test/microsoft.visualstudio.testtools.cppunittestframework-api-reference",
@@ -1852,6 +1857,11 @@
             "redirect_url": "/visualstudio/test/writing-unit-tests-for-c-cpp",
             "redirect_document_id": false
         },
+        {
+            "source_path": "docs/test/writing-unit-tests-for-the-dotnet-framework-with-the-microsoft-unit-test-framework-for-managed-code.md",
+            "redirect_url": "/visualstudio/test/unit-test-your-code",
+            "redirect_document_id": false
+        },
         {
             "source_path": "docs/vb-ide/code-generation-vb.md",
             "redirect_url": "/visualstudio/ide/code-generation-in-visual-studio",
@@ -2117,6 +2127,11 @@
           "source_path": "docs/install/install-visual-studio-behind-a-firewall-or-proxy-server.md",
           "redirect_url": "/visualstudio/install/install-and-use-visual-studio-behind-a-firewall-or-proxy-server",
           "redirect_document_id": false
+        },
+        {
+          "source_path": "docs/ide/quickstart-visual-basic-winforms.md",
+          "redirect_url": "/visualstudio/ide/create-a-visual-basic-winform-in-visual-studio",
+          "redirect_document_id": false
         }
     ]
 }

docs/TOC.md

@@ -83,8 +83,7 @@
 #### [Manage Assembly and Manifest Signing](ide/managing-assembly-and-manifest-signing.md)
 ##### [Sign Application and Deployment Manifests](ide/how-to-sign-application-and-deployment-manifests.md)
 #### [Specify an Application Icon (Visual Basic, C#)](ide/how-to-specify-an-application-icon-visual-basic-csharp.md)
-#### [Target a Specific .NET Framework Version](ide/targeting-a-specific-dotnet-framework-version.md)
-##### [Multi-Targeting Overview](ide/visual-studio-multi-targeting-overview.md)
+#### [Multi-Targeting Overview](ide/visual-studio-multi-targeting-overview.md)
 ##### [Target a Version of the .NET Framework](ide/how-to-target-a-version-of-the-dotnet-framework.md)
 #### [Create Project and Item Templates](ide/creating-project-and-item-templates.md)
 ##### [Create Project Templates](ide/how-to-create-project-templates.md)

docs/code-quality/automatic-feature-suspension.md

@@ -1,64 +1,64 @@
 ---
-title: "Automatic feature suspension | Microsoft Docs"
-ms.custom: ""
+title: "Automatic feature suspension in Visual Studio | Microsoft Docs"
 ms.date: "11/04/2016"
-ms.reviewer: ""
-ms.suite: ""
-ms.tgt_pltfrm: ""
 ms.topic: "article"
-helpviewer_keywords: 
+helpviewer_keywords:
   - "full solution analysis"
   - "performance"
   - "low-memory"
 ms.assetid: 572c15aa-1fd0-468c-b6be-9fa50e170914
-caps.latest.revision: 6
 author: "gewarren"
 ms.author: "gewarren"
 manager: ghogen
-ms.technology: 
-  - "vs-ide-code-analysis"
-ms.workload: 
+ms.technology: vs-ide-code-analysis
+ms.workload:
   - "multiple"
 ---
 # Automatic feature suspension
-If your available system memory falls to 200MB or less, Visual Studio displays the following message in the code editor.  
-  
- ![Alert text suspending full solution analysis](../code-quality/media/fsa_alert.png "FSA_Alert")  
-  
- When Visual Studio detects a low memory condition, it automatically suspends certain advanced features to help it remain stable. When this advanced feature suspension warning appears, Visual Studio will continue to work as before, but its performance will be slightly degraded.  
-  
- In a low memory condition, the following occurs:  
-  
--   Full solution analysis for Visual C# and Visual Basic is disabled.  
-  
--   [Garbage Collection](/dotnet/standard/garbage-collection/index) (GC) low-latency mode for Visual C# and Visual Basic are disabled.  
-  
--   Visual Studio caches are flushed.  
-  
-## Improve Visual Studio performance  
- For tips and tricks on how to improve Visual Studio performance when dealing with large solutions or low-memory conditions, see [Performance considerations for large solutions](https://github.com/dotnet/roslyn/wiki/Performance-considerations-for-large-solutions).  
-  
-## Full solution analysis suspended  
- By default, full solution analysis is enabled for Visual Basic and disabled for Visual C#. However, in a low memory condition, full solution analysis is automatically disabled for both Visual Basic and Visual C#, regardless of their settings in the Options dialog box. However, you can re-enable full solution analysis by choosing the **Re-enable** button in the info bar when it appears, by selecting the **Enable full solution analysis** check box in the Options dialog, or by restarting Visual Studio. The Options dialog box always shows the current full solution analysis settings. For more information, see [How to: Enable and Disable Full Solution Analysis](../code-quality/how-to-enable-and-disable-full-solution-analysis-for-managed-code.md).  
-  
-## GC low-latency disabled  
- To re-enable GC low-latency mode, restart Visual Studio.  By default, Visual Studio enables GC  low-latency mode whenever you are typing to ensure that your typing doesn't block any GC operations. However, if a low memory condition causes Visual Studio to display the automatic suspension warning, GC low-latency mode is disabled for that session. Restarting Visual Studio will re-enable the default GC behavior. For more information, see [GCLatencyMode Enumeration](http://msdn.microsoft.com/Library/057757a5-cd62-4d13-8a40-370eb7f47c87).  
-  
-## Visual Studio caches flushed  
- All Visual Studio caches are immediately emptied, but will begin to repopulate if you continue your current development session or restart Visual Studio. The caches flushed include caches for the following features.  
-  
--   Find all references  
-  
--   Navigate To  
-  
--   Add Using  
-  
- In addition, caches used for internal Visual Studio operations are also cleared.  
-  
+
+If your available system memory falls to 200 MB or less, Visual Studio displays the following message in the code editor:
+
+![Alert text suspending full solution analysis](../code-quality/media/fsa_alert.png)
+
+When Visual Studio detects a low memory condition, it automatically suspends certain advanced features to help it remain stable. Visual Studio continues to work as before, but its performance is degraded.
+
+In a low memory condition, the following actions take place:
+
+- Full solution analysis for Visual C# and Visual Basic is disabled.
+
+- [Garbage Collection](/dotnet/standard/garbage-collection/index) (GC) low-latency mode for Visual C# and Visual Basic is disabled.
+
+- Visual Studio caches are flushed.
+
+## Improve Visual Studio performance
+
+For tips and tricks on how to improve Visual Studio performance when dealing with large solutions or low-memory conditions, see [Performance considerations for large solutions](https://github.com/dotnet/roslyn/wiki/Performance-considerations-for-large-solutions).
+
+## Full solution analysis suspended
+
+By default, full solution analysis is enabled for Visual Basic and disabled for Visual C#. However, in a low memory condition, full solution analysis is automatically disabled for both Visual Basic and Visual C#, regardless of their settings in the Options dialog box. However, you can re-enable full solution analysis by choosing the **Re-enable** button in the info bar when it appears, by selecting the **Enable full solution analysis** check box in the Options dialog, or by restarting Visual Studio. The Options dialog box always shows the current full solution analysis settings. For more information, see [How to: Enable and Disable Full Solution Analysis](../code-quality/how-to-enable-and-disable-full-solution-analysis-for-managed-code.md).
+
+## GC low-latency disabled
+
+To re-enable GC low-latency mode, restart Visual Studio. By default, Visual Studio enables GC  low-latency mode whenever you are typing to ensure that your typing doesn't block any GC operations. However, if a low memory condition causes Visual Studio to display the automatic suspension warning, GC low-latency mode is disabled for that session. Restarting Visual Studio re-enables the default GC behavior. For more information, see <xref:System.Runtime.GCLatencyMode>.
+
+## Visual Studio caches flushed
+
+If you continue your current development session or restart Visual Studio, all Visual Studio caches are immediately emptied, but begin to repopulate. The caches flushed include caches for the following features:
+
+- Find all references
+
+- Navigate To
+
+- Add Using
+
+In addition, caches used for internal Visual Studio operations are also cleared.
+
 > [!NOTE]
->  The automatic feature suspension warning occurs only once on a per-solution basis, not on a per-session basis. This means that if you switch from Visual Basic to Visual C# (or vice-versa) and run into another low memory condition, you can possibly get another automatic feature suspension warning.  
-  
-## See Also  
- [How to: Enable and Disable Full Solution Analysis](../code-quality/how-to-enable-and-disable-full-solution-analysis-for-managed-code.md)   
- [Fundamentals of Garbage Collection](/dotnet/standard/garbage-collection/fundamentals)   
- [Performance considerations for large solutions](https://github.com/dotnet/roslyn/wiki/Performance-considerations-for-large-solutions)
+> The automatic feature suspension warning occurs only once on a per-solution basis, not on a per-session basis. This means that if you switch from Visual Basic to Visual C# (or vice-versa) and run into another low memory condition, you can possibly get another automatic feature suspension warning.
+
+## See also
+
+- [How to: Enable and Disable Full Solution Analysis](../code-quality/how-to-enable-and-disable-full-solution-analysis-for-managed-code.md)
+- [Fundamentals of Garbage Collection](/dotnet/standard/garbage-collection/fundamentals)
+- [Performance considerations for large solutions](https://github.com/dotnet/roslyn/wiki/Performance-considerations-for-large-solutions)

docs/code-quality/ca1064-exceptions-should-be-public.md

@@ -36,7 +36,7 @@ ms.workload:
 ## Rule Description  
  An internal exception is only visible inside its own internal scope. After the exception falls outside the internal scope, only the base exception can be used to catch the exception. If the internal exception is inherited from <xref:System.Exception>, <xref:System.SystemException>, or <xref:System.ApplicationException>, the external code will not have sufficient information to know what to do with the exception.  
 
- But, if the code has a public exception that later is used as the base for a internal exception, it is reasonable to assume the code further out will be able to do something intelligent with the base exception. The public exception will have more information than what is provided by T:System.Exception, T:System.SystemException, or T:System.ApplicationException.  
+ But, if the code has a public exception that later is used as the base for a internal exception, it is reasonable to assume the code further out will be able to do something intelligent with the base exception. The public exception will have more information than what is provided by <xref:System.Exception>, <xref:System.SystemException>, or <xref:System.ApplicationException>.  
 
 ## How to Fix Violations  
  Make the exception public, or derive the internal exception from a public exception that is not <xref:System.Exception>, <xref:System.SystemException>, or <xref:System.ApplicationException>.  
@@ -47,4 +47,4 @@ ms.workload:
 ## Example  
  This rule fires on the first example method, FirstCustomException because the exception class derives directly from Exception and is internal. The rule does not fire on the SecondCustomException class because although the class also derives directly from Exception, the class is declared public. The third class also does not fire the rule because it does not derive directly from <xref:System.Exception?displayProperty=fullName>, <xref:System.SystemException?displayProperty=fullName>, or <xref:System.ApplicationException?displayProperty=fullName>.  
 
- [!code-csharp[FxCop.Design.ExceptionsShouldBePublic.CA1064#1](../code-quality/codesnippet/CSharp/ca1064-exceptions-should-be-public_1.cs)]
+ [!code-csharp[FxCop.Design.ExceptionsShouldBePublic.CA1064#1](../code-quality/codesnippet/CSharp/ca1064-exceptions-should-be-public_1.cs)]