Why does LINQ behave unpredictably when combined with reflection-based projections?

Reflection inside LINQ breaks translation and often forces client-side evaluation.

LINQ providers cannot translate reflection-based logic into SQL because reflection executes at runtime in .NET context. When used inside IQueryable, this breaks translation and either throws exceptions or forces full client-side execution. This leads to performance degradation and unpredictable behavior.