eval-performance

To fix slow MSBuild evaluation performance, you must diagnose bottlenecks using binlogs and preprocessing, then optimize glob patterns and reduce complex project import chains to improve build start times.

High evaluation times during .NET build starts are typically caused by inefficient globbing patterns, deeply nested import chains, and excessive directory scanning during the MSBuild project evaluation phase.

You can analyze MSBuild import chains by examining binlogs to understand the project structure, allowing you to identify and reduce unnecessary complexity that directly slows down the build evaluation process.

The best way to optimize globbing patterns for MSBuild projects is to refine globs and explicitly exclude unnecessary directories, which prevents the evaluation engine from scanning irrelevant files and reduces evaluation time.

Yes, you need MSBuild binlogs to diagnose .NET evaluation bottlenecks effectively, as they provide the detailed evaluation phase data and import chain visibility required to pinpoint exact performance pitfalls.