Expression Trees and Query Translation
Represent code as data with expression trees, distinguish delegates from translatable expressions, and build composable predicates without accidental client evaluation.
Before this lesson
Distinguish delegates from expression trees
Inspect and compose predicate nodes
Avoid unsupported provider translation
The short answer
A delegate is executable behavior; Expression<TDelegate> is a tree describing behavior. Providers inspect that tree to translate supported operations, while Compile turns it into executable code. Keep provider-facing expressions within the provider’s documented translation set.
Build the runtime mental model
A lambda can become either a delegate or an expression tree depending on the target type. Tree nodes describe parameters, constants, calls, comparisons, and other supported syntax. The tree is immutable; composition creates a new tree.
Advanced C# work improves when you separate language syntax, runtime behavior, and application policy. Write down which layer owns the guarantee in this lesson. Then identify the observable evidence—a compiler rejection, test result, generated query, trace, or measurement—that would prove the model correct.
Design the boundary deliberately
IQueryable providers use expression trees to build SQL or another remote query. IEnumerable uses compiled .NET behavior in memory. Cross that boundary intentionally because switching too early can download far more data than expected.
The starter isolates one part of the mental model so it can run in the browser. The exercise moves the same rule into a current local .NET project where packages, framework hosting, diagnostics, and multi-file tests are available.
using System;
using System.Linq.Expressions;
class Program
{
static void Main()
{
Expression<Func<int, bool>> rule = value => value >= 10;
Func<int, bool> compiled = rule.Compile();
Console.WriteLine(rule.Body.NodeType);
Console.WriteLine(compiled(12));
}
}Expected output
GreaterThanOrEqual True
Diagnose failure and misuse
Arbitrary .NET methods may not translate. Captured values become constants or closure access, and careless composition can produce parameters that are not the same node. Dynamic expression construction also creates injection-like policy risks if clients choose unrestricted members.
Classify each failure as a contract violation, transient operational failure, permanent dependency response, concurrency conflict, or programmer defect. That classification determines whether to reject, retry, compensate, cancel, or fail fast. A generic catch-and-continue policy destroys the information needed to make that decision.
| Question | Evidence to inspect | Decision |
|---|---|---|
| Is the input valid? | Validation result and boundary examples | Reject with a stable contract |
| Is the failure transient? | Typed status, exception, and policy context | Retry only when bounded and safe |
| Is state still consistent? | Invariant and transaction outcome | Commit, compensate, or abort |
| Is performance acceptable? | Representative latency and allocation data | Keep simple or optimize one cause |
Apply the concept in production
Log generated queries, constrain sortable and filterable fields through an allowlist, and test important expressions against the real provider. Prefer ordinary typed lambdas until runtime composition is a real requirement.
Finish by making the result operable. Add structured diagnostics at the boundary, propagate cancellation, avoid sensitive data, and record SDK and dependency versions. Test the public behavior instead of private implementation details. If a framework or provider performs translation, serialization, concurrency, or I/O, include at least one test against the real production technology.
A senior-level review should be able to answer four questions: what contract is promised, who owns lifetime and cleanup, how failures become visible, and what evidence supports the design. If any answer depends on “the framework probably handles it,” inspect the documentation or runtime behavior and turn the assumption into a checked decision.
Quick knowledge check
Answer before you reveal.
01What is the key difference between Func<T,bool> and Expression<Func<T,bool>>?
The delegate is executable code; the expression is inspectable data describing code that a provider may translate or compile.
02What must happen before adding complexity to this design?
State the requirement, preserve a correct baseline, collect evidence, and explain how the proposed mechanism improves a specific quality.
Exercise
Practice challenge
Build a safe product-filter expression from an allowlisted field and operator set, then test its compiled behavior and provider translation.
Requirements
- The implementation states its contract and ownership boundary explicitly
- Automated checks cover the successful path and at least two meaningful failures
- Diagnostics expose failure context without secrets or swallowed exceptions
- The project documents required SDK, packages, setup, run, and test commands
Optional extension: Measure or load-test the critical path and record whether the evidence justifies another optimization or abstraction.
Open in C# compilerLesson checkpoint
One small step locks it in
Mark this lesson complete, then keep the momentum going.
Clear up the details
Frequently asked questions
When should I use expression trees and query translation?
Use it when its explicit tradeoff solves a measured requirement or clarifies an owned boundary. Keep the simpler design when the additional mechanism does not improve correctness, operability, or changeability.
Does the browser compiler cover the complete production setup?
No. It runs the focused starter program. Framework, package, database, benchmark, and multi-project work requires a current local .NET SDK and the project commands described in the exercise.
What evidence should I keep after the exercise?
Keep the acceptance cases, automated tests, diagnostic or benchmark output where relevant, and a short decision note describing the chosen boundary and rejected alternative.