📁 One Class, Multiple Files
Large classes are hard to manage. Partial classes split across files. Generated code and custom code separate.
📝 Partial Class Example
// File 1: User.cs (main class)
public partial class User
{
public int Id { get; set; }
public string Name { get; set; }
public string Email { get; set; }
}
// File 2: User.Validation.cs (validation methods)
public partial class User
{
public bool IsValidEmail()
{
return Email.Contains("@") && Email.Contains(".");
}
public bool IsValidName()
{
return !string.IsNullOrWhiteSpace(Name);
}
}
// File 3: User.Database.cs (database methods)
public partial class User
{
public async Task SaveAsync()
{
// Save user to database
}
}
🎯 Generated Code
// Generated by Entity Framework
// User.g.cs
public partial class User
{
public int Id { get; set; }
public string Name { get; set; }
public string Email { get; set; }
public DateTime CreatedAt { get; set; }
}
// Custom code
// User.cs
public partial class User
{
public string DisplayName => $"{Name} ({Email})";
public void UpdateEmail(string newEmail)
{
if (IsValidEmail(newEmail))
{
Email = newEmail;
}
}
private bool IsValidEmail(string email)
{
return email.Contains("@");
}
}
💡 Use Cases
- Generated code (Entity Framework, WCF, Web Services)
- Team collaboration (different developers work on same class)
- Organizing large classes
- Separating concerns (logic, data, validation)
- Designer code separation (WinForms, WPF)
“Partial classes keep generated code separate from custom code. Essential for Entity Framework and WCF.”


