Skip to main content

OOPs...

OOPs or Object Oriented Programming is an approach that puts object at the center of programming model. An object is a self contained entity that has a state and behaviour. State is described by fields and properties, while behavior is defined by methods and events. Object is an instance of a class. 

A class acts like a blueprint for the object. It defines behavior of object of that type.So all objects of type Vehicle will have the same behavior.

Vehicle class will have the properties - 'color' , 'weight', 'model', 'make' . Properties are characteristic shared by all objects of a particular class.  Methods are actions of an object - 'start', 'stop'

Constructors are special kinds of methods, used to initialize objects. It executes automatically when a class is instantiated

Access modifies helps in controlling the visibilty of a class.
* Public allows the property or methods to be called outside the class
* Private fields and methods cannot be used outside the class
* Protected members are accessible from within the class, or any code derived from it

To fully understand the concept, lets consider another example
public class Employee               //class definition
    {
        private string _name ;        // fields

        public Employee()            //constructor
        {
           _name = "Test";
        }

        public AddEmployee()      //method
        {
           //code to add employee
        }
}

Here Employee is a class which is public. We can access all the methods and properties of this class. For convenience we have only created one method and one property, a class may have more than 1.

We can create an instance of this class as follows:
Employee emp1 = new Employee();

Here, emp1 is the object of this class and will have all the features of this class. So emp1 has a name which can be accessed as : emp1.name  Similarly, AddEmployee() method can be accessed using emp1.AddEmployee()

 OOPs helps in modular programming and understanding classes and objects is the 1st step towards it.

Comments

Popular posts from this blog

Insufficient access rights to perform the operation. (Exception from HRESULT: 0x80072098)

While accessing the active directory (AD) and authorization manager (AZMAN) , If you get “   Insufficient access rights to perform the operation. (Exception from HRESULT: 0x80072098)  “ message check the    account that is being used to get the LDAP query from AD .  ERROR DETAILS Exception Details:  System.Runtime.InteropServices.COMException: Insufficient access rights to perform the operation. (Exception from HRESULT: 0x80072098) Source Error: Line 154:    'Session("FullName") = System.Security.Principal.WindowsIdentity.GetCurrent.Name.ToString() Line 155: Line 156:    If Not User.IsInRole("Role1") Then Line 157:          Response.Redirect("./Login.aspx") Line 158:    End If  Stack Trace : .... SOLVE IT Steps to do check the app pool rights: Click on the website name that you are having problem with in IIS  In the right panel you will see 'Basic Settings'. Click It. Select the specific pool option and enter the name of the ac

Sql Server database Read_Only / Read_Write

The ALTER DATABASE command allows a database administrator to modify SQL Server databases and their files and filegroups. This includes permitting the changing of database configuration options. Why Read Only ? When you need to ensure that the data is a database is not modified by any users or automated processes, it is useful to set the database into a read-only mode. Once read-only, the data can be read normally but any attempts to create, updated or delete table rows is disallowed. This makes the read-only mode ideal when preparing for data migration, performing data integrity checking or when the data is only required for historical reporting purposes. Make Database Read Only USE  [master] GO ALTER DATABASE  [TESTDB]  SET  READ_ONLY  WITH  NO_WAIT GO Make Database Read/Write USE  [master] GO ALTER DATABASE  [TESTDB]  SET  READ_WRITE  WITH  NO_WAIT GO In case you get the following error message make the database single user: Msg 5070, Level 16, Stat

Do's and Don't SQL

Do's: Writing comments whenever something is not very obvious, as it won’t impact the performance.  (--) for single line  (/*…*/) to mark a section Use proper indentation Use Upper Case for all SQL keywords. SELECT, UPDATE, INSERT, WHERE, INNER JOIN, AND, OR, LIKE. Use BEGIN... END block for multiple statements in conditional code  Use Declare and Set in beginning of Stored procedure Create objects in same database where its relevant table exists otherwise it will reduce network performance. Use PRIMARY key in WHERE condition of UPDATE or DELETE statements as this will avoid error possibilities. If User table references Employee table than the column name used in reference should be UserID where User is table name and ID primary column of User table and UserID is reference column of Employee table. Use select column name instead of select * Use CTE (Common Table Expression); its scope is limited to the next statement in SQL query, instead of temporary tables and der