如何集成 VSS 6 以便 VB 6 在编辑时自动检出？
我正在使用 Visual Studio 6.0 和 Visual Basic 6.0。
我已将它们集成，但是当我签出一个项目，然后尝试编辑该项目中的模块时，它被锁定，我必须手动右键单击它并执行“签出”操作才能将其解锁。
我认为有一种方法可以让 VSS 自动检出文件进行编辑。
有什么建议么？
I'm using Visual Studio 6.0 and Visual Basic 6.0.
I have them integrated but when I check out a Project and then try to edit a module in that project it's locked and I have to manually right-click on it and do a Check Out to unlock it.
I thought there was a way to have VSS automatically check out the file for editing.
Any suggestions?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（6）
我同意克里斯的观点。 现在我知道一群人说你的“软件很糟糕”并不能真正回答你的问题。 但是签出式源代码控制和源安全等文件锁定系统之间存在天壤之别。 普遍的共识是结帐系统要优越得多。
通过签出，您要做的就是从存储库中签出项目。 所有文件都是可编辑的。 您像往常一样处理您的项目。 然后在您签入之前进行另一次更新。 如果您团队中的其他人进行了更新，软件会自动将更改合并到您的代码中。 您将有机会检查合并并解决任何冲突。 更新后，您可以签入您的更改，其他人都可以检索。
最可怕的部分是合并部分。 当 CVS 和 subversion 只是命令行工具时，这有点可怕，因为检索合并时发生的事情很痛苦。 但如今像 Tortoise 这样的工具都是可视化的。 在过去的几年里，我想不出有任何自动合并失败的例子。 任何冲突（基本上是两个人编辑同一行代码）都会显示在此处供您解决。
Subversion
乌龟SVN
I agree with kris here. Now I know that a bunch of folks saying your "software stinks" doesn't really answer your question. But there is a world of difference between a check out style source control and a file locking system like Source safe. The general consensus is that Check out systems are far superior.
With check out, what you do is you check out the project from your repository. All the files are editable. You work on your project as normally. Then before you checkin you do another update. If anybody else in your team did a update the software will automatically merge in the changes into your code. You will have a chance to review the merges and resolve any conflicts. After the update you can then check in your changes which everyone else can retrieve.
The big scary part is the merging part. Back when CVS and subversion where just command line tools it was a little scary as it was a pain to retrieve what happened with the merging. But with today's tools like Tortoise is all visual. In the last couple of years I can't think of any instance where a automatic merge failed. Any conflicts (basically two people edit the same line of code) are display right here for you to resolve.
Subversion
Tortoise SVN
SourceSafe 中的“本地文件”选项卡下有一个选项，标记为“对未签出的文件使用只读标志”。 默认情况下，此选项处于选中状态，但如果取消选中它，您将能够编辑项目中的任何文件，而无需将其检出。
取消选中该选项后，您可以获得项目的最新版本，以从所有文件中删除只读标志。
当您签出文件时，系统会警告您，工作文件夹中有该文件的可写副本，此时您可以将其替换为 SourceSafe 数据库中的版本。
There is an option in SourceSafe under the "Local Files" tab labeled "Use read-only flag for files that are not checked out". By default this option is selected, but if you unselect it, you will be able to edit any file in the project without checking it out.
Once you uncheck the option, you can get the latest version of a project to remove the read-only flag from all the files.
When you check out a file, you will be warned that there is a writable copy of the file in your working folder, at which time you can replace it with the version in the SourceSafe database.
我从来没有想出办法做到这一点。 这始终是一个巨大的痛苦。 很抱歉发布否定答案，但我想您可能想知道您并不是唯一一个讨厌这个的人，但没有立即且明显的答案。 我将与您一起关注这个问题，以防有人知道解决方案......
I never figured out a way to do this. It was always a huge pain. Sorry for posting a negative answer, but I figured that you might want to know that you aren't alone in hating this, but that there wasn't an immediate and obvious answer. I'll be following this question along with you in case someone out there does know of a solution...
我认为不可能做到这一点（至少八年前我们使用 VSS 时不是这样），但是当您正在经历签出风格的源代码控制的痛苦时，跑——不要走，去一些真正的、非锁定式的源代码控制解决方案。 SVN、CVS、Git、Mecruial，任何不锁定文件且不会将源代码保留在专有文件系统中的工具。 八年前，我们切换到 CVS，因为 VSS 故障导致我们丢失了所有源代码历史记录（代码已签出，因此可以检索）。 我们做过的最好的事情是，让协作变得更加容易。 现在CVS不是最好的解决方案（它是当时windows最合理的解决方案），但任何东西都比VSS更好。
I don't think it is possible to do this (at least it wasn't when we used VSS eight years ago), but while you are experiencing the pain of a check out styled source control, run - don't walk, to some real, non-locking style source control solution. SVN, CVS, Git, Mecruial, anything that doesn't lock files, and doesn't leave your source in a proprietary file sytem. We switched to CVS eight years ago because we lost all of our source history (the code was checkout out so it was retrievable), due to a VSS glitch. Best thing we ever did, made collaboration ten times easier. Now CVS isn't the best solution (it was the most reasonable solution for windows back then), but anything is better than VSS.
我发现的最佳解决方案是检查所有文件。 花了一些时间来弄清楚如何做到这一点。 就是这样：
如何从 VSS 检出所有 VB6 项目文件？
Best solution I found was to check out all the files. Took a bit of poking around to figure out how to do that. Here's how:
How to check out all VB6 Project files from VSS?
喜不喜欢，它都是按照设计的方式工作的，即你可以查看所有文件，但你必须明确选择这样做，而不是作为默认选项。 我想这是因为检查所有模块（类模块、表单、用户控件等）会锁定整个项目的所有其他用户，这在团队协作环境中通常是不受欢迎的。
Like it or not, it works that way by design i.e. you can check out all the files but you have to explicitly choose to do so, rather than being the default option. I guess that's because checking out all modules (class modules, forms, usercontrols, etc) locks out all other users from the entire project, which is normally undesirable in a team collaboration environment.