I just said, that I'm working with the application from my late colleague. All forms classes are in one library, all dialogs in another, all biz objects in another and some extra class libraries.

But since there are lots of forms and dialogs in this application, each library has more than 20 classes (I haven't counted them, actually).

Now I don't want to change this organization right now, because I may have some reference problems, AFAIK, if I start moving things around.

On the other hand, there is a bigger chance for corruption now and more at stake to lose.

>>>Exactly the problem. Had you started with them broken out, there would be no need to combine them.
>>
>>I haven't started this application.
>
>I'm not sure what you're saying. Look around you. Most physical things are assembled from parts for use (at runtime). The individual parts have their own blueprints.
>
>No engineer draws a single blueprint the embeds the blueprints of all the other devices.
>
>For something as simple as a USB key the blueprint will look like
>
>shell - usb interface - memory chip.
>
>Some/most programmers would have...
>
>shellusbinterfaceshellusbinterfaceconnectorsmemorychipshellmemorychipcomponentsmemorychipconnectors.
>
>I can't even make the analogy because nobody designs things as programmers do. ;)