WXS123

I doubt you are supposed to do this, but I often times either find someone who purposely did this or somehow accidentally did this.

They would map:

$/Myproject to w:\Myproject

and map:

$/Myproject/dir1 to w:\MyProject\dir1

Sometimes with mappings this way I have found that dir1 directory will no longer get pulled down.

So one of two things here:

1. Either this is allowed and it should work - then the follow up question is, why doesn't it

or

2. This should not be allowed and it should not let you set these in the workspace to avoid confusion

Which one is the appropriate answer Smile

Thanks



Re: Team Foundation Server - Version Control Overlapping workspace directories issues

Eugene Zakhareyev

I have been using the following structure lately:

$/Project/Ongoing to c:\Project

$/Libraries/Lib1 to c:\Project\Common\Lib1

$/Libraries/Lib2 to c:\Project\Common\Lib2

It was allowed and it worked. No problems with getting the latest version for subfolders (I used SCE).

Cheers, Eugene






Re: Team Foundation Server - Version Control Overlapping workspace directories issues

WXS123

Eugene Zakhareyev wrote:

I have been using the following structure lately:

$/Project/Ongoing to c:\Project

$/Libraries/Lib1 to c:\Project\Common\Lib1

$/Libraries/Lib2 to c:\Project\Common\Lib2

It was allowed and it worked. No problems with getting the latest version for subfolders (I used SCE).

Cheers, Eugene

We've found most people work tthat way for a while and then finally something seems to come unglued, we are not sure what precipitates that.

At that point though it becomes impossible to get code from the underlying directory regardless of any get latest, get specific version or workspace sync until the overlap is removed.





Re: Team Foundation Server - Version Control Overlapping workspace directories issues

Eugene Zakhareyev

Pretty weird, that.

Are you doing get latest using Solution Explorer or SCE And if the latter do you do it recursively (from the root) or on specific projects/folders And would forced get solve the issue

It is very interesting - because if there is a problem, I'd rather know about it in advance as the layout is pretty typical.

Thanks for following that up,

Eugene






Re: Team Foundation Server - Version Control Overlapping workspace directories issues

Richard Berg MSFT

It should work.

WXS123, if you can reproduce this again, please turn on client logging so we can see what's going on.




Re: Team Foundation Server - Version Control Overlapping workspace directories issues

WXS123

Yes we were doing this from SCE. From the folder itself or root, didn't seem to matter.





Re: Team Foundation Server - Version Control Overlapping workspace directories issues

WXS123

Richard Berg MSFT wrote:
It should work.

WXS123, if you can reproduce this again, please turn on client logging so we can see what's going on.

Ok, if I see this again I will put tracing on. I have only seen this happen 2 times so far, but I am sure this is what is happening as I tried every other method of resolving and the only answer was to remove the overlapping directories and do a get latest again.





Re: Team Foundation Server - Version Control Overlapping workspace directories issues

Mario Rodriguez- MSFT

You might also want to check that somehow ... and yes I don't know how ... the second mapping did not switch from Active to Cloak. If it did you will see the behavior you are stating.

Eitherway next time turn tracing and let us know and also check the Active or CLoak state of those folders.

thanks, mario






Re: Team Foundation Server - Version Control Overlapping workspace directories issues

WXS123

Mario Rodriguez- MSFT wrote:

You might also want to check that somehow ... and yes I don't know how ... the second mapping did not switch from Active to Cloak. If it did you will see the behavior you are stating.

Eitherway next time turn tracing and let us know and also check the Active or CLoak state of those folders.

thanks, mario

Next time I'll double check but I'm pretty sure I verified it was not set to cloak as I had thought the same thing at the time. We'll turn tracing on next time.

Thanks





Re: Team Foundation Server - Version Control Overlapping workspace directories issues

Ben Ryan - MSFT

For the specific example you list:

$/Myproject to w:\Myproject

and map:

$/Myproject/dir1 to w:\MyProject\dir1

You should end up with only one mapping: $/MyProject to w:\MyProject. The server is smart enough to figure out that the mapping $/Myproject/dir1 already maps to w:\MyProject\dir1, and it doesn't create a separate explicit mapping. If you are seeing two mappings remain in existence then most likely:

1) the dir1 mapping is a cloak rather than an active mapping (as Mario posits) -or-

2) the $/MyProject/dir1 server folder is mapped to something other than w:\myproject\dir1

In case 1, you will obviously have files residing under dir1 in the repository that would not be fetched by a Get.

In case 2, you have the files from the dir1 server folder being fetched to a location locally that no longer matches their relative location on the server with respect to the MyProject folder. This could cause issues opening a solution if that solution's files were distributed across MyProject and MyProject\dir1.

--Ben Ryan






Re: Team Foundation Server - Version Control Overlapping workspace directories issues

Eugene Zakhareyev

Ben,

I think the idea is to have layout like that:

$/Project1/Source c:\Project1\Source\Application

$/Project2/Source c:\Project1\Source\Common\Project2

I have been using the layout above and never had any issues. Does that layout make sense to you

Thanks, Eugene