CVS .Net

It's been 2 weeks since i switched my SCC provider to CVSNT http://www.cvsnt.org . It has solved a lot of problems that i had before when i wanted to work on a new release but still maintain the old codeline for bug fixes and patches. Now using the branching capabilities of CVS i have two codelines life is much easier.

Also now that i have the hang of both WinCVS http://www.wincvs.org and TortoiseCVS http://www.tortoisecvs.org

it's great. The CVS-SCC Proxy from PushOk http://www.pushok.com is working great, i have had no problems till now. It amazes me that people still use VSS for large scale team development, i can't imagine how people manage branches, merging etc. Is it just me or is there something amiss.

4 Comments

  • CVSNT and TortoiseCVS and the proxy from PushOK actually take a little work to figure out, whereas Microsoft has integrated all 3 things into 1 easy to not understand install process. Then they flock to something like SourceGear's Vault just because it wraps these 3 things up into 1 again.

  • Does CVSNT have any issues with spaces in filenames?

  • I think the latest version of CVSNT does not have such issues. I have filenames with spaces and they seem to be working fine.

  • I've been working with CVSNT and TortoiseCVS and the proxy from PushOK and VS.NET 2003. PushOK works but we've had to do some hacks to get it to work properly on the computers that did not add the solution to source control. We're primary working on asp.net apps. We've found that it's necessary to copy the source files including the CVS dir's to the other computers and get latest for everything to work properly because we can't get the open project from source control to successfull get a project and make it work. These projects are microsoft Asp.net content management server projects and i don't know if thats the difference or not but otherwise it appears to work. I just wish we didnt have to have a hack to make it work.



    Has anyone else experienced anything similar?

Comments have been disabled for this content.