I am currently working with a source tree that has one sln file housing all the WebApps, WinServices, WebServices, Console Apps and Common libraries (Business entities, custom controls etc).
The file structure for this is very flat, as in
+--Solution Folder
+----Solution File
+------WebApp1
+------WcfService1
+------WinService1
+------CommonEntities
+------WebControls1
+------ThirdPartyAssemblies
I have begun work to create separate solutions for each web app, wcf service etc. In doing this I am able to see the common projects across these solutions.
MY Question to you guys is how do i structure my file system within TFS so i can use the common projects across the board?
I am more than happy to follow the Single TFS Project approach defining areas per site/service for work items and reporting, but i am less keen on branching the common libraries for each project. That said how have you guys overcome these problems?
I understand that people also suggest having the common projects in one solution and then referencing the compiled binaries in other solutions. I’m not really keen on this approach either. To be fair i will take the lesser of two evils if these are the only options but am eager to see how other people have tackled it.
I can’t exactly feel your point so I will try to open the door for you, have you look on Multiple Solution Approach?
More info:
Chapter 3 – Structuring Projects and Solutions in Source Control
For the source control structure there are different approaches
Have you look on Server-Side Structure?
More info:
Chapter 4 – Structuring Projects and Solutions in Team Foundation Source Control