MicrosoftDocs · ghogen · Feb 22, 2020 · Feb 14, 2020 · Feb 14, 2020 · Feb 14, 2020
diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json
@@ -4880,6 +4880,11 @@
       "redirect_url": "/visualstudio/porting/port-migrate-and-upgrade-visual-studio-projects",
       "redirect_document_id": false
     },
+    {
+      "source_path": "docs/profiling/walkthrough-command-line-profiling-using-sampling.md",
+      "redirect_url": "/visualstudio/profiling/command-line-profiling-of-stand-alone-applications",
+      "redirect_document_id": false
+    },
     {
       "source_path": "docs/profiling/analyze-cpu-usage-in-a-windows-universal-app.md",
       "redirect_url": "/visualstudio/profiling/beginners-guide-to-performance-profiling",

diff --git a/docs/debugger/graphics/getting-started-with-visual-studio-graphics-diagnostics.md b/docs/debugger/graphics/getting-started-with-visual-studio-graphics-diagnostics.md
@@ -29,11 +29,11 @@ In this section you'll prepare to use Graphics Diagnostics for the first time, t
 
 1. In Search, type **Apps and features** and then open the **Apps & features** settings.
 
-2. On the right-hand side of the **Apps & features** dialog, choose **Manage optional features** (under **Apps & features**).
+2. On the right-hand side of the **Apps & features** settings, choose **Optional features** (under **Apps & features**).
 
-   The **Manage optional features** dialog appears.
+   The **Optional features** settings appear.
 
-3. In the **Manage optional features** dialog, choose **Add a feature**. A list of optional features you can install appears.
+3. In the **Optional features** settings, choose **Add a feature**. A list of optional features you can install appears.
 
 4. Select **Graphics Tools** from the list of features, then choose **Install**.
 

diff --git a/docs/debugger/how-to-debug-an-executable-not-part-of-a-visual-studio-solution.md b/docs/debugger/how-to-debug-an-executable-not-part-of-a-visual-studio-solution.md
@@ -1,8 +1,8 @@
 ---
 title: "Debug an app that isn't part of a Visual Studio solution"
 titleSuffix: ""
-ms.custom: "seodec18"
-ms.date: "11/19/2018"
+ms.custom: ""
+ms.date: "02/21/2020"
 ms.topic: "conceptual"
 dev_langs:
   - "CSharp"
@@ -23,13 +23,15 @@ ms.workload:
 ---
 # Debug an app that isn't part of a Visual Studio solution (C++, C#, Visual Basic, F#)
 
-You may want to debug an app (*.exe* file) that isn't part of a Visual Studio solution. You or someone else may have created the app outside of Visual Studio, or you got the app from somewhere else.
+You may want to debug an app (*.exe* file) that isn't part of a Visual Studio solution. It may be an [open folder](../ide/develop-code-in-visual-studio-without-projects-or-solutions.md) project, or you or someone else may have created the app outside of Visual Studio, or you got the app from somewhere else.
 
-The usual way to debug an app that doesn't exist in Visual Studio is to start the app outside of Visual Studio, and then attach to it using **Attach to Process** in the Visual Studio debugger. For more information, see [Attach to running processes](../debugger/attach-to-running-processes-with-the-visual-studio-debugger.md).
+- For an open folder project in Visual Studio (which has no project or solution file), see [Run and debug your code](../ide/develop-code-in-visual-studio-without-projects-or-solutions.md#run-and-debug-your-code) or, for C++, [Configure debugging parameters with launch.vs.json](/cpp/build/open-folder-projects-cpp#configure-debugging-parameters-with-launchvsjson).
 
-Attaching to an app requires manual steps that take a few seconds. Because of this delay, attaching won't help debug a startup issue, or an app that doesn't wait for user input and finishes quickly.
+- For an app that doesn't exist in Visual Studio, the usual way to debug is to start the app outside of Visual Studio, and then attach to it using **Attach to Process** in the Visual Studio debugger. For more information, see [Attach to running processes](../debugger/attach-to-running-processes-with-the-visual-studio-debugger.md).
 
-In these situations, you can create a Visual Studio EXE project for the app, or import it into an existing C#, Visual Basic, or C++ solution. Not all programming languages support EXE projects.
+   Attaching to an app requires manual steps that take a few seconds. Because of this delay, attaching won't help debug a startup issue, or an app that doesn't wait for user input and finishes quickly.
+
+   In these situations, you can create a Visual Studio EXE project for the app, or import it into an existing C#, Visual Basic, or C++ solution. Not all programming languages support EXE projects.
 
 >[!IMPORTANT]
 >Debugging features for an app that wasn't built in Visual Studio are limited, whether you attach to the app or add it to a Visual Studio solution.

diff --git a/docs/deployment/how-to-include-prerequisites-with-a-clickonce-application.md b/docs/deployment/how-to-include-prerequisites-with-a-clickonce-application.md
@@ -25,10 +25,10 @@ Before you can distribute prerequisite software with a [!INCLUDE[ndptecclick](..
 
 3. In Notepad, open the *Package.xml* file.
 
-4. Locate the **Name** element that contains **http://go.microsoft.com/fwlink**, and copy the URL. Include the **LinkID** portion.
+4. Locate the **Name** element that contains `http://go.microsoft.com/fwlink`, and copy the URL. Include the **LinkID** portion.
 
    > [!NOTE]
-   > If no **Name** element contains **http://go.microsoft.com/fwlink**, open the **Product.xml** file in the root folder for the prerequisite and locate the **fwlink** string.
+   > If no **Name** element contains `http://go.microsoft.com/fwlink`, open the **Product.xml** file in the root folder for the prerequisite and locate the **fwlink** string.
 
    > [!IMPORTANT]
    > Some prerequisites have multiple installer packages (for example, for 32-bit or 64-bit systems). If multiple **Name** elements contain **fwlink**, you must repeat the remaining steps for each of them.

diff --git a/docs/deployment/how-to-specify-the-location-where-end-users-will-install-from.md b/docs/deployment/how-to-specify-the-location-where-end-users-will-install-from.md
@@ -34,7 +34,7 @@ The `Installation URL` property can be set on the **Publish** page of the **Proj
 
 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.contoso.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/deployment/server-and-client-configuration-issues-in-clickonce-deployments.md b/docs/deployment/server-and-client-configuration-issues-in-clickonce-deployments.md
@@ -43,7 +43,7 @@ If you use Internet Information Services (IIS) on Windows Server, and your deplo
 ## ClickOnce and proxy authentication
  [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] provides support for Windows Integrated proxy authentication starting in .NET Framework 3.5. No specific machine.config directives are required. [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] does not provide support for other authentication protocols such as Basic or Digest.
 
- You can also apply a hotfix to .NET Framework 2.0 to enable this feature. For more information, see http://go.microsoft.com/fwlink/?LinkId=158730.
+ You can also apply a hotfix to .NET Framework 2.0 to enable this feature. For more information, see [FIX: Error message when you try to install a ClickOnce application that you created in the .NET Framework 2.0 onto a client computer that is configured to use a proxy server: "Proxy authentication required"](https://support.microsoft.com/help/917952/fix-error-message-when-you-try-to-install-a-clickonce-application-that).
 
  For more information, see [\<defaultProxy> element (network settings)](/dotnet/framework/configure-apps/file-schema/network/defaultproxy-element-network-settings).
 
@@ -112,7 +112,7 @@ If you use Internet Information Services (IIS) on Windows Server, and your deplo
 
 - If you create a MIME type with extension "<em>" and the MIME type "application/octet-stream," it will allow files of unblocked file type to be downloaded. (However, blocked file types such as *.aspx</em> and *.asmx* cannot be downloaded.)
 
-  For specific instructions on configuring MIME types on Windows Server, refer to Microsoft Knowledge Base article KB326965, "IIS 6.0 does not serve unknown MIME types" at [http://support.microsoft.com/default.aspx?scid=kb;en-us;326965](http://support.microsoft.com/default.aspx?scid=kb;en-us;326965).
+  For specific instructions on configuring MIME types on Windows Server, see [How to add a MIME type to a Web site or application](/iis/configuration/system.webserver/staticcontent/mimemap#how-to-add-a-mime-type-to-a-web-site-or-application).
 
 ## Content type mappings
  When publishing over HTTP, the content type (also known as MIME type) for the *.application* file should be "application/x-ms-application." If you have .NET Framework 2.0 installed on the server, this will be set for you automatically. If this is not installed, then you need to create a MIME type association for the [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] application vroot (or entire server).

diff --git a/docs/extensibility/commandtable-element.md b/docs/extensibility/commandtable-element.md
@@ -40,7 +40,7 @@ CommandTable is the root element of the *.vsct* file. This is the file that defi
 
 | 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/ide/editorconfig-code-style-settings-reference.md b/docs/ide/editorconfig-code-style-settings-reference.md
@@ -1,6 +1,6 @@
 ---
 title: .NET coding convention settings For EditorConfig
-ms.date: 06/14/2018
+ms.date: 02/21/2020
 ms.topic: reference
 helpviewer_keywords:
 - coding conventions [EditorConfig]
@@ -16,7 +16,7 @@ ms.workload:
 ---
 # .NET coding convention settings for EditorConfig
 
-You can define and maintain consistent code style in your codebase with the use of an [EditorConfig](../ide/create-portable-custom-editor-options.md) file. EditorConfig includes several core formatting properties, such as `indent_style` and `indent_size`. In Visual Studio, .NET coding conventions settings can also be configured by using an EditorConfig file. You can enable or disable individual .NET coding conventions and configure the degree to which you want each rule enforced, via a severity level.
+You can define and maintain consistent code style in your codebase by using an [EditorConfig](../ide/create-portable-custom-editor-options.md) file. EditorConfig includes several core formatting properties, such as `indent_style` and `indent_size`. In Visual Studio, .NET coding conventions settings can also be configured by using an EditorConfig file. You can enable or disable individual .NET coding conventions and configure the degree to which you want each rule enforced, via a severity level.
 
 > [!TIP]
 > - When you define coding conventions in an EditorConfig file, you're configuring how you want the [code style analyzers](../code-quality/roslyn-analyzers-overview.md) that are built into Visual Studio to analyze your code. The EditorConfig file is the configuration file for these analyzers.
@@ -40,7 +40,7 @@ There are three supported .NET coding convention categories:
 
 ## Example EditorConfig file
 
-To help you get started, here is an example *.editorconfig* file with the default options:
+To help you get started, here is an example *.editorconfig* file with the default options. In Visual Studio, you can generate this file and save it to a project at **Tools** > **Options** > **Text Editor** > [**C#** or  **Basic**] > **Code Style** > **General**. Then, click the **Generate .editorconfig file from settings** button. For more information, see [Code style preferences](code-styles-and-code-cleanup.md).
 
 ```ini
 ###############################
@@ -64,9 +64,9 @@ charset = utf-8-bom
 ###############################
 
 [*.{cs,vb}]
+
 # Organize usings
 dotnet_sort_system_directives_first = true
-dotnet_separate_import_directive_groups = false
 
 # this. preferences
 dotnet_style_qualification_for_field = false:silent
@@ -107,8 +107,7 @@ dotnet_style_prefer_conditional_expression_over_return = true:silent
 
 # Style Definitions
 dotnet_naming_style.pascal_case_style.capitalization             = pascal_case
-
-# Use PascalCase for constant fields
+# Use PascalCase for constant fields  
 dotnet_naming_rule.constant_fields_should_be_pascal_case.severity = suggestion
 dotnet_naming_rule.constant_fields_should_be_pascal_case.symbols  = constant_fields
 dotnet_naming_rule.constant_fields_should_be_pascal_case.style    = pascal_case_style
@@ -117,10 +116,11 @@ dotnet_naming_symbols.constant_fields.applicable_accessibilities  = *
 dotnet_naming_symbols.constant_fields.required_modifiers          = const
 
 ###############################
-# C# Code Style Rules         #
+# C# Coding Conventions       #
 ###############################
 
 [*.cs]
+
 # var preferences
 csharp_style_var_for_built_in_types = true:silent
 csharp_style_var_when_type_is_apparent = true:silent
@@ -134,7 +134,7 @@ csharp_style_expression_bodied_properties = true:silent
 csharp_style_expression_bodied_indexers = true:silent
 csharp_style_expression_bodied_accessors = true:silent
 
-# Pattern-matching preferences
+# Pattern matching preferences
 csharp_style_pattern_matching_over_is_with_cast_check = true:suggestion
 csharp_style_pattern_matching_over_as_with_null_check = true:suggestion
 
@@ -182,18 +182,17 @@ csharp_space_around_binary_operators = before_and_after
 csharp_space_between_method_declaration_empty_parameter_list_parentheses = false
 csharp_space_between_method_call_name_and_opening_parenthesis = false
 csharp_space_between_method_call_empty_parameter_list_parentheses = false
-csharp_space_after_comma = true
-csharp_space_after_dot = false
 
 # Wrapping preferences
 csharp_preserve_single_line_statements = true
 csharp_preserve_single_line_blocks = true
 
-##################################
-# Visual Basic Code Style Rules  #
-##################################
+###############################
+# VB Coding Conventions       #
+###############################
 
 [*.vb]
+
 # Modifier preferences
 visual_basic_preferred_modifier_order = Partial,Default,Private,Protected,Public,Friend,NotOverridable,Overridable,MustOverride,Overloads,Overrides,MustInherit,NotInheritable,Static,Shared,Shadows,ReadOnly,WriteOnly,Dim,Const,WithEvents,Widening,Narrowing,Custom,Async:suggestion
 ```
@@ -202,4 +201,5 @@ visual_basic_preferred_modifier_order = Partial,Default,Private,Protected,Public
 
 - [Quick Actions](../ide/quick-actions.md)
 - [Create portable custom editor options](../ide/create-portable-custom-editor-options.md)
-- [.NET Compiler Platform's .editorconfig file](https://github.com/dotnet/roslyn/blob/master/.editorconfig)
+- [.NET Compiler Platform "Roslyn" .editorconfig file](https://github.com/dotnet/roslyn/blob/master/.editorconfig)
+- [.NET Compiler Platform Runtime .editorconfig file](https://github.com/dotnet/runtime/blob/master/.editorconfig)
diff --git a/docs/ide/reference/lcid-devenv-exe.md b/docs/ide/reference/lcid-devenv-exe.md
@@ -47,13 +47,18 @@ The following table lists the LCIDs of the languages supported by Visual Studio.
 |--------------|----------|
 |Chinese (Simplified)|2052|
 |Chinese (Traditional)|1028|
+|Czech|1029|
 |English|1033|
 |French|1036|
 |German|1031|
 |Italian|1040|
 |Japanese|1041|
 |Korean|1042|
+|Polish|1045|
+|Portuguese (Brazil)|1046|
+|Russian|1049|
 |Spanish|3082|
+|Turkish|1055
 
 ## Example
 

diff --git a/docs/msbuild/common-msbuild-project-properties.md b/docs/msbuild/common-msbuild-project-properties.md
@@ -62,6 +62,7 @@ The following table lists frequently used properties that are defined in the Vis
 | FileAlignment | Specifies, in bytes, where to align the sections of the output file. Valid values are 512, 1024, 2048, 4096, 8192. This property is equivalent to the `/filealignment` compiler switch. |
 | FrameworkPathOverride | Specifies the location of *mscorlib.dll* and *microsoft.visualbasic.dll*. This parameter is equivalent to the `/sdkpath` switch of the *vbc.exe* compiler. |
 | GenerateDocumentation | (C#, Visual Basic) A boolean parameter that indicates whether documentation is generated by the build. If `true`, the build generates documentation information and puts it in an *.xml* file together with the name of the executable file or library that the build task created. |
+| GenerateFullPaths | (C#) Generate full paths for filenames in output by using the [-fullpaths](/dotnet/csharp/language-reference/compiler-options/fullpaths-compiler-option) compiler option. |
 | GenerateSerializationAssemblies | Indicates whether XML serialization assemblies should be generated by *SGen.exe*, which can be set to on, auto, or off. This property is used for assemblies that target .NET Framework only. To generate XML serialization assemblies for .NET Standard or .NET Core assemblies, reference the *Microsoft.XmlSerializer.Generator* NuGet package. |
 | IntermediateOutputPath | The full intermediate output path as derived from `BaseIntermediateOutputPath`, if no path is specified. For example, *\obj\debug\\*. |
 | KeyContainerName | The name of the strong-name key container. |

diff --git a/docs/msbuild/copy-task.md b/docs/msbuild/copy-task.md
@@ -30,7 +30,7 @@ The following table describes the parameters of the `Copy` task.
 
 |Parameter|Description|
 |---------------|-----------------|
-|`CopiedFiles`|Optional <xref:Microsoft.Build.Framework.ITaskItem>`[]` output parameter.<br /><br /> Contains the items that were successfully copied.|
+|`CopiedFiles`|Optional <xref:Microsoft.Build.Framework.ITaskItem>`[]` output parameter.<br /><br /> Contains the items that were successfully copied, *including* those that were not actually copied, but were skipped because they were already up-to-date and `SkipUnchangedFiles` was `true`.|
 |`DestinationFiles`|Optional <xref:Microsoft.Build.Framework.ITaskItem>`[]` parameter.<br /><br /> Specifies the list of files to copy the source files to. This list is expected to be a one-to-one mapping with the list specified in the `SourceFiles` parameter. That is, the first file specified in `SourceFiles` will be copied to the first location specified in `DestinationFiles`, and so forth.|
 |`DestinationFolder`|Optional <xref:Microsoft.Build.Framework.ITaskItem> parameter.<br /><br /> Specifies the directory to which you want to copy the files. This must be a directory, not a file. If the directory does not exist, it is created automatically.|
 |`OverwriteReadOnlyFiles`|Optional `Boolean` parameter.<br /><br /> Overwrite files even if they are marked as read only files|

diff --git a/docs/msbuild/delete-task.md b/docs/msbuild/delete-task.md
@@ -34,6 +34,9 @@ The following table describes the parameters of the `Delete` task.
 ## Remarks
 In addition to the parameters listed above, this task inherits parameters from the <xref:Microsoft.Build.Tasks.TaskExtension> class, which itself inherits from the <xref:Microsoft.Build.Utilities.Task> class. For a list of these additional parameters and their descriptions, see [TaskExtension base class](../msbuild/taskextension-base-class.md).
 
+> [!WARNING]
+> Be careful when you use wildcards with the `Delete` task. You can easily delete the wrong files with expressions like `$(SomeProperty)\**\*.*` or `$(SomeProperty)/**/*.*`, especially if the property evaluates to an empty string, in which case the `Files` parameter can evaluate to the root of your drive and delete much more than you wanted to delete.
+
 ## Example
 The following example deletes the file *MyApp.pdb*.