Skip to content

Commit d5181e9

Browse files
committed
edits
1 parent 6fdb0c8 commit d5181e9

File tree

2 files changed

+9
-7
lines changed

2 files changed

+9
-7
lines changed

docs/msbuild/errors/msb4096.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ This error occurs when your MSBuild script uses a shorthand unqualified syntax t
3030

3131
## Resolution
3232

33-
You can also avoid this error by ensuring that all items of the given type define a value for the metadata. For more information, see [Item metadata](../msbuild-items.md#item-metadata).
33+
Ensure all items of the given type define a value for the metadata. For more information, see [Item metadata](../msbuild-items.md#item-metadata).
3434

3535
## Applies to
3636

docs/msbuild/errors/msb6004.md

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -30,13 +30,15 @@ This error occurs when an executable for a task isn't found. An MSBuild task tha
3030

3131
## Resolution
3232

33-
To resolve the error, try the following actions:
33+
Check the executable to make sure it's installed at the expected path.
3434

35-
- Check the executable to make sure it's installed at the expected path.
36-
- Look at the error that came from the tool associated with the MSBuild task, if any. For example, if the tool normally generates a log file, check the logs.
37-
- Check the installation of the package that provides the tool. For example, if the tool is a compiler, try reinstalling the compiler or package that provides the compiler. In this context, a package might mean a NuGet package, an OS package, a Visual Studio extension, or any other installed product.
38-
- Confirm the executable location is on the PATH environment variable, or that any other expected environment variables are set.
39-
- If your installation appears correct, check with the vendor that provides the tool to report the error.
35+
Look at the error that came from the tool associated with the MSBuild task, if any. For example, if the tool normally generates a log file, check the logs.
36+
37+
Check the installation of the package that provides the tool. For example, if the tool is a compiler, try reinstalling the compiler or package that provides the compiler. In this context, a package might mean a NuGet package, an OS package, a Visual Studio extension, or any other installed product.
38+
39+
Confirm the executable location is on the PATH environment variable, or that any other expected environment variables are set.
40+
41+
If your installation appears correct, check with the vendor that provides the tool to report the error.
4042

4143
## Applies to
4244

0 commit comments

Comments
 (0)