Ok, I made the mistake of deleting my local copy of the files that are in source control instead of handling all updates via Source control.  In the treeview for the files it shows that the files have a status of "Not downloaded".  I have been unable to Get the Latest version of the files at all. 

I've tried the following to resolve this to no avail:

• Get Latest Version:  Which shows that all files have been downloaded, use the get Specific Version and use the force flag.
• Get Specific Version with Force Get Flag Set:  Which gives the same error asking me to Get Specific Version with the Force Flag Set.
• Open the project via Open From Source Control:  Which gives the error The selected solution cannot be opened as a solution or Project.  Please select a solution file or a project file.  The project file is of type .csproj.
• Delete my workspace, delete all working folders and create a new workspace:  Get Latest ends up retrieving all files except for the folders I am having problems with.

Any help or advise would be greatly appreciated.

Thanks,
Dave

It says "All files are up to date." and the folder is empty as you can see by the below log. Even though the source folder has several files and subfolders.

>dir
Volume in drive C has no label.
Volume Serial Number is 0812-B001

Directory of C:\EHR\Source\XeAppUtils

08/28/2006 10:22 AM <DIR> .
08/28/2006 10:22 AM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 23,634,288,640 bytes free

C:\EHR\Source\XeAppUtils>tf get *.* /all /recursive
All files are up to date.

Ok I just solved the issue.  Even after deleting my workspace and adding a new one for myself, the workspace had a working folder set for the folder in question as well as its parent folder.  Im guessing to TF Source Control this looks like two working folders to the same folder and was causing it to be confused.  I deleted all child working folders and left myself with only the root working folder and I was able to get the latest version. 

I think because I created a new workspace with the same name as the deleted workspace it must have retained some of the old working folder data. 

Hi Dave,

We just had a similar problem in our company.

When I ran TF /workfold I got mappings like:

$/CommonObjects : D:\BacSoft\Common\CommonObjects

This is the WRONG MAPPING!

the Mapping should be

$/BacSoft/Common/CommonObjects : D:\BacSoft\Common\CommonObjects

(We have a mapping from $/Bacsoft to D:\BacSoft and all other mappings are created from that mapping )

This seems like a real bug!

We didn't do anything special before that happened.

The only thing that happened was a blackout that turned off the network connection to the TFS Server

And one of the developement computers

(The Server itself did not go down).

I don't know if this had anything to do with the problem, but it was the only thing out of the ordinary that happened.

Nadav

I created in the Workspace mapping from D:\Bacsoft to $/BacSoft.

All my projects sit under D:\Bacsoft, so when I Add To Source Control VS2005 automatically adds them under $/Bacsoft and adds the mapping.

In the other computers I used Open From Source Control to add them to the solutions.

We never change the mappings manually.

All was working as expected, untill yesterday when suddenly the VS2005 started complaining that it can't find some projects is the solution, it deleted the all the files of the project under D:\BacSoft and tried(and failed) to get them under D:\.

When I tried to get the files (either from VS2005 or using TF.EXE) I got a response that all files were up to date even when I used the force option.

when I looked at the mapping I saw that the mapping changed.

Another thing, the Change happened at the same time in two different workspaces - two different owners on two different computers.

Could this bug we related to the fact that we have a solution that uses projects that are not under it in the tree.
(i.e we have in the solution projects whose relative path starts with ..\..).
I know that it's not recommended to work like this, but it still should not cause the mappings to change invalid mappings, should it?

Thanks,

Nadav

A similar problem happened to my coworker just now.

The VS2005 tries to get the sources for several projects from the wrong place (from $/<projectname> instead of $/BacSoft/Common/<projectname>).

This problem happened after the guy restarted his computer while the solution was checked out
(the previous time the computer was reset because of a power outage).

This is not exactly the same problem (we can still checkout the files through the Source Control Explorer)
and you can open the same projects from other solutions but for this solution is does not work.

If I remove one of the projects from the solution and then try to add it back using Add Existing solution VS2005 complain that it can't find the project file, but it complains about the wrong file!
(I add c:\BacSoft\Common\Utilities\General\General.csproj and VS2005 complains that it can't find C:\General\General.csproj).

TF workfold only shows one mapping:
$/ c:\

I tried deleting the TF cache but it did not help.

Any Ideas?

Nadav