🔒 Encapsulation = Hide Internal State
Public fields break encapsulation. Private fields + public properties protect data. Validation, computed values, change tracking.
❌ No Encapsulation
public class User
{
public string Name; // Direct access
public int Age; // No validation
}
// Any code can set invalid values
user.Age = -5; // Valid but wrong
✅ Encapsulation
public class User
{
private string _name;
private int _age;
public string Name
{
get => _name;
set => _name = value?.Trim() ?? throw new ArgumentException();
}
public int Age
{
get => _age;
set
{
if (value < 0 || value > 150)
throw new ArgumentException();
_age = value;
}
}
}
🎯 Encapsulation Benefits
// Validation
public class Person
{
private string _name;
public string Name
{
get => _name;
set
{
if (string.IsNullOrWhiteSpace(value))
throw new ArgumentException("Name is required");
_name = value;
}
}
}
// Computed value
public class Order
{
private List _items = new();
public decimal Total => _items.Sum(i => i.Price * i.Quantity);
}
// Change tracking
public class Entity
{
private bool _isModified;
public bool IsModified => _isModified;
private string _name;
public string Name
{
get => _name;
set
{
if (_name != value)
{
_name = value;
_isModified = true;
}
}
}
}
💡 OOP Principles
- Encapsulation: Hide internal state
- Abstraction: Show only what’s needed
- Inheritance: Reuse code
- Polymorphism: Different behaviors
“Encapsulation prevents invalid data. Validation in property setters. Essential for data integrity.”
