Real life usage of new keyword to hide virtual method implementation? c#

Question

What's the real life scenario where we will use new to provide new implementation for a virtual method in the derived class? C#

I know what it means technically. what I am looking for is a real life scenario where this will be needed.

We can always achieve the same by providing the override functionality. Why would we want to incorrect method been picked when methods call is made casted to base.

Answer 1

No. You can't achieve the same.

// Define the base class
class Car
{
    public virtual void DescribeCar()
    {
        System.Console.WriteLine("Four wheels and an engine.");
    }
}

// Define the derived classes
class ConvertibleCar : Car
{
    public new virtual void DescribeCar()
    {
        base.DescribeCar();
        System.Console.WriteLine("A roof that opens up.");
    }
}

class Minivan : Car
{
    public override void DescribeCar()
    {
        base.DescribeCar();
        System.Console.WriteLine("Carries seven people.");
    }
}

Now, if you try to do this:

public static void TestCars2()
{
    Car[] cars = new Car[3];
    cars[0] = new Car();
    cars[1] = new ConvertibleCar();
    cars[2] = new Minivan();
}

The result will be:

Car object: YourApplication.Car

Four wheels and an engine.

----------

Car object: YourApplication.ConvertibleCar

Four wheels and an engine.

----------

Car object: YourApplication.Minivan

Four wheels and an engine.

Carries seven people.

----------

Override ALWAYS override while new ONLY does it when is used as its declared type (not base one).

You can see more here