If you are using .NET you must get all of them because like you said, the solution and the project files for a build.
However, actually they are .NET files and makes perfect sense if you get the common items 1 time and 1 time for all the projects, maybe per release, and put it in your workspace. This is essentially the baseline version or the version of the last release. You obviously branch from the main and then you get the 3 files from the branch and do a get latest off of those and have the workspace of the branch be the same as the workspace for baseline.
The references of the projects in the .sln would all have to be in your workplace. You even do an MKLINK to make a symbolic link to make the referencing easlier with the .sln.
That may actually work-out, kinda thinking and typing here.
One that situation would have 1 hit on time to take the 10 minutes to get that latest from the common and 1 for all the projects. Then after that you still have the branch and if you only need to modify those 3 files. Then you have only those 3 files from the branch in your workspace.
You can still build and compile the .NET using those 3 changed versions. The other projects would use the same baseline version in the workspace but hmmm...wouldn't isolate like the Project 1, Project 2, etc because those change from each Project would go into the base the the projects really aren't isolated, per say. It would be like a unit test system test.
Let me think about this...there are pro's and con's.
I will play with this tomorrow. I will let you know the outcome.
Thanks for the dicussion davidkallan. It has me thinking.
Again, I'll let you know how that works out or if it is even within reason considering.
Thanks!
However, actually they are .NET files and makes perfect sense if you get the common items 1 time and 1 time for all the projects, maybe per release, and put it in your workspace. This is essentially the baseline version or the version of the last release. You obviously branch from the main and then you get the 3 files from the branch and do a get latest off of those and have the workspace of the branch be the same as the workspace for baseline.
The references of the projects in the .sln would all have to be in your workplace. You even do an MKLINK to make a symbolic link to make the referencing easlier with the .sln.
That may actually work-out, kinda thinking and typing here.
One that situation would have 1 hit on time to take the 10 minutes to get that latest from the common and 1 for all the projects. Then after that you still have the branch and if you only need to modify those 3 files. Then you have only those 3 files from the branch in your workspace.
You can still build and compile the .NET using those 3 changed versions. The other projects would use the same baseline version in the workspace but hmmm...wouldn't isolate like the Project 1, Project 2, etc because those change from each Project would go into the base the the projects really aren't isolated, per say. It would be like a unit test system test.
Let me think about this...there are pro's and con's.
I will play with this tomorrow. I will let you know the outcome.
Thanks for the dicussion davidkallan. It has me thinking.
Again, I'll let you know how that works out or if it is even within reason considering.
Thanks!