Introduction

First the architect created partial classes. Partial classes were deemed good, so next the architect created partial methods.

It just doesn’t work. Trying to phrase partial classes and partial classes like a verse from Genesis just doesn’t work. Let’s try something else.

Partial classes permit developers, including Microsoft developers, to split classes between multiple files. This works out pretty good because it lets Microsoft hide some plumbing, for example, for the Windows Forms designer. Partial classes also makes it possible for programmers that consume generated code to write the custom part in a separate location, in case the generated part needs to be re-generated. So there are definite uses for partial classes.

Partial methods help solve the same kinds of problems as partial classes. With partial methods one developer can define a method and another can implement it. Partial methods can be used to separate custom code, at the method level, from generated code.

In this holiday article I will introduce the basic rules for using partial methods and offer some suggested uses for same. The topic is important and useful but not long (perfect for light holiday reading).

Rules for Partial Methods

Partial methods like any part of a language specification have grammatical rules. In a nutshell here are the things you can do and those that you can’t:

It isn’t necessary to memorize these rules. The help documentation is a great source for checking your facts and the compiler will warn you if a mistake is made. Familiarity is enough; extemporization comes with practice and use frequency. That is, if you use partial methods a lot, like anything else fewer syntactical errors will be made.