s***n
发帖数: 10693 | 1 半小时写出的code用了四倍的时间check-in.
我司的version control system太烂了。 |
a9
发帖数: 21638 | 2 vss? 远程?
【在 s***n 的大作中提到】
: 半小时写出的code用了四倍的时间check-in.
: 我司的version control system太烂了。
|
s***n
发帖数: 10693 | 3 team foundation
主要是branch规划得很不合理。
巨怀念以前用的synergy
vss? 远程?
【在 a9 的大作中提到】
: vss? 远程?
|
v******n
发帖数: 421 | 4 TFS怎么这么慢。。。两个小时
【在 s***n 的大作中提到】
: 半小时写出的code用了四倍的时间check-in.
: 我司的version control system太烂了。
|
a9
发帖数: 21638 | 5 这不也是vss嘛。vss远程就是这样。
【在 s***n 的大作中提到】
: team foundation
: 主要是branch规划得很不合理。
: 巨怀念以前用的synergy
:
: vss? 远程?
|
N********n
发帖数: 8363 | 6
Wait until you try SVN. I thought I'd never use a system worse than VSS.
Then I ran into SVN, oh boy.
【在 s***n 的大作中提到】
: 半小时写出的code用了四倍的时间check-in.
: 我司的version control system太烂了。
|
v******n
发帖数: 421 | 7 I used svn for small projets and felt okay...any better source control
recommendation?
【在 N********n 的大作中提到】
:
: Wait until you try SVN. I thought I'd never use a system worse than VSS.
: Then I ran into SVN, oh boy.
|
a9
发帖数: 21638 | 8 就跟vs.net集成来讲，svn貌似不错的了。不过我还没用过，呵呵。
我原来用vss，check in的时候无线都不行。需要连上有线网络。
【在 v******n 的大作中提到】
: I used svn for small projets and felt okay...any better source control
: recommendation?
|
k***e
发帖数: 7933 | 9 what do you mean? for me, SVN is much much better than VSS.
【在 N********n 的大作中提到】
:
: Wait until you try SVN. I thought I'd never use a system worse than VSS.
: Then I ran into SVN, oh boy.
|
N********n
发帖数: 8363 | 10
Lots of gotchas when you really use it. Especially merging. It's slow and
over-merges what you do not want to check-in yet.
【在 k***e 的大作中提到】
: what do you mean? for me, SVN is much much better than VSS.
|
|
|
a9
发帖数: 21638 | 11 跟vs.net集成度还不行？
vss跟vs.net集成好，用起来方便。缺点就是只适合局域网用。通过互联网实在是太慢
了。
【在 N********n 的大作中提到】
:
: Lots of gotchas when you really use it. Especially merging. It's slow and
: over-merges what you do not want to check-in yet.
|
k***e
发帖数: 7933 | 12 有个plugin， free的，还好。
【在 a9 的大作中提到】
: 跟vs.net集成度还不行？
: vss跟vs.net集成好，用起来方便。缺点就是只适合局域网用。通过互联网实在是太慢
: 了。
|
k***e
发帖数: 7933 | 13 我们组已经在production环境下用了好几年了。
branch，merge之类的比VSS不知道好多少。VSS
简直就是没有这些功能。
【在 N********n 的大作中提到】
:
: Lots of gotchas when you really use it. Especially merging. It's slow and
: over-merges what you do not want to check-in yet.
|
N********n
发帖数: 8363 | 14
VSS doesn't have them. SVN have but difficult to use compared w/ TFS that
sits on a mini SharePoint to get the whole development flow organized.
【在 k***e 的大作中提到】
: 我们组已经在production环境下用了好几年了。
: branch，merge之类的比VSS不知道好多少。VSS
: 简直就是没有这些功能。
|
S***k
发帖数: 370 | 15 I used SourceOffSite to access Visual SourceSafe remotely before.
After we upgraded to TFS, I use VPN to connect to tfs to access code from
home.It seems OK to get latest version, check-in and check-out. However, the
tfs has no any branch because the administrators don't know how to set it
up. The person who deploys code never announce the publishing schedule. It
happened several times that my code were deployed to production just several
minutes after I checked it in. So, it is not bad to spend |
c**t
发帖数: 2744 | 16 TFS is too complex. Visual SourceSafe is not comparable.
the
several
check-
【在 S***k 的大作中提到】
: I used SourceOffSite to access Visual SourceSafe remotely before.
: After we upgraded to TFS, I use VPN to connect to tfs to access code from
: home.It seems OK to get latest version, check-in and check-out. However, the
: tfs has no any branch because the administrators don't know how to set it
: up. The person who deploys code never announce the publishing schedule. It
: happened several times that my code were deployed to production just several
: minutes after I checked it in. So, it is not bad to spend
|
M******k
发帖数: 27573 | 17 TFS branching/merging to me is not too shabby, but again, maybe the codebase
is too small to be used as example.
the
several
check-
【在 S***k 的大作中提到】
: I used SourceOffSite to access Visual SourceSafe remotely before.
: After we upgraded to TFS, I use VPN to connect to tfs to access code from
: home.It seems OK to get latest version, check-in and check-out. However, the
: tfs has no any branch because the administrators don't know how to set it
: up. The person who deploys code never announce the publishing schedule. It
: happened several times that my code were deployed to production just several
: minutes after I checked it in. So, it is not bad to spend
|
