Skip to main content

Simple Object Oriented Programming (OOP) Concepts with Examples Part 1

Let's begin with a simple base class and derived class, and explain how the both are working.

Let's create a Base Class with the constructor taking no parameters,


        class BaseClass1

        {

            public BaseClass1()

            {

                Console.WriteLine("In BaseClass1 constructor");

            }

        }

 

 And Creating a Derived Class DerivedClass1  which inherits Base class BaseClass1

 

        class DerivedClass1 : BaseClass1

        {

            public DerivedClass1()

            {

                Console.WriteLine("In DerivedClass1 constructor");

            }

        }

And in the Main Function just create an object for the BaseClass1 

            BaseClass1 BC1Obj = new BaseClass1();

Now the output will be 

            In BaseClass1 constructor

While trying to create another object for 

            BaseClass1 BC1Obj2 = new DerivedClass1();

Now the output will be 

            In BaseClass1 constructor
            In DerivedClass1 constructor

While trying to create another object for   

            DerivedClass1 DC1Obj1 = new DerivedClass1();

Now the output will be  

            In BaseClass1 constructor
            In DerivedClass1 constructor

 

This is the order of execution of constructors if we are using inheritance, 

 

A detailed video has been posted in Youtube with the Examples:

https://youtu.be/ojxTJ4FPFnY

 

Source Code Link : https://github.com/oneananda/C_Sharp_Examples/blob/main/OOP_Examples_1/Program.cs

Let's see in the next part

 



Comments

Popular posts from this blog

Using of global variables in C# - Drawbacks & Solutions

How using global variables can have implications on the design, maintainability, and test-ability of C# code: Harder to understand and reason about the code:       class Program     {         public static int globalCounter = 0;         static void Main()         {             globalCounter++;             Console.WriteLine(globalCounter);         }     }   In this example, the global variable globalCounter is accessible from anywhere in the program, including the Main method. It's not clear where the value of the globalCounter is updated, it could be updated in other methods or classes, making it harder to trace the flow of data and understand the source of bugs.   More prone to errors:       class Program     {         public static string globalString;         static void Main()         {             globalString = "Hello" ;             Method1();             Method2();         }         static void Method1()         {

Task Parallel Library (TPL) and Akka.NET Alternatives

Task Parallel Library (TPL) and Akka.NET are among the most commonly used libraries for parallel and concurrent programming in the .NET ecosystem. However, there are also several other options available, depending on your specific needs: Parallel Language Integrated Query (PLINQ) is a parallel programming feature of .NET that provides an easy and efficient way to perform operations on collections in parallel. LINQ (Language Integrated Query) is a powerful feature in .NET that allows developers to work with data in a more declarative and language-integrated manner. While LINQ queries are inherently sequential, PLINQ extends LINQ by providing parallel versions of the query operators, allowing some queries to execute faster by utilizing multiple processors or cores on a machine. PLINQ is great when you are working with large collections where operations might be CPU-intensive or I/O-bound and could potentially be sped up by parallel execution. Here is a simple example of a PLI

SOLID Principles with Real World examples in C#

  SOLID Principles with Real World examples in C#   SOLID principles are formed by using S Single Responsibility Principles (SRP) O Open Closed Principle (OCP) L Liskov’s Substitution Principle (LCP) I Interface Segregation Principle (ISP) D Dependency Inversion Principle (DIP)   S Single Responsibility Principles (SRP) There should never be more than one reason for a class to change, to be precise one class should have only one responsibility Single Responsibility Principles (SRP) Real world example, A perfect match for SRP is Microservices , a Microservice will not contain functionalities other than the one it is designated to do,  Example ·                   Order Processing Service, ·                   Shipment Management Service, ·                   User Authentication Service, ·                   Catalogue List Service       class OrderProcessor     {         public void Process(Order order)         {             // Check inven