One name many forms

public class AppleBase  

   {  

       public AppleBase()  

       {

           Console.WriteLine("1. Base class: AppleBase");  

       }  

   } 



The derived class: MacBook. It is also printing a message in its constructor.

1. 
   class MacBook : AppleBase  
   
2. 
      {  
   
3. 
          public MacBook()  
   
4. 
          {  
   
5. 
              Console.WriteLine("2. Derived class: MacBook");  
   
6. 
          }  
   
7. 
      } 
   
   
   

Now if I create an object of MacBook. what do you think what will happen?

1. 
   class Program  
   
2. 
      {  
   
3. 
          static void Main(string[] args)  
   
4. 
          {  
   
5. 
              MacBook macBook = new MacBook();  
   
6. 
          }  
   
7. 
      } 
   
   
   

Let's see what will happen.

 

 

Analyze the output, even if we create an object of a MacBook, Compiler still calls an AppleBase class's constructor prior to MacBook's.

 

This concept is known as constructor chaining. 

 

What did this tell us?

 

Exactly my thoughts. which means we do have another way to call a constructor. 

 

Object creation does not hold a monopoly over constructor executions, Right?

 

So what do we know?

• 
  We know that Abstract classes can have constructors.
  
• 
  And we can not instantiate an abstract class.
  

What did we learn?

• 
  We can call the Abstract class's constructor through constructor chaining.
  

 Let's have our abstract class back and let's have an abstract method to define the name of the product.

1.