Assigning a LINQ query to a variable usually does not retrieve its results. It creates a description of the work to do; the work begins when you enumerate the sequence, for example with foreach. To run it at a chosen point and keep the results, call ToList() or ToArray(). What happens at execution time depends in part on whether the source is an in-memory IEnumerable<T> or a provider-backed IQueryable<T>.
Why assigning a LINQ query does not run it
For a sequence-producing query, the variable generally holds the operations needed to produce results, not the results themselves. Microsoft’s Introduction to LINQ Queries (C#) puts it plainly: “In other words, you don’t retrieve any data by creating a query variable.” Query creation and query execution are separate steps.
As an Amazon Associate I earn from qualifying purchases.
var query = numbers.Where(n => n % 2 == 0); // describes the filter
// No results have necessarily been read yet.
foreach (var n in query) // enumerates and runs it
Console.WriteLine(n);
var snapshot = query.ToList(); // runs now and stores resultsThe filter is applied when the sequence is enumerated. A foreach consumes its elements, triggering the deferred work.
Free tools Windows power users keep installed
One-click scans. No signup required.
What forces a query to execute?
Enumerating a sequence
A foreach is the usual trigger when you want to consume results one by one. Other consumers that enumerate a sequence can trigger it too. If the same deferred query is enumerated again, its work can run again; if the source has changed, the second run may produce different results.
Calling an immediate scalar operator
Operators such as Count(), Max(), Average(), and First() return a value rather than another sequence. They must inspect the sequence to produce that value, so execution happens as part of the call.
Materializing with a collection conversion
ToList() and ToArray() enumerate the source immediately and retain the resulting elements in a collection. This is useful when results are needed now or will be reused without rerunning the original query. The collection represents the results captured at materialization time; it does not automatically re-evaluate the query when its source later changes.
Rank #2
- Used Book in Good Condition
Conversion methods beginning with To enumerate to produce a result. By contrast, As methods change the static type without enumerating; they do not, by themselves, force the query to run.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Deferred execution does not always stream results
Deferred execution means work starts when the sequence is enumerated. It does not promise that each result can be produced immediately as input arrives. Microsoft’s LINQ query overview distinguishes streaming operators, such as Where and Select, from nonstreaming operators such as OrderBy.
Where can examine an input element and yield it if it matches. OrderBy must process and sort the full source before it can return the first ordered element. The query remains deferred until enumeration, but the enumeration does not necessarily yield its first result immediately.
How IEnumerable and IQueryable change the behavior
With LINQ to Objects, operators commonly work over IEnumerable<T>; their logic runs as the returned sequence is enumerated. An IQueryable<T> instead represents a query as an expression tree. A provider may translate that tree into a native query—for example, Entity Framework can translate LINQ to SQL. Translation capabilities and restrictions vary by provider, so an expression that works for an in-memory sequence may not be supported by a particular provider.
Rank #4
For provider-backed queries, enumeration or materialization is when the provider is asked to perform the requested work. That is why a provider-related error can appear at that point rather than when the query variable is created. Consult the documentation for the specific provider when investigating translation or database behavior; Microsoft explains the distinction in Standard Query Operators overview.
How to diagnose a query that appears not to run
- Check what the variable contains. Determine whether it is a sequence such as
IEnumerable<T>orIQueryable<T>, or a scalar value already returned by an operator such asCount(). - Consume the sequence once. Use
foreachwhen you want to process its elements, or callToList()orToArray()where you need a materialized collection. - Use side effects only as a diagnostic. A breakpoint or temporary observable effect in a predicate or projection can help confirm when it runs, but query expressions should not rely on side effects as normal program behavior.
- If an error appears during enumeration, inspect the source or provider. Deferred execution delays the work, and therefore can delay failures from the enumerator or provider as well.
- Check whether you enumerate more than once. A deferred query can rerun and see changed source data. Materialize it if you need to reuse a stable captured result.
Choose when to execute based on how you will use the results
| Approach | When work happens | Useful when | What to account for |
|---|---|---|---|
Enumerate with foreach |
When the sequence is consumed | You want to process values as a sequence | Enumerating again can run deferred work again and may observe changed source data. |
Call a scalar operator such as Count() or First() |
During the call, to produce its value | You need the scalar result | The operator must inspect the sequence as needed to return that value. |
Call ToList() or ToArray() |
During the call | You need to execute now and reuse the captured results | The selected results are retained in a collection; memory and performance effects depend on the workload. |
There is no universal memory or speed threshold that determines when to materialize. The practical choice is whether to defer work until consumption, whether repeated enumeration is acceptable, and whether retaining a collection of the results suits your workload.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
