Merged main into live

mijacobs · mijacobs · commit dc1196e94136 · 2025-07-03T01:02:04.000Z
diff --git a/docs/data-tools/create-a-simple-data-application-with-wpf-and-entity-framework-6.md b/docs/data-tools/create-a-simple-data-application-with-wpf-and-entity-framework-6.md
@@ -6,7 +6,7 @@ ms.author: ghogen
 manager: mijacobs
 ms.subservice: data-tools
 ms.topic: tutorial
-ms.date: 03/27/2025
+ms.date: 7/2/2025
 dev_langs:
 - CSharp
 
@@ -17,7 +17,7 @@ dev_langs:
 # Create a basic data application with WPF and Entity Framework 6
 
 ::: moniker range="vs-2022"
-> [!WARNING]
+> [!NOTE]
 > If you're running Visual Studio 2022, ensure you use version 17.3 or later for this tutorial.
 ::: moniker-end
 
@@ -41,7 +41,7 @@ In this tutorial, you:
 
 ## Prerequisites
 
-* [Visual Studio](https://visualstudio.microsoft.com/downloads/?cid=learn-onpage-download-cta) with the **Windows Communication Foundation** component installed. To install it:
+* [Visual Studio](https://visualstudio.microsoft.com/downloads/?cid=learn-onpage-download-cta) with **.NET Desktop Development** workload installed, and the **Windows Communication Foundation** component installed. To install it:
 
    1. Open the **Visual Studio Installer** app, or select **Tools** > **Get Tools and Features** from the Visual Studio menu.
    1. In **Visual Studio Installer**, choose **Modify** next to the version of Visual Studio you want to modify.
@@ -52,6 +52,8 @@ In this tutorial, you:
 
 * SQL Server Object Explorer. To install it, install the **Data storage and processing** workload in the **Visual Studio Installer** app.
 
+* Entity Framework 6 tools. This is usually installed when you install the **.NET Dektop Development** workload.
+
 ## Install and connect to Northwind
 
 The following example uses SQL Server Express LocalDB and the Northwind sample database. If the ADO.NET data provider for that product supports Entity Framework, it should work with other SQL database products as well.
diff --git a/docs/ide/intellicode-visual-studio.md b/docs/ide/intellicode-visual-studio.md
@@ -2,7 +2,7 @@
 title: IntelliCode for Visual Studio
 titleSuffix: ""
 description: Read an overview of IntelliCode for Visual Studio. Understand preview features, supported languages, prerequisites, troubleshooting issues, and telemetry.
-ms.date: 4/1/2025
+ms.date: 7/2/2025
 ms.service: visual-studio-family
 ms.subservice: intellicode
 ms.topic: conceptual
@@ -88,7 +88,7 @@ If disabling extensions that override IntelliSense UI doesn't solve the problem
 
 IntelliCode captures some anonymized usage and error-reporting data to help improve the product. No user-defined code is sent to Microsoft, but we do collect information about your use of the IntelliCode results.  For base model suggestions, which are open source or .NET types and members, we capture whether you selected an IntelliCode suggestion and log the name of the suggestion. Microsoft uses the data to monitor the quality of the base model. For custom models, we capture whether you selected an IntelliCode suggestion but *don't* log the names of your user-defined types or methods.
 
-To turn off data collection for IntelliCode, opt out of the [Visual Studio Experience Improvement Program](visual-studio-experience-improvement-program.md). From the menu bar, select **Help** > **Send Feedback** > **Settings**. In the **Visual Studio Experience Improvement Program** dialog, select **No, I would not like to participate** and then select **OK**.
+To turn off data collection for IntelliCode, opt out of the [Visual Studio Experience Improvement Program](visual-studio-experience-improvement-program.md). From the menu bar, select **Help** > **Privacy** > **Privacy Settings**. In the **Visual Studio Experience Improvement Program** dialog, select **No, I would not like to participate** and then select **OK**.
 
 ## See also
 
diff --git a/docs/ide/reference/command-devenv-exe.md b/docs/ide/reference/command-devenv-exe.md
@@ -1,7 +1,7 @@
 ---
 title: -Command (devenv.exe)
 description: Learn how to use the Command devenv command-line switch to execute a specified command after launching the Visual Studio IDE.
-ms.date: 12/10/2018
+ms.date: 7/2/2025
 ms.topic: reference
 helpviewer_keywords:
 - Devenv, /Command switch
@@ -45,8 +45,6 @@ The third example creates a new file called `some_file.cs` and opens it in a cod
 ```shell
 devenv /command "Macros.MyMacros.Module1.OpenFavoriteFiles"
 
-devenv /command "navigate https://learn.microsoft.com/"
-
 devenv /command "nf some_file.cs"
 ```
 
diff --git a/docs/ide/visual-studio-whole-line-completions.md b/docs/ide/visual-studio-whole-line-completions.md
@@ -18,6 +18,8 @@ This feature supports C# in Visual Studio 2022.
 
 ![Screenshot of Whole Line Completion by IntelliCode in Visual Studio.](media/intellicode/intellicode-visual-studio-whole-line-completions-small.png)
 
+To turn text predictions off, disable the IntelliCode extension. Select **Extensions** > **Manage Extensions** from the menu, find and select the IntelliCode extension, and then click **Disable**.
+
 ## How it works
 
 IntelliCode uses a large scale transformer model, trained on around half a million public, open-source repos from GitHub. This model makes predictions on what you type next based on a rich knowledge of what you have coded so far, including:
diff --git a/docs/msbuild/errors/msb3277.md b/docs/msbuild/errors/msb3277.md
@@ -1,7 +1,7 @@
 ---
 title: MSB3277 diagnostic code
-description: Learn about the possible causes of the MSB3277 build error and get troubleshooting tips.
-ms.date: 05/16/2025
+description: Learn about the possible causes of the MSB3277 build warning and get troubleshooting tips.
+ms.date: 7/2/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB3277
@@ -20,25 +20,25 @@ ms.subservice: msbuild
 
 <!-- :::ErrorDefinitionDescription::: -->
 <!-- :::editable-content name="introDescription"::: -->
-This article describes the MSB3277 error code.
+This article describes the MSB3277 warning.
 <!-- :::editable-content-end::: -->
 
 ## Message text
 
 <!-- :::editable-content name="messageText"::: -->
-`MSB3277: Found conflicts between different versions of 'value' that could not be resolved.`
+`MSB3277: Found conflicts between different versions of 'assembly-name' that could not be resolved.`
 <!-- :::editable-content-end::: -->
 <!-- MSB3277: Found conflicts between different versions of "{0}" that could not be resolved.
 {1} -->
 
 <!-- :::editable-content name="postOutputDescription"::: -->
 ## Description
 
-This error occurs during a build when more than one version of the same dependent assembly is referenced in a build of the same project. In a .NET build, all assemblies that are referenced, directly or indirectly through other referenced assemblies, have to resolve to the same version. You can't reference two different and conflicting versions of the same assembly when building the same binary. The [ResolveAssemblyReference task](../resolveassemblyreference-task.md) emits this error. The task inspects all the referenced assemblies, and all assemblies referenced indirectly by those assemblies, and so on. The task works through the process until all assembly references are resolved.
+This warning occurs during a build when more than one version of the same dependent assembly is referenced in a build of the same project. In a .NET build, all assemblies that are referenced, directly or indirectly through other referenced assemblies, have to resolve to the same version. You shouldn't reference two different and conflicting versions of the same assembly when building the same binary. The [ResolveAssemblyReference task](../resolveassemblyreference-task.md) emits this warning. The task inspects all the referenced assemblies, and all assemblies referenced indirectly by those assemblies, and so on. The task works through the process until all assembly references are resolved.
 
-## Diagnose the error
+## Diagnose the warning
 
-To diagnose the error, first enable diagnostic log output by using the `-verbosity:diag` command-line switch, and then check the MSBuild log file with the full diagnostics output. For longer 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 issue, first enable diagnostic log output by using the `-verbosity:diag` command-line switch, and then check the MSBuild log file with the full diagnostics output. For longer 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.
 
 In MSBuild 16.x or later, the specific assembly versions in conflict are written to the log file. In earlier versions of MSBuild, the content isn't added to the log file. Instead, follow the assembly dependency chain to locate the conflicting reference. Look at each assembly that your project references, and then the assemblies that the initial assemblies reference, and so on. Follow this process until you identify the conflicting assembly versions.
 
@@ -108,10 +108,10 @@ Visual Studio or settings in project files can enable or disable automatic bindi
 
 In advanced scenarios, your project might intentionally require more than one version of the same assembly. You can use special techniques to override the normal assembly loading process to accomplish the goal. For more information, see [Resolve assembly loads](/dotnet/standard/assembly/resolve-loads). Be sure to understand and follow the guidance in [Best practices for assembly loading](/dotnet/framework/deployment/best-practices-for-assembly-loading).
 
-For a guide on resolving errors with assembly references, see [Troubleshoot assembly references](../troubleshoot-assembly-references.md) and [How the runtime locates assemblies](/dotnet/framework/deployment/how-the-runtime-locates-assemblies).
+For a guide on resolving issues with assembly references, see [Troubleshoot assembly references](../troubleshoot-assembly-references.md) and [How the runtime locates assemblies](/dotnet/framework/deployment/how-the-runtime-locates-assemblies).
 <!-- :::editable-content-end::: -->
 <!-- :::ErrorDefinitionDescription-end::: -->
 
 ## Applies to
 
-All versions of MSBuild
+All versions of MSBuild
diff --git a/docs/msbuild/item-functions.md b/docs/msbuild/item-functions.md
@@ -1,7 +1,7 @@
 ---
 title: Call item functions from MSBuild code
 description: Explore how MSBuild code in tasks and targets can call item functions to get information about the items in the project.
-ms.date: 2/7/2025
+ms.date: 7/2/2025
 ms.topic: how-to
 helpviewer_keywords:
 - msbuild, Item functions
@@ -57,11 +57,11 @@ The table below lists the intrinsic functions available for items.
 |`Exists`|`@(MyItems->Exists())`|Filters a set of items to those that actually exist on disk.|
 |`GetPathsOfAllDirectoriesAbove`| `@(MyItems->GetPathsOfAllFilesAbove())`|Given a set of items, returns items representing all the ancestor directories. No order is guaranteed.|
 |`Reverse`|`@(MyItems->Reverse())`|Returns the items in reverse order.|
-|`AnyHaveMetadataValue`|`@(MyItems->AnyHaveMetadataValue("MetadataName", "MetadataValue"))` | Returns a `boolean` to indicate whether any item has the given metadata name and value. The comparison is case insensitive. |
+|`AnyHaveMetadataValue`|`@(MyItems->AnyHaveMetadataValue('MetadataName', 'MetadataValue'))` | Returns a `boolean` to indicate whether any item has the given metadata name and value. The comparison is case insensitive. |
 |`ClearMetadata`|`@(MyItems->ClearMetadata())` |Returns items with their metadata cleared. Only the `itemspec` is retained.|
-|`HasMetadata`|`@(MyItems->HasMetadata("MetadataName"))`|Returns items that have the given metadata name. The comparison is case insensitive.|
-|`Metadata`|`@(MyItems->Metadata("MetadataName"))`|Returns the values of the metadata that have the metadata name. The items returned have the same metadata as the source values.|
-|`WithMetadataValue`|`@(MyItems->WithMetadataValue("MetadataName", "MetadataValue"))`|Returns items that have the given metadata name and value. The comparison is case insensitive.|
+|`HasMetadata`|`@(MyItems->HasMetadata('MetadataName'))`|Returns items that have the given metadata name. The comparison is case insensitive.|
+|`Metadata`|`@(MyItems->Metadata('MetadataName'))`|Returns the values of the metadata that have the metadata name. The items returned have the same metadata as the source values.|
+|`WithMetadataValue`|`@(MyItems->WithMetadataValue('MetadataName', 'MetadataValue'))`|Returns items that have the given metadata name and value. The comparison is case insensitive.|
 
 > [!NOTE]
 > `Exists` can also be used in other contexts; in [MSBuild conditions](msbuild-conditions.md), for example `Condition="Exists('path')"`; or in [Static property functions](property-functions.md), for example `$([System.IO.File]::Exists("path"))`.
