Dependent projects

[Guest]

When I have a project (e.g. App1) and dependent projects, such as generic
components (e.g. Comp1, Comp2), I store them in the following directory
structure:
Apps\App1\App1.sln
Apps\App1\App1.csproj
Apps\App1\Comp1\Comp1.csproj
Apps\App1\Comp2\Comp2.csproj

That's fine - for App1. But what when App2 wants to use one of Comp1 or Comp2?
Do I have
Apps\App2\App2.sln
and then use "..\..\App1\Comp1\Comp1.csproj" which is ugly and causes
SourceSafe to complain that someone else won't be able to check it out to
their folder.

The best solution I can find at the moment is
Apps\App1\App1.sln
Apps\App1\App1.csproj
GenericComponents\Comp1\Comp1.csproj

which is fine for the projects on my system, but still causes Source Safe to
complain that they my projects aren't all in a "nice" directory structure.
Short of having ALL projects, components and everything in the SAME
directory, just bunged in together (which I'm HIGHLY tempted to do as they
all have unique filenames...), what would readers recommend I adopt as my
standard directory structure policy, for projects and generic components?

 

[Nick Malik]

If a component is actually re-usable, then you won't need to share the
SOURCE CODE. You will reference the DLL. If you compile a seperate project
that contains the component, and refer to that project in your solution
(your second structure, below), and if your component project is bound to
VSS seperately from the solution that uses it, you shouldn't get complaints
from VSS.

--- Nick