All 11 Extension Methods questions
More in Extension Methods
How do you chain multiple extension methods together in a fluent style, and what design principle makes this possible? What are extension methods in C#, and how do they let you add functionality to a type you can't modify? How would you write an extension method on an interface (like IEnumerable<T>) that provides a default implementation shared across EVERY concrete implementing type? How would you write extension methods to build a lightweight, fluent validation/guard-clause library? How do 'extension method ambiguity' conflicts arise when two different NuGet packages or namespaces define extension methods with the identical signature, and how do you resolve them? How would you write generic extension methods leveraging C# 11's generic math interfaces (like INumber<T>) to build a single reusable numeric utility working across int, double, decimal, and other numeric types?
Advertisement
C# › Extension Methods

Why can't extension methods be used to add STATIC members, operators, or FIELDS to an existing type, and what are the practical implications of this limitation?

Advanced

Answer

Extension methods only extend the set of callable INSTANCE methods available on a type through syntactic sugar — they can't add actual state (fields), can't participate in operator overloading, and can't extend static method call syntax on the type itself, because none of these actually modify the type's real metadata; the extended type genuinely gains nothing at the runtime/reflection level.
public static class StringExtensions {
  // public static string EmptyValue = ""; // Error: can't add a static field this way
  // public static string operator +(string a, string b) => a + b; // Error: extension methods can't define operators
}
Real-world example Understanding why you must use inheritance, composition, or a wrapper type instead of extension methods when you genuinely need to add state to a type.

Common follow-ups: What alternative approaches exist when you need to attach genuinely new STATE to instances of an existing type you don't own?

OOP
All 11 Extension Methods questions