Partial Classes In C# with Real Example

Partial Class in C#

In this article, I explain partial classes in C# language with examples. A partial class splits the definition of a class over two or more source (.cs) files. You can create a class definition in multiple physical files but it will be compiled as one class when the classes are compiled.

Suppose you have a “Person” class. That definition is divided into two physical source files, Person1.cs and Person2.cs. Then these two files have a class that is a partial class. You compile the source code and then create it in a single class. Let's see that in Figure 1.

Figure 1: Partial class and compiled class

Advantages of a partial class

Here is a list of some of the advantages of partial classes.

1. You can separate UI design code and business logic code so that it is easy to read and understand. For example, if you are developing a web application using Visual Studio and adding a new web form then there are two source files, “aspx.cs” and “aspx.designer.cs”. These two files have the same class with the partial keyword. The “.aspx.cs” class has the business logic code while “aspx.designer.cs” has the user interface control definition.

2. When working with an automatically generated source, the code can be added to the class without having to recreate the source file. For example, you are working with LINQ to SQL and create a DBML file. Now when you drag and drop a table it creates a partial class in designer. cs and all table columns have properties in the class. You need more columns in this table to bind on the UI grid but you don't want to add a new column to the database table so you can create a separate source file for this class that has a new property for that column and it will be a partial class. So that does affect the mapping between the database table and DBML entity but you can easily get an extra field. It means you can write the code on your own without messing with the system-generated code.

3. More than one developer can simultaneously work the code for the same class.

4. You can maintain your application better by compacting large classes. Suppose you have a class that has multiple interfaces so you can create multiple source files depending on interface implementation. It is easy to understand and maintain an interface implemented on which the source file has a partial class. Let's see the following code snippet.

   public interface IRegister    
   {    
       //Register realted function    
   }    
   public interface ILogin    
   {    
       //Login related function    
   }    
   //UserRegister.cs file    
   public partial classUser : IRegister, ILogin    
   {    
       //implements IRegister interface    
   }    
   //UserLogin.cs file    
   public partial classUser    
   {    
       //implements ILogin interface    
   }

Points that you should be careful about partial classes

There are some points that you should be when you are developing a partial class in your application.

1. You need to use a partial keyword in each part of the partial class.
2. The name of each part of the partial class should be the same but the source file name for each part of the partial class can be different.
3. All parts of a partial class should be in the same namespace.
4. Each part of a partial class should be in the same assembly or DLL, in other words, you can't create a partial class in source files of a different class library project.
5. Each part of a partial class has the same accessibility.
6. If you inherit a class or interface on a partial class then it is inherited on all parts of a partial class.
7. If a part of a partial class is sealed then the entire class will be sealed.
8. If a part of the partial class is abstract then the entire class will be an abstract class.

Example

I will develop an example that explains how to use a partial class in your project. Suppose you are working with LINQ to SQL in your application. So you create a data context, in other words, a .dbml file, and drag and drop the necessary tables. Each table creates a partial class in the data context designer file and each table field becomes a property for the table. Suppose you have a “Person” table that has the three fields "Id”, “Name” and “DateOfBirth” and you want to show the age of each person in a grid view.