Quantcast
Channel: Team Foundation Server - General forum
Viewing all articles
Browse latest Browse all 6687

How can I remove a forced checkout lock currently enforced by TFS?

$
0
0

Hello, 

We are currently using (Visual Studio 2010 Premium) TFS for a small dev team and continually run into issues when attempting to work on the same file at one time.

We have all of our pertinent file types enabled for multiple checkouts (via Team>Team Project Collection Settings>Source Control File Types>(Select file type, edit...)Enable file merging and multiple checkout) at the team level, and lock settings on the project set as well (Right click on project) Team Project Settings>Source Control>Enable multiple checkout selected.

However, any time that one of us goes to edit a file or manually performs a "Check out for edit...", there is a checkout lock being applied, with no recourse for disabling or otherwise selecting a "no lock" option. I am currently unable to attach images to posts, but when we attempt to check out a file manually, the "Lock type" drop-down option is forced to a check out lock and is a grayed out selection ( unable to be changed ).

Additionally, we are each working in our own private workspace (saving locally) and check-ins update the repository hosted on a local server (if I am understanding correctly).  All members of the dev team have been added as administrators as well, so I do not believe this to be an issue of permission for edits/writes of files.

Is there a better alternative to what we are trying to accomplish, which is to have basic version control with a centralized repository where multiple people can work on same files and conflicts are resolved using the merge tool? I feel like this is Version control 101, but a missing a setting that is ultimately defeating the purpose of using TFS in the first place. 

I appreciate any help you can offer in advance,

Regards,

Kevin



Viewing all articles
Browse latest Browse all 6687

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>