References to other projects

[Peter Morris]

I have a product which has a solution made up of about 6 projects. I am now
writing a website for this project and one of the requirements is to use a
project from the first solution in order to use the class that creates user
license files. This license project uses other projects too.

I don't want to merge both into a single solution because they are
completely separate but just share common projects. So what I'd like to
know is this...

How should I reference these original projects in my new solution? I
normally like to add projects and use project references, just to ensure
they are always up to date. In this case the original project is VS2005 and
the site is VS2008.

Are there any problems with me directly referencing
OtherProject\Release\Bin\OtherProject.dll?

I'd just like to know what a good approach to this would be


Thanks

Pete

 

[Marc Gravell]

There should be no problem having 2 separate solutions that reference
the same project, as long as the solutions are outside of the project
tree (otherwise it has a nasty habit of finding the other solution).

Referencing the binary should also be fine, but can make it harder to
debug (although you can step into the code if you include the symbols
file (.pdb)).

Marc