It is possible to split the definition of a class or a struct, or an interface over two or more source files. Each source file contains a section of the class definition, and all parts are combined when the application is compiled.
When working on large projects, spreading a class over separate files allows multiple programmers to work on it simultaneously.
When working with automatically generated source, code can be added to the class without having to recreate the source file. Visual Studio uses this approach when creating Windows Forms, Web Service wrapper code, and so on. You can create code that uses these classes without having to edit the file created by Visual Studio.
Benefit of partial classes
- More than one developer can simultaneously write the code for the class.
- You can easily extend VS.NET generated class. This will allow you to write the code of your own need without messing with the system generated code.
- All the partial definitions must proceeded with the key word "Partial".
- All the partial types meant to be the part of same type must be defined within a same assembly and module.
- Method signatures (return type, name of the method, and parameters) must be unique for the aggregated typed (which was defined partially).
- The partial types must have the same accessibility.
- If any part is sealed, the entire class is sealed.
- If any part is abstract, the entire class is abstract.
- Inheritance at any partial type applies to the entire class.