The existing documentation made an overly absolute statement about method calls in expression trees, claiming that query providers "can't replicate the method's function" when they don't recognize a method call. This was inaccurate because many query providers can handle specific method calls by translating them appropriately.

Changes Made

Updated the documentation in docs/csharp/language-reference/operators/lambda-expressions.md to:

1. Replace absolute language with conditional guidance: Changed from "Otherwise, the query provider can't replicate the method's function" to explaining that support depends on the provider's capabilities
2. Add concrete example: Mentioned that SQL-based providers can translate String.StartsWith to LIKE expressions
3. Improve accuracy: Used "you should limit method calls to those methods that the query provider can handle" instead of the previous phrasing

Before

However, when creating expression trees evaluated by a query provider, limit method calls to those methods recognized by the query provider. Otherwise, the query provider can't replicate the method's function.

After

However, when creating expression trees evaluated by a query provider, you should limit method calls to those methods that the query provider can handle. Different query providers have varying capabilities—for example, many SQL-based providers can translate methods like String.StartsWith into appropriate SQL expressions such as LIKE. If a query provider doesn't recognize a method call, it can't translate or execute the expression.

This change makes the documentation more accurate and helpful by acknowledging that method call support varies by provider rather than being universally impossible.

Fixes #13323.

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Internal previews