如何防止 Team Foundation 解除锁定 [英] How to prevent Team Foundation undoing locks

查看:20
本文介绍了如何防止 Team Foundation 解除锁定的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我已经与 Team Foundation 合作了一段时间,我发现一种行为特别令人讨厌.假设我有几个团队项目:

I've been working with Team Foundation for a short while now, and I'm finding one behaviour particularly annoying. Say I have several Team Projects:

$/
  Project1
  Project2

现在,出于我们并不真正需要进入的原因,我想保持 $/Project2 锁定,以防止其他人对其进行任何操作.通常,每当您在树的特定级别进行签入时,该级别及以下级别的所有内容都包含在签入中.

Now, for reasons we don't really need to get into, I'm wanting to keep $/Project2 locked, to prevent anyone else doing anything to it. Normally, whenever you do a check-in at a particular level of the tree, everything at that level and below is included in the check-in.

但是,在这种情况下,每当我对 $/Project1 下的任何内容进行签入时,要签入的项目列表中包含对 $/Project2 的锁定.如果我点击 OK,我的锁就会消失.有什么办法可以防止这种行为吗?

However, in this case, whenever I do a checkin to anything under $/Project1, included in the list of items to check-in is the lock on $/Project2. If I just hit OK, my lock disappears. Is there any way to prevent this behaviour?

推荐答案

使用不同的工作区.锁定、签出和签入仅限于工作区.

Use different workspaces. Locks, checkouts and checkins are scoped to the workspace.

设置工作区后,它们的使用在很大程度上是透明的(特别是如果您选择在结帐时获取最新信息).

Once the workspaces are set up their use is largely transparent (especially if you select to get latest on checkout).

这篇关于如何防止 Team Foundation 解除锁定的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