Merge pull request #12 from MicrosoftDocs/master

new stuff

Author: WilliamAntonRohm

.gitattributes

@@ -0,0 +1,14 @@
+# Set the default behavior, in case people don't have core.autocrlf set.
+* text=auto
+
+# Explicitly declare text files you want to always be normalized and converted
+# to native line endings on checkout.
+*.c text
+*.h text
+
+# Declare files that will always have CRLF line endings on checkout.
+*.sln text eol=crlf
+
+# Denote all files that are truly binary and should not be modified.
+*.png binary
+*.jpg binary

.openpublishing.publish.config.json

@@ -86,6 +86,9 @@
     }
   ],
   "notification_subscribers": [],
+  "sync_notification_subscribers": [
+    "[email protected]"
+  ],
   "branches_to_filter": [],
   "git_repository_url_open_to_public_contributors": "https://github.com/MicrosoftDocs/visualstudio-docs",
   "git_repository_branch_open_to_public_contributors": "master",
@@ -113,11 +116,7 @@
     ]
   },
   "need_generate_pdf_url_template": true,
-  "targets": {
-    "Pdf": {
-      "template_folder": "_themes.pdf"
-    }
-  },
+  "targets": {},
   "need_generate_pdf": false,
   "need_generate_intellisense": false
-}
+}

.openpublishing.redirection.json

@@ -1092,7 +1092,13 @@
         },
         {
             "source_path": "docs/ide/not-in-toc/web-publish-options.md",
-            "redirect_url": "/visualstudio/deployment/deploying-applications-services-and-components-resources",   "redirect_document_id": false
+            "redirect_url": "/visualstudio/deployment/deploying-applications-services-and-components-resources",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "docs/ide/not-in-toc/intellicode-faq.md",
+            "redirect_url": "/visualstudio/intellicode/faq",
+            "redirect_document_id": false
         },
         {
             "source_path": "docs/ide/optimize-solution-loading-in-visual-studio.md",
@@ -5730,6 +5736,11 @@
             "source_path": "mac/benefits-vsmac-over-xs.md",
             "redirect_url": "/visualstudio/mac/",
             "redirect_document_id": false
+        },
+        {
+            "source_path": "docs/cross-platform/overview-of-visual-studio-tools-for-unity.md",
+            "redirect_url": "/visualstudio/cross-platform/visual-studio-tools-for-unity",
+            "redirect_document_id": false
         }
 
     ]

docs/code-quality/analyzer-rule-sets.md

