A derived object calls different methods depending on the variable's declared type. How do overloads, overrides, and new method hiding differ?

Overload resolution, overriding, and method hiding

Separates compile-time overload selection from runtime virtual dispatch and diagnoses method hiding through a base reference.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

Overloading means several methods share a name but have different parameter lists; the compiler chooses the best applicable overload from the argument expressions and their compile-time types. Overriding replaces a virtual or abstract base implementation, and runtime dispatch selects the most-derived override for the actual object. Declaring new hides a base member instead of participating in that virtual slot, so the chosen member depends on the variable's declared type. I use override for polymorphic behavior and avoid hiding unless the distinction is deliberate and clearly documented.

Full answer below

Practice focus

Compile-time overload resolution, runtime virtual dispatch, override contracts, new method hiding, static type, dynamic, optional parameters, and API evolution.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Why this question matters
Several C# features use the same method name but select behavior at different times. Predicting the call requires separating the compile-time candidate from runtime virtual dispatch.
Overloading means several methods share a name but have different parameter lists; the compiler chooses the best applicable overload from the argument expressions and their compile-time types. Overriding replaces a virtual or abstract base implementation, and runtime dispatch selects the most-derived override for the actual object. Declaring new hides a base member instead of participating in that virtual slot, so the chosen member depends on the variable's declared type. I use override for polymorphic behavior and avoid hiding unless the distinction is deliberate and clearly documented.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
If overrides , then calls the dog's override. If merely declares , the same base-typed call uses the base member, while a dog-typed variable sees the hidden member. Overload selection happens first: an overload accepting may be selected even when the runtime object is a dog, unless the selected member is itself virtual. A argument defers overload binding to runtime, but that trades compiler checking for runtime binder failures.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Assuming runtime type chooses among every overload automatically.
Using new when the design requires polymorphic override behavior.
Changing optional parameter defaults and expecting deployed callers to pick them up immediately.
Calling overridable members from a base constructor before derived state is initialized.

A derived object calls different methods depending on the variable's declared type. How do overloads, overrides, and new method hiding differ?

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue the section

Tech stacks

Skill areas

Suggest an improvement