eval-performance

Capture a binlog and use the binlog MCP evaluations tool to list evaluation durations, or replay the log with -flp:v=diag and grep for evaluation started/finished events. Confirm evaluation is the bottleneck before changing any project configuration.

Use DefaultItemExcludes to exclude large directories like node_modules, .git, bin, and obj from glob expansion. Prefer specific paths like src/**/*.cs over **/*.cs, and only disable EnableDefaultItems as a last resort.

A project is evaluated once per unique set of global properties, so references from multiple projects with differing global properties cause repeated evaluations. Normalize global properties or use graph build with /graph to reduce redundant evaluations.

Do not apply it when slowness occurs during compilation or target execution, or when the issue is incremental rebuild behavior. Also skip changes when measurements show evaluation is already fast, even if broad globs or deep imports exist.

Property functions run during evaluation, so file I/O like $([System.IO.File]::ReadAllText(...)) executes on every evaluation and adds real cost. Property functions should be fast and side-effect-free; avoid network calls and heavy computation.