用Visual Source Safe分支的正确方法是什么? [英] What's the right way to branch with Visual Source Safe?

查看:97
本文介绍了用Visual Source Safe分支的正确方法是什么?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我目前要做的是将项目链接到另一个位置并为其命名,然后选中共享后分支框。
然后我将签出共享项目并进行处理。并最终与原始项目合并。

What I currently do is I link the project to another location and give it the same name, then check the box where it says "Branch after share." And then I would Check out the shared project and work off it. And finally merge with the original project.

这行得通,但是感觉很笨拙:驱动器上有多个项目实例;每当我在其他分支机构工作时,我都必须更改网站的物理地址(我使用asp.net 1.1);

This works okay, but it feels very clunky: I have multiple instances of the project on my drive; I have to change physical address of the website (i use asp.net 1.1) every time I work on a different branch;

那感觉不正确。您如何使用VSS分支项目?

That doesn't feel like the right way to do it. How do you branch your projects with VSS?

推荐答案

我认为问题中的描述是唯一的方法

I think the way you describe in the question is the only way you can do it in sourceSafe.

我通常将复制的目录命名为 V1.0(或适当的名称),并将其全部保留在主项目名称的文件夹中。

I usually name the copied directory "V1.0" (or whatever is appropriate) and keep them all in a folder that is the main project name.

这篇关于用Visual Source Safe分支的正确方法是什么?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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