Here's what is probably a foolish question but I'll ask it anyway. Is there a way in Visual SourceSafe to do following:
1. Have trunk and branch versions of a VS.Net solution containg a web project and common (shared by multiple solutions in the source tree) library projects and have both of these solution's web projects peacefully coexist on a single dev box. Based on my initial tests, the answer appears to basically yes. 2. Have the library project references within the branched solution correctly reference the projects of the original trunk solution. The answer, due the the relative file paths used by VS.Net appears to be no. I suppose that one could update the solution's project references paths but this becomes a maintainance hassle ... fast. 3. Because there is no way to branch within VS.Net directly there is also no way to control/scope all projects to a particular branch. So what you end up doing is tracking all of the solution's project dependancies separately for the Visual SourceSafe tree. 4. Do any of the source control features in Team Foundation help me with these issues? For example, I believe a developer can create a "private branch" but can a common branch be created too? Can the Team Source branch scoped and managed at the solution level and not the file level? Does Team source and VS.Net 2005 effectively manage multiple web projects? 5. Are there any source control projects that address many or all of these issues? VS.Net does a lot od solution maintainance for you but in real world situations such as described above it actually gets in the way. =================================== This list is hosted by DevelopMentorŪ http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
