Team System Source Control Structure
For example, suppose my first shared library is Romax.RealEstate and I have corporate intranets for Client 1 and Client 2. Both clients will also have their own class libraries with custom classes as well as classes that inherit from ones that exist in Romax.RealEstate.
What I've done is structure Client 1 the following way in my file system:
MainFolder
Romax.RealEstate
Client1
ClientLibrary
Website
Client1.sln
Client2
ClientLibrary
Website
Client2.sln
So basically, both solution files reference the shared class library which exists outside of their own folder.
Can anyone recommend a way that I can implement something like this without having Visual Studio complain about binding roots and the like?