Opening TFS VC bound solution causes path change and check-out

[etropic]

Developer team using Tfs Version control. When opening (not checking-out) a
solution the solution will resolve relative paths for projects in the
solution based on the users local workspace. If these rojects then contain
references to other project (in the same solution) output (dll) the project
with the dll reference will have its relative path to that project changed
causing a checkout of the project file!

Requiring everyone to use the same structure in their workspaces that VC has
will limit the initial probem, but in our opinion this limits the flexability
of the workspace functionality.

The bigger issue comes in when trying to branch this solution to a DEV
folder. We can't seem to figure out how to keep the paths correctly working
when branching. Obviously if we only branch to DEV (instead of MAIN) then the
path depth is the same, but with multiple developers branching their own
work, you need sub folders in dev to isolate changes.

I can't seem to find any guidence or functionality information for this
other than project layout guidence and how workspaces work on a very general
level.

1. should a GET change paths? If so to what?
2. If GET changes paths, why does the solution find the projects, but the
project can't find the other projects without changing and doing a check-out?
3. If the workspace is aiding in this change, how should a DEV branch be
structured so that it can find the correct outputs?

thank you!!