Impove substituted strings in error messages and add links

ghogen · ghogen · commit c50d783ba4e7 · 2025-06-13T11:48:18.000-07:00
diff --git a/docs/msbuild/errors/msb3025.md b/docs/msbuild/errors/msb3025.md
@@ -27,7 +27,7 @@ This article describes the MSB3025 error code.
 ## Message text
 
 <!-- :::editable-content name="messageText"::: -->
-`MSB3025: The source file 'value' is actually a directory.  The 'Copy' task does not support copying directories.`
+`MSB3025: The source file 'path' is actually a directory.  The 'Copy' task does not support copying directories.`
 <!-- :::editable-content-end::: -->
 <!-- MSB3025: The source file "{0}" is actually a directory.  The "Copy" task does not support copying directories. -->
 
diff --git a/docs/msbuild/errors/msb3052.md b/docs/msbuild/errors/msb3052.md
@@ -27,7 +27,7 @@ This article describes the MSB3052 error code.
 ## Message text
 
 <!-- :::editable-content name="messageText"::: -->
-`MSB3052: The parameter to the compiler is invalid, ''value''value'' will be ignored.`
+`MSB3052: The parameter to the compiler is invalid, ''switch''value'' will be ignored.`
 <!-- :::editable-content-end::: -->
 <!-- MSB3052: The parameter to the compiler is invalid, '{0}{1}' will be ignored. -->
 
diff --git a/docs/msbuild/errors/msb3088.md b/docs/msbuild/errors/msb3088.md
@@ -27,7 +27,7 @@ This article describes the MSB3088 error code.
 ## Message text
 
 <!-- :::editable-content name="messageText"::: -->
-`MSB3088: Could not read state file 'filename'.`
+`MSB3088: Could not read state file 'file-path'.`
 <!-- :::editable-content-end::: -->
 <!-- MSB3088: Could not read state file "{0}". {1} -->
 
diff --git a/docs/msbuild/errors/msb3107.md b/docs/msbuild/errors/msb3107.md
@@ -27,7 +27,7 @@ This article describes the MSB3107 error code.
 ## Message text
 
 <!-- :::editable-content name="messageText"::: -->
-`MSB3107: The specified project reference metadata for the reference 'value' is missing or has an invalid value:`
+`MSB3107: The specified project reference metadata for the reference 'referenced-project-name' is missing or has an invalid value:`
 <!-- :::editable-content-end::: -->
 <!-- MSB3107: The specified project reference metadata for the reference "{0}" is missing or has an invalid value: {1} -->
 
diff --git a/docs/msbuild/errors/msb3217.md b/docs/msbuild/errors/msb3217.md
@@ -27,7 +27,7 @@ This article describes the MSB3217 error code.
 ## Message text
 
 <!-- :::editable-content name="messageText"::: -->
-`MSB3217: Cannot register assembly 'value'.`
+`MSB3217: Cannot register assembly 'assembly-name'.`
 <!-- :::editable-content-end::: -->
 <!-- MSB3217: Cannot register assembly "{0}". {1} -->
 
@@ -37,11 +37,11 @@ This article describes the MSB3217 error code.
 -->
 ## Description
 
-This error occurs in the [RegisterAssembly task](../registerassembly-task.md) when, for any reason, the assembly could not be registered as a COM object. The error is followed by information from Windows with more details about the issue.
+This error occurs in the [RegisterAssembly task](../registerassembly-task.md) when, for any reason, the assembly could not be registered as a COM object. The error is followed by information from Windows with more details about the issue. See [Registering assemblies with COM](/dotnet/framework/interop/registering-assemblies-with-com).
 
 ## Resolution
 
-This error occurs for a wide variety of causes that result in a failure to register an assembly. Registering a COM object requires that the account that runs MSBuild has admin permissions on the machine.
+This error occurs for a wide variety of causes that result in a failure to register an assembly. Registering a COM object requires that the account that runs MSBuild has admin permissions on the machine. 
 
 <!-- :::editable-content-end::: -->
 <!-- :::ErrorDefinitionDescription-end::: -->
