Before my current job I actually had had very little experience with non-SourceSafe VCSes, and I have to say Perforce has been a very nice experience. It's a little slow (although SourceSafe is worse, with less stuff in it), and rolling back is much more of a pain than it needs to be, but otherwise I like it quite a bit.
I'll mention AccuRev to the higher ups, but I think our "final 3" is pretty much determined. Thanks for the heads-up. :) On 2/8/06, J. Merrill <[EMAIL PROTECTED]> wrote: > > I'm glad someone mentioned Perforce; tho I have not used it much, it has > many advocates -- tho its cross-platform nature probably doesn't matter much > for us .Net folks. > > Depending on your requirements, you might want to look into AccuRev -- in > particular, it is strong for distributed teams and "outside" > contributors. It has a somewhat different "mindset" than other SCM > products; if you are trying to figure out how to deal with some oddities of > your particular world in traditional source control products, check it > out. (If you've ever tried to figure out how to keep the work you're doing > on a new version under source control during the current version's "code > freeze" without doing lots of extra work, at least look at it!) > > At 11:53 AM 2/8/2006, Eric Means wrote (in part) > >We're trying to decide between Perforce...TFS, and SVN > > > > J. Merrill / Analytical Software Corp > > =================================== > This list is hosted by DevelopMentor(r) http://www.develop.com > > View archives and manage your subscription(s) at > http://discuss.develop.com > -- Eric Means [EMAIL PROTECTED] http://www.randomtree.org/eric/ =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
