First of all sorry for the late reply, I didn’t have a subscription to the discussion list, so just found today that this question is here since end of January.
To Get back to your question, you are totally right! The guidance assumes you set up a build environment that also puts the daily build results into the version control system. This would provide all team members
with the simple steps of setting up their dev environment to:
- Get the workspace mapping from the team (e.g. a workspace template placed in the team members option of the power tools)
- Do a full get on the workspace
- Have all the references to shared items to the shared location in the workspace.
As some guidance in this area, we normally set up a location in version control we call "99-bin" and we hev some subfolders in there as well. e.g. an folder with the name extref for external references to e.g. 3th
party products we use. Then we have a folder called "deliverables" with subfolders for each solution that produces output and is part of our product.
We also make the "99-bin" folder a local drive using the subst command. we do a "subst s: <drive>:\<workingfolder>\product\99-bin"
When we set references in our projects we use the s: drive for the reference so visual studio keeps a full path reference instead of an relative path that breaks when someone uses a different folder structure on
their local dev machine.
Hope this helps,