Merge pull request #8418 from MicrosoftDocs/main637975839006745232sync_temp

Repo sync for protected CLA branch

Author: Jak-MS

docs/cross-platform/cross-platform-mobile-development-in-visual-studio.md

@@ -7,8 +7,8 @@ ms.date: "10/17/2019"
 ms.technology: vs-ide-mobile
 ms.topic: "conceptual"
 ms.assetid: 8202717a-e990-45cf-b092-438651ccb38a
-author: conceptdev
-ms.author: crdun
+author: therealjohn
+ms.author: johmil
 manager: crdun
 ms.workload:
   - "multiple"

docs/ide/reference/devenv-command-line-switches.md

@@ -2,7 +2,7 @@
 title: Devenv command line switches
 description: Learn about devenv command-line switches and how to use them to set IDE options, and also build, debug, and deploy projects, all from the command line.
 ms.custom: SEO-VS-2020
-ms.date: 12/10/2018
+ms.date: 08/31/2022
 ms.topic: reference
 helpviewer_keywords:
 - switches, Devenv
@@ -70,6 +70,7 @@ The following command-line switches display the IDE and do the described task.
 |[/Edit](edit-devenv-exe.md)|Opens the specified files in a running instance of this application. If there are no running instances, it starts a new instance with a simplified window layout.<br /><br /> `devenv /edit File1 File2`|
 |[/LCID or /L](lcid-devenv-exe.md)|Sets the default language for the IDE. If the specified language isn't included in your installation of Visual Studio, this setting is ignored.<br /><br /> `devenv /l 1033`|
 |[/Log](log-devenv-exe.md)|Starts Visual Studio and logs all activity to the log file.<br /><br /> `devenv /log mylogfile.xml`|
+|/NoScale| Opens the IDE in a [DPI-disabled mode](../../designers/disable-dpi-awareness.md) that allows for a more accurate layout in the Windows Forms Designer. |
 |[/NoSplash](nosplash-devenv-exe.md)|Opens the IDE without showing the splash screen.<br /><br /> `devenv /nosplash File1 File2`|
 |[/ResetSettings](resetsettings-devenv-exe.md)|Restores Visual Studio default settings. Optionally resets the settings to the specified `.vssettings` file.<br /><br /> `devenv /resetsettings mysettings.vssettings`|
 |[/Run or /R](run-devenv-exe.md)|Compiles and runs the specified solution.<br /><br /> `devenv /run mysln.sln`|

docs/msbuild/errors/msb3073.md

