I've been having 'discussions' here with my boss over the course of several weeks about the merits of programmatic class definition vs visual definition (in particular for customer classes that are used to encapsulate business functionality).

So far the only compelling arguement produced by either side is that all of his classes are defined in one procedure file. If he wants to use just one of them, he has to include the whole file, or copy and and paste just that one into a new file, which means that when the original is updated, the copy will have to be updated separately.

Does anyone have anything to add this?