与 SVN 共享工作副本时锁定文件
我知道这不是建议的 SVN 处理方式，但我不想改变我们当前使用经典 ASP 应用程序的方式。
一切都集中在一个 IIS 开发服务器上，我不希望每个开发人员都有自己的副本。
话虽如此，在 SVN 下共享工作副本时有没有办法使用锁定呢？
据我了解，您可以锁定存储库上的文件，这样任何人都无法提交它们，但是工作目录中的并发访问又如何呢？
I know that this is not the suggested way of doing things with SVN, but I would like not to change our current way of working with our classic ASP application.
Everything is centralized on a single IIS development server and I don't want every developer to have their own copy.
Having said that, is there a way to use locking when sharing a working copy under SVN?
From what I understood, you can lock files on the repository so no one can commit them, but what about concurrent access in the working directory?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
无法通过工作副本上的 SVN 进行锁定。这是一种模糊的概念，即使用存储库，但仍然有一个所有开发人员都在工作的公共区域！
我建议您改变工作方法，让开发人员拥有自己的副本，并在 IIS 工作副本上，一旦签入更改就使用更新（或自动更新）。您可以使用轮询器来查找更改在存储库中。
The locking is not available thru SVN on a Working copy. This is kind of a vague concept of using a repository and still having a common area where all developers are working!
I would suggest you to change the working methodology and let the developers have their own copies, and on the IIS working copy, use update (or auto-update) as soon as a change is checked in. You can use Pollers to look for changes in the repository.
如果您共享工作副本，那么它基本上只是一堆文件和文件夹，您可以使用标准文件系统权限“锁定”它们。
If you are sharing the working copy, then it is basically just a bunch of files and folders and you "lock" them using standard filesystem permissions.