@@ -0,0 +1,56 @@
+---
+title: Analyzer rule sets
+ms.date: 07/20/2018
+ms.prod: visual-studio-dev15
+ms.technology: vs-ide-code-analysis
+ms.topic: conceptual
+helpviewer_keywords:
+  - "analyzers, rule sets"
+  - "rule sets for analyzers"
+author: gewarren
+ms.author: gewarren
+manager: douge
+ms.workload:
+  - "multiple"
+---
+# Rule sets for Roslyn analyzers
+
+Predefined rule sets are included with some NuGet analyzer packages. For example, the rule sets that are included with the [Microsoft.CodeAnalysis.FxCopAnalyzers NuGet analyzer package](https://www.nuget.org/packages/Microsoft.CodeAnalysis.FxCopAnalyzers/) (starting in version 2.6.2) enable or disable rules based on their category, such as security, naming, or performance. Using rule sets makes it easy to quickly see only those rule violations that pertain to a particular category of rule.
+
+If you're migrating from legacy "FxCop" static code analysis to Roslyn analyzers, these rule sets enable you to continue using the same rule configurations you used previously.
+
+## Use analyzer rule sets
+
+After you [install a NuGet analyzer package](install-roslyn-analyzers.md), locate the predefined rule set in its *rulesets* directory, for example *%USERPROFILE%\\.nuget\packages\microsoft.codequality.analyzers\<version>\rulesets*. From there, you can drag and drop, or copy and paste, one or more of the rulesets to your Visual Studio project in **Solution Explorer**.
+
+To make a rule set the active rule set for analysis, right-click on the project in **Solution Explorer** and choose **Properties**. In the project property pages, select the **Code Analysis** tab. Under **Run this rule set**, select **Browse**, and then select the desired rule set that you copied to the project directory. Now you only see rule violations for those rules that are enabled in the selected rule set.
+
+You can also [customize a predefined rule set](how-to-create-a-custom-rule-set.md#create-a-custom-rule-set) to your preference. For example, you can change the severity of one or more rules so that violations appear as errors or warnings in the **Error List**.
+
+## Available rule sets
+
+The predefined analyzer rule sets include three rulesets that affect all the rules in the package&mdash;one that enables them all, one that disables them all, and one that honors each rule's default severity and enablement settings:
+
+- AllRulesEnabled.ruleset
+- AllRulesDisabled.ruleset
+- AllRulesDefault.ruleset
+
+Additionally, there are two rule sets for each category of rules in the package, such as performance or security. One rule set enables all rules for the category, and one rule set honors the default severity and enablement settings for each rule in the category.
+
+ The [Microsoft.CodeAnalysis.FxCopAnalyzers NuGet analyzer package](https://www.nuget.org/packages/Microsoft.CodeAnalysis.FxCopAnalyzers/) includes rule sets for the following categories, to match the rule sets available for legacy "FxCop" static code analysis:
+
+- design
+- documentation
+- maintainability
+- naming
+- performance
+- reliability
+- security
+- usage
+
+## See also
+
+- [Overview of .NET Compiler Platform analyzers](roslyn-analyzers-overview.md)
+- [Install .NET Compiler Platform analyzers](install-roslyn-analyzers.md)
+- [Configure and use Roslyn analyzer rules](use-roslyn-analyzers.md)
+- [Use rule sets to group code analysis rules](using-rule-sets-to-group-code-analysis-rules.md)

docs/code-quality/ca0063.md

@@ -14,25 +14,27 @@ ms.workload:
   - "multiple"
 ---
 # CA0063
+
 Failed to load rule set file or one of its dependent rule set files.
 
- Failed to load rule set file or one of its dependent rule set files.
+Failed to load rule set file or one of its dependent rule set files.
 
- The specified ruleset could not be found or one of the ruleset files included in your ruleset could not be found. Make sure that the all the rulesets included in your ruleset exist on disk and that the appropriate ruleset directories are being specified in your project through the **CodeAnalysisRuleSetDirectories** property of [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)].
+The specified rule set could not be found or one of the rule set files included in your rule set could not be found. Make sure that the all the rule sets included in your rule set exist on disk and that the appropriate rule set directories are being specified in your project through the **CodeAnalysisRuleSetDirectories** property of [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)].
 
- To debug the error, examine your ruleset file in a text editor. To find the path to the ruleset file, right-click the project in Solution Explorer, click **Properties**, and then click **Code Analysis**. Make sure the ruleset file is selected in **Run this rule set**. The Path to the rule set is listed in the description field.
+To debug the error, examine your rule set file in a text editor. To find the path to the rule set file, right-click the project in Solution Explorer, click **Properties**, and then click **Code Analysis**. Make sure the rule set file is selected in **Run this rule set**. The Path to the rule set is listed in the description field.
 
- Examine the **Path** attribute value all the **Include** elements. Include paths can use relative paths to the parent/current ruleset file, environment variables, and absolute paths. For example:
+Examine the **Path** attribute value all the **Include** elements. Include paths can use relative paths to the parent/current rule set file, environment variables, and absolute paths. For example:
 
-```
+```xml
 <Include Path="%PUBLIC%\Documents\RuleSets\alldesign.ruleset" Action="Default" />
 <Include Path="..\alldesign.ruleset" Action="Default" />
 <Include Path="C:\Rulesets\alldesign.ruleset" Action="Default" />
 ```
 
- Inspect each of these include paths and verify they are all valid.
+Inspect each of these include paths and verify they are all valid.
 
- In some cases, the location of a ruleset can be dependent on an [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)] property. [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)] properties cannot be referenced from a ruleset. To work around this issue, specify additional search paths in the **CodeAnalysisRuleSetDirectories** property of [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)]. In this scenario, specify only the name of the ruleset in the **Path** attribute of the **Include** element.
+In some cases, the location of a rule set can be dependent on an [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)] property. [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)] properties cannot be referenced from a rule set. To work around this issue, specify additional search paths in the **CodeAnalysisRuleSetDirectories** property of [!INCLUDE[vstecmsbuild](../extensibility/internals/includes/vstecmsbuild_md.md)]. In this scenario, specify only the name of the rule set in the **Path** attribute of the **Include** element.
 
 ## See Also
- [Code Analysis Application Errors](../code-quality/code-analysis-application-errors.md)
+
+- [Code Analysis Application Errors](../code-quality/code-analysis-application-errors.md)

docs/code-quality/ca0064.md

@@ -19,12 +19,12 @@ No analysis was performed because the specified rule set did not contain any FxC
 
 This warning can occur in one of the following situations:
 
-- If you encounter this warning in conjunction with CA0063 warnings, there was an a problem loading your ruleset file. For more information, see the [CA0063](ca0063.md) documentation.
+- If you encounter this warning in conjunction with CA0063 warnings, there was a problem loading your rule set file. For more information, see the [CA0063](ca0063.md) article.
 
-- If you encounter this error in conjunction with CA0062 warnings, it most likely that Code Analysis was unable to find the assembly or assemblies that contain the rules specified by the ruleset. For more information, see the [CA0062](ca0062.md) documentation.
+- If you encounter this error in conjunction with CA0062 warnings, it most likely that code analysis was unable to find the assembly or assemblies that contain the rules specified by the rule set. For more information, see the [CA0062](ca0062.md) article.
 
-- Otherwise, this warning usually occurs when your ruleset is empty or all of the rules enabled in a child rule set have been disabled. Use the Visual Studio [rule set editor](../code-quality/working-in-the-code-analysis-rule-set-editor.md) to enable some rules in your ruleset.
+- Otherwise, this warning usually occurs when your rule set is empty or all of the rules enabled in a child rule set are disabled. Use the Visual Studio [rule set editor](../code-quality/working-in-the-code-analysis-rule-set-editor.md) to enable some rules in your rule set.
 
 ## See also
 
-- [Code Analysis Application Errors](../code-quality/code-analysis-application-errors.md)
+- [Code analysis application errors](../code-quality/code-analysis-application-errors.md)

docs/code-quality/ca1020-avoid-namespaces-with-few-types.md

@@ -18,6 +18,7 @@ ms.workload:
   - "multiple"
 ---
 # CA1020: Avoid namespaces with few types
+
 |||
 |-|-|
 |TypeName|AvoidNamespacesWithFewTypes|
@@ -26,16 +27,20 @@ ms.workload:
 |Breaking Change|Breaking|
 
 ## Cause
- A namespace other than the global namespace contains fewer than five types.
+
+A namespace other than the global namespace contains fewer than five types.
 
 ## Rule Description
- Make sure that each of your namespaces has a logical organization, and that a valid reason exists to put types in a sparsely populated namespace. Namespaces should contain types that are used together in most scenarios. When their applications are mutually exclusive, types should be located in separate namespaces. For example, the <xref:System.Web.UI> namespace contains types that are used in Web applications, and the <xref:System.Windows.Forms> namespace contains types that are used in [!INCLUDE[TLA#tla_mswin](../code-quality/includes/tlasharptla_mswin_md.md)]-based applications. Even though both namespaces have types that control aspects of the user interface, these types are not designed for use in the same application. Therefore, they are located in separate namespaces. Careful namespace organization can also be helpful because it increases the discoverability of a feature. By examining the namespace hierarchy, library consumers should be able to locate the types that implement a feature.
+
+Make sure that each of your namespaces has a logical organization, and that a valid reason exists to put types in a sparsely populated namespace. Namespaces should contain types that are used together in most scenarios. When their applications are mutually exclusive, types should be located in separate namespaces. For example, the <xref:System.Web.UI> namespace contains types that are used in web applications, and the <xref:System.Windows.Forms> namespace contains types that are used in [!INCLUDE[TLA#tla_mswin](../code-quality/includes/tlasharptla_mswin_md.md)]-based applications. Even though both namespaces have types that control aspects of the user interface, these types are not designed for use in the same application. Therefore, they are located in separate namespaces. Careful namespace organization can also be helpful because it increases the discoverability of a feature. By examining the namespace hierarchy, library consumers should be able to locate the types that implement a feature.
 
 > [!NOTE]
->  Design-time types and permissions should not be merged into other namespaces to comply with this guideline. These types belong in their own namespaces below your main namespace, and the namespaces should end in `.Design` and `.Permissions`, respectively.
+> Design-time types and permissions should not be merged into other namespaces to comply with this guideline. These types belong in their own namespaces below your main namespace, and the namespaces should end in `.Design` and `.Permissions`, respectively.
 
 ## How to Fix Violations
- To fix a violation of this rule, try to combine namespaces that contain just a few types into a single namespace.
+
+To fix a violation of this rule, try to combine namespaces that contain just a few types into a single namespace.
 
 ## When to Suppress Warnings
- It is safe to suppress a warning from this rule when the namespace does not contain types that are used with the types in your other namespaces.
+
+It is safe to suppress a warning from this rule when the namespace does not contain types that are used with the types in your other namespaces.

docs/code-quality/ca2001-avoid-calling-problematic-methods.md

@@ -39,7 +39,7 @@ Avoid making unnecessary and potentially dangerous method calls. A violation of
 |<xref:System.GC.Collect%2A?displayProperty=fullName>|Calling GC.Collect can significantly affect application performance and is rarely necessary. For more information, see [Rico Mariani's Performance Tidbits](http://go.microsoft.com/fwlink/?LinkId=169256) blog entry on MSDN.|
 |<xref:System.Threading.Thread.Resume%2A?displayProperty=fullName><br /><br /> <xref:System.Threading.Thread.Suspend%2A?displayProperty=fullName>|Thread.Suspend and Thread.Resume have been deprecated because of their unpredictable behavior.  Use other classes in the <xref:System.Threading> namespace, such as <xref:System.Threading.Monitor>, <xref:System.Threading.Mutex>, and <xref:System.Threading.Semaphore>, to synchronize threads or protect resources.|
 |<xref:System.Runtime.InteropServices.SafeHandle.DangerousGetHandle%2A?displayProperty=fullName>|The DangerousGetHandle method poses a security risk because it can return a handle that is not valid. See the <xref:System.Runtime.InteropServices.SafeHandle.DangerousAddRef%2A> and the <xref:System.Runtime.InteropServices.SafeHandle.DangerousRelease%2A> methods for more information about how to use the DangerousGetHandle method safely.|
-|<xref:System.Reflection.Assembly.LoadFrom%2A?displayProperty=fullName><br /><br /> <xref:System.Reflection.Assembly.LoadFile%2A?displayProperty=fullName><br /><br /> <xref:System.Reflection.Assembly.LoadWithPartialName%2A?displayProperty=fullName>|These methods can load assemblies from unexpected locations. For example, see Suzanne Cook's .NET CLR Notes blog posts [LoadFile vs. LoadFrom](http://go.microsoft.com/fwlink/?LinkId=164450) and [Choosing a Binding Context](http://go.microsoft.com/fwlink/?LinkId=164451) on the MSDN Web site for information about methods that load assemblies.|
+|<xref:System.Reflection.Assembly.LoadFrom%2A?displayProperty=fullName><br /><br /> <xref:System.Reflection.Assembly.LoadFile%2A?displayProperty=fullName><br /><br /> <xref:System.Reflection.Assembly.LoadWithPartialName%2A?displayProperty=fullName>|These methods can load assemblies from unexpected locations. For example, see Suzanne Cook's .NET CLR Notes blog posts [LoadFile vs. LoadFrom](http://go.microsoft.com/fwlink/?LinkId=164450) and [Choosing a Binding Context](http://go.microsoft.com/fwlink/?LinkId=164451) for information about methods that load assemblies.|
 |[CoSetProxyBlanket](http://go.microsoft.com/fwlink/?LinkID=169250) (Ole32)<br /><br /> [CoInitializeSecurity](http://go.microsoft.com/fwlink/?LinkId=169255) (Ole32)|By the time the user code starts executing in a managed process, it is too late to reliably call CoSetProxyBlanket. The common language runtime (CLR) takes initialization actions that may prevent the users P/Invoke from succeeding.<br /><br /> If you do have to call CoSetProxyBlanket for a managed application, we recommend that you start the process by using a native code (C++) executable, call CoSetProxyBlanket in the native code, and then start your managed code application in process. (Be sure to specify a runtime version number.)|
 
 ## How to fix violations