मुख्य सामग्रीवर वगळा

Enacpsulation in C#




Encapsulation is defined as the wrapping up of data under a single unit. It is the mechanism that binds together code and the data it manipulates. In a different way, encapsulation is a protective shield that prevents the data from being accessed by the code outside this shield.
  • Technically in encapsulation, the variables or data of a class are hidden from any other class and can be accessed only through any member function of own class in which they are declared.
  • As in encapsulation, the data in a class is hidden from other classes, so it is also known as data-hiding.
  • Encapsulation can be achieved by: Declaring all the variables in the class as private and using C# Properties in the class to set and get the values of variables.
// C# program to illustrate encapsulation
using System;
public class DemoEncap {

 // private variables declared
 // these can only be accessed by
 // public methods of class
 private String studentName;
 private int studentAge;

 // using accessors to get and
 // set the value of studentName
 public String Name
 {

  get
  {
   return studentName; 
  }

  set
  {
   studentName = value;
  }

 }

 // using accessors to get and
 // set the value of studentAge
 public int Age
 {

  get
  {
   return studentAge; 
  }

  set
  {
   studentAge = value;
  }

 }

}
// Driver Class
class GFG {

 // Main Method
 static public void Main()
 {

  // creating object
  DemoEncap obj = new DemoEncap();
  // calls set accessor of the property Name,
  // and pass "Ankita" as value of the
  // standard field 'value'
  obj.Name = "Ankita";

  // calls set accessor of the property Age,
  // and pass "21" as value of the
  // standard field 'value'
  obj.Age = 21;
  // Displaying values of the variables
  Console.WriteLine("Name: " + obj.Name);
  Console.WriteLine("Age: " + obj.Age);
 }
}
n the above program the class DemoEncap is encapsulated as the variables are declared as private. To access these private variables we are using the Name and Age accessors which contains the get and set method to retrieve and set the values of private fields. Accessors are defined as public so that they can access in other class.
Advantages of Encapsulation:
  • Data Hiding: The user will have no idea about the inner implementation of the class. It will not be visible to the user that how the class is stored values in the variables. He only knows that we are passing the values to accessors and variables are getting initialized to that value.
  • Increased Flexibility: We can make the variables of the class as read-only or write-only depending on our requirement. If we wish to make the variables as read-only then we have to only use Get Accessor in the code. If we wish to make the variables as write-only then we have to only use Set Accessor.
  • Reusability: Encapsulation also improves the re-usability and easy to change with new requirements.
  • Testing code is easy: Encapsulated code is easy to test for unit testing.

टिप्पण्या

या ब्लॉगवरील लोकप्रिय पोस्ट

Dependency Inversion Principle, Dependency Injection and Inversion Of Control

Dependency Inversion Principle, Dependency Injection and Inversion Of Control I’m a big fan of Dependency Injection pattern since it allows me to create more testable, maintainable and loosely coupled components. While it is easy to apply this pattern if you’ve seen some code samples you need more time to understand principles and terms around this pattern. In this article I will try to illustrate differences between those terms and explain how they come to work together. I will use well known car/engine example in this article but any example with dependency will do. All examples are written in C# language. Let’s first define few example classes: public class Engine { } public class Car { private Engine _engine ; public Car ( ) { _engine = new Engine ( ) ; } } n the example above we can see that Car (higher level component) depends on Engine (lower level component). At some point we may need to make car more reusable, for examp...
How To Customize Password Policy in ASP.Net Identity   Nimit Joshi   Jan 17  2014   Article 3 9 132.8k facebook twitter linkedIn google Plus Reddit Expand Download Free Office API Introduction Microsoft has released a new version of ASP.NET Identity, 2.0.0-alpha 1. You can refer to  ASP.NET Identity Preview  to get the idea of this release. In that context, we are here today to create a MVC application using ASP.NET Identity to customize the password to provide better security to the application. You'll learn here to modify the minimum length of the password and to make the entering of numeric and special characters in the password mandatory and disallow recently used passwords. By default the ASP.NET Identity requires that the minimum length of the password is 6 characters and here we change it to 8. We'll work on the Visual Studio 2013 version and you must update all the assemblies rela...