Skip to content

Commit 325719c

Browse files
Merge pull request #13200 from ghogen/msbuild-error-4025
Recommend diagnostic logs
2 parents 7967ded + a5b6f6d commit 325719c

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

docs/msbuild/errors/msb4025.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -18,12 +18,14 @@ ms.subservice: msbuild
1818
---
1919
# MSB4025
2020

21-
This error occurs when MSBuild tries to load and parse a project, but the project file or MSBuild import file could not be loaded. The file must be an XML MSBuild file, such as a validly formatted project file, `.props` file, or `.targets` file, or a file with any other extension that contains XML that is intended to be interpreted by MSBuild.
21+
This error occurs when MSBuild tries to load and parse a project, but the project file or MSBuild import file could not be loaded. The file must be an XML MSBuild file, such as a validly formatted project file, `.props` file, or `.targets` file, or a file with any other extension that contains XML that is intended for MSBuild to interpret.
2222

2323
The message resembles the following, but this text might be followed by additional information:
2424

2525
```output
26-
MSB4024: The imported project file 'filename' could not be loaded.
26+
MSB4024: The imported project file could not be loaded.
2727
```
2828

29-
Look to the additional information provided to determine the cause of the problem. Typical causes include the project file is missing, has an incorrect path, or is misspelled; unauthorized access; XML parsing errors in the project file; or it's open and locked by another program.
29+
If it's not obvious what imported file caused the problem, rerun the build with full diagnostic logs (use the `-verbosity:diag` command-line switch), and check the MSBuild log file. 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.
30+
31+
Look to the additional information provided to determine the cause of the problem. Typical causes include the project file is missing, has an incorrect path, or is misspelled; unauthorized access; XML parsing errors in the project file; or it's open and locked by another program.

0 commit comments

Comments
 (0)