@@ -32,4 +32,6 @@ Look to the output of the command to determine the root cause of the failure. If
 
 To diagnose the error, first enable a diagnostic log (use the `-verbosity:diag` command-line switch), and check the MSBuild log file with the full diagnostics output. For bigger output logs on large projects, consider using the binary log (`-bl` command-line switch) and the [MSBuild Structured Log Viewer](https://msbuildlog.com/) to view the output more easily.
 
+You can also set the `MSBuildDebugEngine` environment variable to 1 to get all possible logs. See [Building MSBuild for the .NET Framework - Logs](https://github.com/dotnet/msbuild/blob/main/documentation/wiki/Building-Testing-and-Debugging-on-Full-Framework-MSBuild.md#logs).
+
 It might be helpful to reproduce the error in isolation. Try running the tool separately with the same inputs and command-line arguments that MSBuild used in the build. If symbols are available and you have a Debug build of the tool, you can try attaching a debugger to the tool and debug the tool itself to see what the problem is.

docs/msbuild/errors/msb3277.md

@@ -66,6 +66,8 @@ There was a conflict between "StreamJsonRpc, Version=2.1.0.0, Culture=neutral, P
     References which depend on "StreamJsonRpc, Version = 2.2.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" [].
 ```
 
+You can also set the `MSBuildDebugEngine` environment variable to 1 to get all possible logs. See [Building MSBuild for the .NET Framework - Logs](https://github.com/dotnet/msbuild/blob/main/documentation/wiki/Building-Testing-and-Debugging-on-Full-Framework-MSBuild.md#logs).
+
 ## Common fixes
 
 Depending on the root cause of the conflict, the fix might be to update the version of an assembly on disk, perhaps by upgrading or reinstalling a NuGet package or SDK. If you simply want to update all packages to the latest versions, you can run the command `Update-Package -reinstall` from the Package Manager Console in Visual Studio. See [Reinstalling and updating packages](/nuget/consume-packages/reinstalling-and-updating-packages). However, it could be that you intentionally have more than one version of the referenced assembly on disk, but your project or one of its dependencies needs to be updated so that it's referencing the latest version of the conflicting assembly that you have installed. The Global Assembly Cache (GAC) might also be a source of a potential conflict, in cases where you are referencing a specific version of an assembly, but the GAC overrides it. See [Global Assembly Cache](/dotnet/framework/app-domains/gac).

docs/msbuild/errors/msb3721.md

@@ -26,4 +26,6 @@ To investigate the error, check the build output or build log to see if the cust
 
 If you can't see the exact command-line that failed, you can change the verbosity of the build output to show more detail. The MSBuild command-line option is `-verbosity:{level}` or `-V:{level}`, where `{level}` is one of `q[uiet]`, `m[inimal]`, `n[ormal]` (the default), `d[etailed]`, or `diag[nostic]`. See [MSBuild command line reference](../msbuild-command-line-reference.md). For bigger output logs on large projects, consider using the binary log (`-bl` command-line switch) and the [MSBuild Structured Log Viewer](https://msbuildlog.com/) to view the output more easily.
 
+You can also set the `MSBuildDebugEngine` environment variable to 1 to get all possible logs. See [Building MSBuild for the .NET Framework - Logs](https://github.com/dotnet/msbuild/blob/main/documentation/wiki/Building-Testing-and-Debugging-on-Full-Framework-MSBuild.md#logs).
+
 In Visual Studio, you can change the verbosity in **Tools** > **Options**, **Projects and Solutions**, **Build and Run**. See [How to: View, save, and configure build log files](../../ide/how-to-view-save-and-configure-build-log-files.md#to-change-the-amount-of-information-included-in-the-build-log).

docs/msbuild/errors/msb4181.md

@@ -20,12 +20,14 @@ ms.workload:
 ---
 # MSB4181: The 'task' task returned false but did not log an error
 
-This error occurs when a task returned `false` to signal that it did not complete successfully, but did not log an error. This indicates a failure from a task that did not report enough information about the problem.  
+This error occurs when a task returned `false` to signal that it didn't complete successfully, but didn't log an error. If you see this error, it means task failed, but it didn't report a specific error with more information.  
 
-To diagnose the error, first enable a diagnostic log (use the `-verbosity:diag` command-line switch), and check the MSBuild log file with the full diagnostics output. For bigger output logs on large projects, consider using the binary log (`-bl` command-line switch) and the [MSBuild Structured Log Viewer](https://msbuildlog.com/) to view the output more easily.
+To diagnose the problem, first enable a diagnostic log (use the `-verbosity:diag` command-line switch), and check the MSBuild log file with the full diagnostics output. For bigger output logs on large projects, consider using the binary log (`-bl` command-line switch) and the [MSBuild Structured Log Viewer](https://msbuildlog.com/) to view the output more easily.
+
+You can also set the `MSBuildDebugEngine` environment variable to 1 to get all possible logs. See [Building MSBuild for the .NET Framework - Logs](https://github.com/dotnet/msbuild/blob/main/documentation/wiki/Building-Testing-and-Debugging-on-Full-Framework-MSBuild.md#logs).
 
 If the task ran an executable, try running the executable separately with the same inputs and command line.
 
-If you know the owner of the task, consider reporting this issue to them and recommending that they modify the task to log more information.
+If you know the owner of the task, consider reporting this issue to the task owner and recommending that they modify the task to log more information.
 
-If it's a custom task and you are the task owner, consider improving the error logging.
+If it's a custom task and you are the task owner, consider improving the error logging. For example, if an API you're calling could throw an exception, add an exception handler that logs the exception message.

docs/msbuild/errors/msb6003.md

@@ -24,6 +24,8 @@ This error indicates that an executable that was part of the build process could
 
 If you need more information to diagnose the error, first enable a diagnostic log (use the `-verbosity:diag` command-line switch), and check the MSBuild log file with the full diagnostics output. For bigger output logs on large projects, consider using the binary log (`-bl` command-line switch) and the [MSBuild Structured Log Viewer](https://msbuildlog.com/) to view the output more easily.
 
+You can also set the `MSBuildDebugEngine` environment variable to 1 to get all possible logs. See [Building MSBuild for the .NET Framework - Logs](https://github.com/dotnet/msbuild/blob/main/documentation/wiki/Building-Testing-and-Debugging-on-Full-Framework-MSBuild.md#logs).
+
 If the task ran an executable, try running the executable separately with the same inputs and command line.
 
 Examples of situations that cause this error:

docs/msbuild/errors/msb6006.md

@@ -28,6 +28,8 @@ This error occurs when a command is executed and returns a non-zero exit code, o
 
 Look to the output of the command to determine the root cause of the failure. If logging was enabled in the build, the output might be written to the build log.
 
-To diagnose the error, first enable a diagnostic log (use the `-verbosity:diag` command-line switch), and check the MSBuild log file with the full diagnostics output. For bigger output logs on large projects, consider using the binary log (`-bl` command-line switch) and the [MSBuild Structured Log Viewer](https://msbuildlog.com/) to view the output more easily.
+To diagnose the error, first enable a diagnostic log (use the `-verbosity:diag` command-line switch), and check the MSBuild log file with the full diagnostics output. For bigger output logs on large projects, consider using the binary log (`-bl` command-line switch) and the [MSBuild Structured Log Viewer](https://msbuildlog.com/) to view the output more easily. 
+
+You can also set the `MSBuildDebugEngine` environment variable to 1 to get all possible logs. See [Building MSBuild for the .NET Framework - Logs](https://github.com/dotnet/msbuild/blob/main/documentation/wiki/Building-Testing-and-Debugging-on-Full-Framework-MSBuild.md#logs).
 
 It might be helpful to reproduce the error in isolation. Try running the tool separately with the same inputs and command-line arguments that MSBuild used in the build. If symbols are available and you have a Debug build of the tool, you can try attaching a debugger to the tool and debug the tool itself to see what the problem is.

docs/test/how-to-create-a-web-service-test.md

@@ -21,7 +21,7 @@ ms.technology: vs-ide-test
 You can use a web performance test to test web services. By using the **Insert Request** and **Insert Web Service Request** options, you can customize the individual requests in the **Web Performance Test Editor** to locate web service pages. Typically, you do not display these pages in the web application. Therefore, you must customize the request to gain access to these pages.
 
 >[!NOTE]
-> Web performance and load test functionality is deprecated in Visual Studio 2019. For Application Insights, multi-step web tests depend on Visual Studio webtest files. It was [announced](https://devblogs.microsoft.com/devops/cloud-based-load-testing-service-eol/) that Visual Studio 2019 will be the last version with webtest functionality. It is important to understand that while no new features will be added, webtest functionality in Visual Studio 2019 is still currently supported and will continue to be supported during the support lifecycle of the product. The Azure Monitor product team has addressed questions regarding the future of multi-step availability tests [here](https://github.com/MicrosoftDocs/azure-docs/issues/26050#issuecomment-468814101).
+> Web performance and load test functionality is deprecated in Visual Studio 2019. For Application Insights, multi-step web tests depend on Visual Studio webtest files. It was [announced](https://devblogs.microsoft.com/devops/cloud-based-load-testing-service-eol/) that Visual Studio 2019 will be the last version with webtest functionality. It is important to understand that while no new features will be added, webtest functionality in Visual Studio 2019 is still currently supported and will continue to be supported during the support lifecycle of the product. The Azure Monitor product team has addressed questions regarding the future of multi-step availability tests [here](https://github.com/MicrosoftDocs/azure-docs/issues/26050#issuecomment-468814101). We recommend using [Apache JMeter](https://jmeter.apache.org) in [Azure Load Test](https://azure.microsoft.com/services/load-testing/) as an alternative.
 
 **Requirements**
 

docs/test/includes/web-load-test-deprecated.md

@@ -2,4 +2,4 @@
 ms.topic: include
 ---
 > [!NOTE]
-> Web performance and load test functionality is deprecated. Visual Studio 2019 is the last version where web performance and load testing will be fully available. For more information, see the [Cloud-based load testing service end of life](https://devblogs.microsoft.com/devops/cloud-based-load-testing-service-eol/) blog post. To reduce the impact on users some minimum support is still available in Visual Studio 2022 Preview 3 or later. Users should also note web performance and load test functionality only supports Internet Explorer which is not available on Windows 11 and some versions of Windows 10. Read more on [Internet Explorer Lifecycle policy](/lifecycle/faq/internet-explorer-microsoft-edge#what-is-the-lifecycle-policy-for-internet-explorer-).
+> Web performance and load test functionality is deprecated. Visual Studio 2019 is the last version where web performance and load testing will be fully available. For more information, see the [Cloud-based load testing service end of life](https://devblogs.microsoft.com/devops/cloud-based-load-testing-service-eol/) blog post. To reduce the impact on users, some minimum support is still available in Visual Studio 2022 Preview 3 or later. Users should also note web performance and load test functionality only supports Internet Explorer which is not available on Windows 11 and some versions of Windows 10. Read more on [Internet Explorer Lifecycle policy](/lifecycle/faq/internet-explorer-microsoft-edge#what-is-the-lifecycle-policy-for-internet-explorer-). We recommend that you use [Azure Load Testing](https://azure.microsoft.com/services/load-testing/) as an alternative.