We are having an issue with one of our repositories. This repository has numerous branches. When one of our developers (the only one having this issue) try's to pull down one of the branches, he can check out but cannot check in a file. This occurs in both Visual Studio 2008 and the Fortress Client. Also, when he right clicks the file and selects properties, the location of the file doesn't match where the file is via the working directory. Any thoughts of what this could be? We are on build 2.0.1.18729.
Thanks,
Richard
Issue with Repository
Moderator: SourceGear
Re: Issue with Repository
If your user tried to set two branches to the same location in Fortress, it's possible to get confused what goes where. Only one location in Fortress can point to one location on disk.
It's also possible that your user added the file to the solution from the wrong disk location. In that case, the project file would point to the location the file was added from.
Can you look in the project file for the file you can't check in? Is it listed and is the correct path in the project file?
Can you go to your bindings in VS, by going to File - Fortress Source Control - Change Fortress Bindings? Do the locations listed in both the repository and on disk look correct and is there a valid status?
Are you using the Fortress Enhanced Client or the Fortress Classic Client?
It's also possible that your user added the file to the solution from the wrong disk location. In that case, the project file would point to the location the file was added from.
Can you look in the project file for the file you can't check in? Is it listed and is the correct path in the project file?
Can you go to your bindings in VS, by going to File - Fortress Source Control - Change Fortress Bindings? Do the locations listed in both the repository and on disk look correct and is there a valid status?
Are you using the Fortress Enhanced Client or the Fortress Classic Client?
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support