I would suggest that you set up VSS so that your common assemblies are not
under the "solution tree" that VSS sets up for any particular project.
Make them their own solutions, individually. Compile them and release the
compiled code into an installable MSI. Developers in your team
would get the MSI from VSS, install it locally, and reference the DLLs from
the same location on each developer's machine (needed so that you
can share the higher-level projects from machine to machine).
For the higher-level app, the reference to the compiled dll is normally
enough to get the dll included in it's install package.
I would not consider it good practice for two higher-level projects to have
access to the source code of a single independent shared project.
Versioning becomes a nightmare.
I hope this helps,
--- Nick
"Simon Neve" <Si*******@discussions.microsoft.com> wrote in message
news:B0**********************************@microsof t.com...
Hello,
This question is related to sharing .Net projects across solutions and is
reposted from the SourceSafe group.
We have several different solutions and want to share common assemblies
across them. Is it best to share the project and its files to each
solution (each solution has it's own shared project), or have each solution point
to the same file location of the project?
If you have each solution point to the same project files, then there are
disadvantages with labelling etc.
Currently we think the sharing option is best but we read in MSDN articles
that Microsoft suggests you avoid sharing top level projects.
Any guidance would be appreciated,
Simon Neve
