In addition to what Marcus said, I'd also recommend splitting your class libraries up by function, rather than by type. For example, in the devguide, there's a recommendation to put the forms in the aforms library, biz objects in abizness, etc. This works fine for a single developer, but severely limits the ability to have different developers working on different functional areas simultaneously. There's no good way (that I know of, at any rate) to allow multiple developers to work on the same classlibrary, and then merge the work of the developers.

In some cases, I've even considered (though have not yet done it) having a number of class libraries with one class.



>Nerissa,
>
>I would strongly recomend to use Visual Source Safe(VSS). VSS is a great tool to deal with team developement and it will help you keep things simple because every developer needs to check out files he wants to work on.
>It is in fact no question of the framework you use, the same questions come up with every fwk.
>
>If you don't want to use VSS you can try to devide things up: Put MMortals on and you own base classes on the server (relative pathes) and the modules also on the server in a own path. This will actually help you not to mess up to much, but still you need a bunch of commununication for "who is allowed to change the base classes", "who changed wich class..."...
>
>Marcus
>
>>I currently have only one module in my MM application which calls the main form for this module. We are moving it to the live environment soon. Then two more modules are to be added to it. Now we are thinking on how to do it since two different developers are writing the new modules. How can we make it work like developers can work at the same time in the same project but in different modules? Then afterwards, every developer can move their module in the project in the live environment without affecting others.