I work in a team of five. We are working on a C # application with five csprojects.
The problem is that for each cs project, each of my colleagues has their own ideas on how to reference a DLL; some would like to link the Project link, others would like to link only in the DLL. Thus, each of us will have his own project.
I want them all to check their csproject; but provided that each copy of the csproject project is different, there really isn’t a viable mechanism for this, is there? But if I do not ask them to check their csproject, then every time they add a new file, I will have to manually edit my csproject project and this is very tiring, not to mention that it aims at continuous integration.
Is there any strategy for this? I know that it would be better to use the standard, but is there another option that leaves this aside?
There is a reason that csproject content is different for everyone; not everyone has all five csprojects, and not everyone can have all 5 csprojects. Therefore, invariably, some will need to refer to DLLs instead of projects, and some want to refer to projects for ease of debugging. If I were to apply the standard, as the answers here suggest, I would have to solve this problem.
Regarding the need to split into several cs projects, this is because we want to reuse some parts of the code for other applications and because not everyone can have all access to the source code. This is more political than technological.