# Encapsulation

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 its 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**.

```csharp
// 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);
	}
}
```

**Output:**

```
Name: Ankita
Age: 21
```

**Explanation:** In 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 contain 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.&#x20;

#### **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.
* Increases modularity and maintainability by making it easier to change the implementation without affecting other parts of the code.
* Allows for easy addition of new methods and fields without affecting the existing code.

#### Disadvantages of Encapsulation:

1. Can lead to increased complexity, especially if not used properly.
2. Can make it more difficult to understand how the system works.
3. May limit the flexibility of the implementation.

Encapsulation is a fundamental concept in object-oriented programming (OOP) that refers to the bundling of data and the methods that operate on that data within a single unit. In C#, this is typically achieved through the use of classes.

The idea behind encapsulation is to keep the implementation details of a class hidden from the outside world, and to only expose a public interface that allows users to interact with the class in a controlled and safe manner. This helps to promote modularity, maintainability, and flexibility in the design of software systems.

#### To demonstrate encapsulation in C#, let’s consider the following example:

```csharp
public class BankAccount {
	private decimal balance;

	public BankAccount(decimal initialBalance)
	{
		balance = initialBalance;
	}

	public void Deposit(decimal amount)
	{
		balance += amount;
	}

	public void Withdraw(decimal amount)
	{
		if (balance >= amount) {
			balance -= amount;
		}
		else {
			Console.WriteLine("Insufficient funds.");
		}
	}

	public decimal GetBalance() { return balance; }
}

class Program {
	static void Main(string[] args)
	{
		BankAccount myAccount = new BankAccount(1000);

		myAccount.Deposit(500);
		Console.WriteLine("Balance: "
						+ myAccount.GetBalance());

		myAccount.Withdraw(1200);
		Console.WriteLine("Balance: "
						+ myAccount.GetBalance());
	}
}
```

Output:

```
Balance: 1500
Insufficient funds.
Balance: 1500
```

In this example, we have a class BankAccount that represents a simple bank account with a balance that can be deposited into and withdrawn from. The balance field is marked as private, which means that it cannot be accessed directly from outside the class. Instead, we provide public methods Deposit, Withdraw, and GetBalance that provide a controlled interface to the balance field.

In the Main method, we create an object myAccount of the BankAccount class with an initial balance of 1000. We then call the Deposit and Withdraw methods to modify the balance, and the GetBalance method to retrieve the current balance. Note that we cannot access the balance field directly, but must use the public methods provided by the class to interact with it.



\