diff --git a/docs/msbuild/errors/msb3331.md b/docs/msbuild/errors/msb3331.md
@@ -27,7 +27,7 @@ This article describes the MSB3331 error code.
 ## Message text
 
 <!-- :::editable-content name="messageText"::: -->
-`MSB3331: Unable to apply publish properties for item 'value'.`
+`MSB3331: Unable to apply publish properties for item 'item-name'.`
 <!-- :::editable-content-end::: -->
 <!-- MSB3331: Unable to apply publish properties for item "{0}". -->
 
diff --git a/docs/msbuild/errors/msb4075.md b/docs/msbuild/errors/msb4075.md
@@ -27,7 +27,7 @@ This article describes the MSB4075 error code.
 ## Message text
 
 <!-- :::editable-content name="messageText"::: -->
-`MSB4075: The project file 'value' must be opened in the Visual Studio IDE and converted to the latest version before it can be built by MSBuild.`
+`MSB4075: The project file 'file-path' must be opened in the Visual Studio IDE and converted to the latest version before it can be built by MSBuild.`
 <!-- :::editable-content-end::: -->
 <!-- MSB4075: The project file "{0}" must be opened in the Visual Studio IDE and converted to the latest version before it can be built by MSBuild. -->
 
diff --git a/docs/msbuild/errors/msb4244.md b/docs/msbuild/errors/msb4244.md
@@ -39,6 +39,8 @@ This article describes the MSB4244 error code.
 
 An SDK resolver assembly is an assembly that is loaded when an SDK is referenced in a project file. The purpose of the SDK resolver is to find and load the appropriate SDK. If this error occurs, it means that the resolver assembly couldn't be located or loaded.
 
+For general information on SDKs in MSBuild, see [Use MSBuild project SDKs](../how-to-use-project-sdk.md).
+
 ## Resolution
 
 This error should never occur if you're using `dotnet build` or Visual Studio to build, but it could occur in a custom tool that uses the MSBuild API to perform a build and doesn't locate the right MSBuild installation files. The recommended way to locate MSBuild is to use <xref:Microsoft.Build.Locator.MSBuildLocator>. For detailed instructions, see [Find and use MSBuild versions](../find-and-use-msbuild-versions.md).
diff --git a/docs/msbuild/errors/msb4252.md b/docs/msbuild/errors/msb4252.md
@@ -27,14 +27,14 @@ This article describes the MSB4252 error code.
 ## Message text
 
 <!-- :::editable-content name="messageText"::: -->
-`MSB4252: Project 'value' with global properties
-    ('value')
-    is building project 'value' with global properties
-    ('value')
-    with the ('value') target(s) but the build result for the built project is not in the engine cache. In isolated builds this could mean one of the following:
-    - the reference was called with a target which is not specified in the ProjectReferenceTargets item in project 'value'
+`MSB4252: Project 'project-name' with global properties
+    ('properties')
+    is building project 'project-name' with global properties
+    ('properties')
+    with the ('target-name') target(s) but the build result for the built project is not in the engine cache. In isolated builds this could mean one of the following:
+    - the reference was called with a target which is not specified in the ProjectReferenceTargets item in project 'project-name'
     - the reference was called with global properties that do not match the static graph inferred nodes
-    - the reference was not explicitly specified as a ProjectReference item in project 'value'`
+    - the reference was not explicitly specified as a ProjectReference item in project 'project-name'`
 <!-- :::editable-content-end::: -->
 <!-- MSB4252: Project "{0}" with global properties
     ({1})
diff --git a/docs/msbuild/errors/msb5023.md b/docs/msbuild/errors/msb5023.md
@@ -27,7 +27,7 @@ This article describes the MSB5023 error code.
 ## Message text
 
 <!-- :::editable-content name="messageText"::: -->
-`MSB5023: Error parsing the nested project section in solution file. A project with the GUID 'value' is listed as being nested under project 'value', but does not exist in the solution.`
+`MSB5023: Error parsing the nested project section in solution file. A project with the GUID 'guid' is listed as being nested under project 'project-name', but does not exist in the solution.`
 <!-- :::editable-content-end::: -->
 <!-- MSB5023: Error parsing the nested project section in solution file. A project with the GUID "{0}" is listed as being nested under project "{1}", but does not exist in the solution. -->
 
