optimizing-msbuild-performance

Profile first using the /profileevaluation flag, BenchmarkDotNet, or ETW traces to find real bottlenecks. Then minimize import chain depth, avoid overly broad glob patterns, and order condition checks so cheap evaluations short-circuit first.

Replace LINQ operators like Where and First with foreach loops to avoid enumerator and closure allocations. Use Span<T> and stackalloc for short-lived buffers, cache computed values outside loops, and prefer TryGetValue over ContainsKey plus indexer.

Use MSBuildNameIgnoreCaseComparer for property, item, and target names and as dictionary key comparers. Never use ToLower or ToUpper for comparisons since they allocate new strings, and never use CurrentCulture for MSBuild identifiers.

ImmutableArray<T> is almost always the right choice for build-once, read-many collections because it offers O(1) indexed access. ImmutableList<T> has O(log n) access time and is rarely appropriate for performance-critical code.

string.Format allocates a new string even when the log message is filtered out by verbosity level. Use structured logging or guard the call with a verbosity check so allocation only happens when the message will actually be written.

Apply MethodImplOptions.AggressiveInlining only to small methods called millions of times in extremely hot paths. Also consider avoiding virtual dispatch in inner loops and using struct enumerators to eliminate heap allocation.