Share
ReportWe are finally trying to make the move from using VSS as our source code control system to TFS. In my setup and testing of this, I have come up with something that has stumped me. I have setup and imported our source code into TFS and it is fine. On my build machine I have created the workspace, installed and have running the DSCCS and everything looks fine. I then open Dexterity and enter the correct project and I can then see and fetch the source correctly. All good.
Problem comes in that I checkout some code and edit it and then check it back in. No errors, and it 'looks' fine. However, if I look at the Repository in Dexterity's Resource Explorer, it says that code is still locked by me and the version (changeset number) is not incremented. If I go into TFS itself, the code is NOT updated and is still at status 'lock, edit' and looking at the workspace files themselves, that file is not Read-only unlike all the other files and instead has the Archive attribute set.
I assumed that the file would have been checked in using the Dexterity check-in function in the same way it was with VSS. I can go unlock code and it correctly resets the status in TFS but checking in doesn't seem to work, either with the Resource Explorer button (green check mark) or the menu Check In that allows multiple check-ins at once.
Has anyone seen this or have information as to why this might be occurring?
Thanks,
Geoff
*This post is locked for comments
All responses (
Answers (
291,280
