Question

When I was working in enterprise, we used multiple projects in the solution – projects for UI, business logic, data access, database and printing. Now I’m in a new enterprise and the manager tells me that I don’t have to make all these projects, but that I have to make them into seperate directories in one project in the solution.

I just want to know if I have to convince him to use multiple projects!

Answer 1

I actually agree with your manager.

Multiple projects means multiple assemblies, lots of copying around of assemblies, and generally slower compilation times.

If your only reason to have multiple projects is improved organization, then you are doing it wrong. It would be just as effective to use folders.

Some valid reasons for having different assemblies are:

• You have a plugin architecture
• You need to deploy assemblies separately
• You need to work in multiple languages
• You are creating libraries to be used in different places