Private Construct in C#

A private constructor is a special instance constructor. It is commonly used in classes that contain static members only. If a class has one or more private constructors and no public constructors, then other classes (except nested classes) are not allowed to create instances of this class. 

For example:

public class Customer

    {

        private Customer()

        {

        }

        public static string getCustomerName()

        {

            return "Hello World";

        }

    }

Access this getCustomerName() Function

class AccessCustomer

{

    static void Main()

    {

string a;

a = Customer.getCustomerName();

System.Console.WriteLine("Customer Private Constructor: {0}",a);

    }

}

OUTPUT

Hello World

• you can not inherit the class or you can not create a object of class which has private constructor.

• which condition use private constructor

• Many time we do not want to create instance of certain classes like utility, common routine of classes.

Hope you liked my article. Please stay with me I will share more article with you.

Cheer 

MVC Architecture Fundamental

The main aim of the MVC architecture  is to separate the business logic and application data from the presentation data to the user.
Here are the reasons why we should use the MVC design pattern. 1. They are resuable : When the problems recurs, there is no need to invent a new solution, we just have to follow the pattern and adapt it as necessary. 2. They are expressive: By using the MVC design pattern our application becomes more expressive.

1)Model: The model object knows about all the data that need to be displayed. It is model who is aware about all the operations that can be applied to transform that object. It only represents the data of an application. The model represents enterprise data and the business rules that govern access to and updates of this data. Model is not aware about the presentation data and how that data will be displayed to the browser.

2)View : The view represents the presentation of the application. The view object refers to the model. It uses the query methods of the model to obtain the contents and renders it. The view is not dependent on the application logic. It remains same if there is any modification in the business logic. In other words, we can say that it is the responsibility of the of the view's to maintain the consistency in its presentation when the model changes.

3)Controller: Whenever the user sends a request for something then it always go through the controller. The controller is responsible for intercepting the requests from view and passes it to the model for the appropriate action. After the action has been taken on the data, the controller is responsible for directing the appropriate view to the user. In  GUIs, the views and the controllers often work very closely together.