Abstract methods and hiding methods

Question 1

I'm trying to understand abstract classes in c# better.

OK, then lets correct your mistakes, because you have some completely wrong ideas about abstract classes here.

I know that in abstract classes you MUST override abstract methods and MAY override virtual methods.

Absolutely not; the first part of that sentence is completely wrong. There is no requirement whatsoever in an abstract class to override an abstract method.

A non-abstract class is called a concrete class. The real rules are:

A concrete class must override all abstract methods of all its abstract base classes with concrete methods; it can do so either itself, or via one or more of its base classes.

This should make sense: you can't make an instance of a concrete class until every abstract method is implemented; otherwise you could invoke a method that has no implementation, and that would be bad.

Any derived class may override a non-sealed virtual method of any of its base classes.

can I override non virtual methods?

No. You can overload non-virtual methods and you can hide existing non-virtual methods, but you cannot override them.

it seems to me that because non virtual methods statically linked at compile time and can't be changed - I would not be able to call the methods in the derived class ,never?

Of course not. You call the methods of the derived class by converting the receiver to the derived class.

what is the point of hiding a method?

Duplicate of:

Is method hiding ever a good idea

Here's a BONUS QUESTION that you did not ask. See if you can answer it.

Can a method be marked as both abstract and override? If no, why not? If yes, give an example and explain why you would want to.

If you can answer that question correctly then you probably have a good understanding of abstract methods. The solution is here.

Question 2

No, you can't. They must have virtual keyword. Good example here,similar This one as well

Question 3

I would advise taking a closer look into what you can do with OOP

In reference to your question, you can only override a virtual class, another of example instead of hiding methods would be:

However you can use inheritance, to use the controls from your base class. This should be done when both classes are related, to prevent creating duplicate code.

An example of this would be an individual person : Human, okay so here we use ('type of' :) stating that a person is a type of human. This is the basic use of inheritance.

This shouldn't be done if they are not related, this may seem quicker when you are doing it, however when you look back at your application 3months on you will say "Why did I do that?".

An example of this would be, this base class has a method close to what I am looking for, you need to make a comparison, is it Really? Should I actually do this?

The msdn article provided will give you the information you need to progress with this. Enjoy OOP

Question 4

You have a little misunderstanding:

in abstract classes you MUST override abstract methods and MAY override virtual methods.

That sentence should really be:

in concrete classes that derive from an abstract class, you MUST override abstract methods and MAY override virtual methods, either in that class itself, one of its parent classes, or one of its subclasses.

You can use the new keyword to shadow, or hide, non-virtual methods, so yes it will be hiding and not overriding.

If you hide a method in a subclass, and then want to call the method as it appeared in the base class, cast the subclass as the to the base class type, as done in the second example here.