Comments on: Working With CVS and Visual Studio http://bobondevelopment.com/2007/05/12/working-with-cvs-and-visual-studio/ Musings on the craft and business of software development Thu, 26 Aug 2010 03:21:57 -0600 http://wordpress.org/?v=2.8.6 hourly 1 By: Chris Dewane http://bobondevelopment.com/2007/05/12/working-with-cvs-and-visual-studio/comment-page-1/#comment-2064 Chris Dewane Thu, 19 Jul 2007 15:46:31 +0000 http://bobondevelopment.com/2007/05/12/working-with-cvs-and-visual-studio/#comment-2064 TamTam will work with any CVS server. It uses the client portion of CVSNT to talk with the server. Install CVSNT first, you can do a custom install and leave out the server component if you want. Then install TamTam. I just set up TamTam to connect to our CVS repository which is running on an IBM AIX server. TamTam will work with any CVS server. It uses the client portion of CVSNT to talk with the server. Install CVSNT first, you can do a custom install and leave out the server component if you want. Then install TamTam.

I just set up TamTam to connect to our CVS repository which is running on an IBM AIX server.

]]> By: Paul Lefebvre http://bobondevelopment.com/2007/05/12/working-with-cvs-and-visual-studio/comment-page-1/#comment-1864 Paul Lefebvre Wed, 23 May 2007 16:00:42 +0000 http://bobondevelopment.com/2007/05/12/working-with-cvs-and-visual-studio/#comment-1864 I've used PushOK for a couple years with Visual Studio 2003 to connect to CVS. It worked OK, but was a bit slow and occasionally did some weird things. Another team here decided to just use WinCVS instead, which seemed to work well for them. We've since switched to TFS for our source control. I found that even TFS source control was a bit wonky with Visual Studio 2003, particularly with branches. I think that Visual Studio 2003 just doesn't work well with integrated source control. I’ve used PushOK for a couple years with Visual Studio 2003 to connect to CVS. It worked OK, but was a bit slow and occasionally did some weird things. Another team here decided to just use WinCVS instead, which seemed to work well for them.

We’ve since switched to TFS for our source control. I found that even TFS source control was a bit wonky with Visual Studio 2003, particularly with branches.

I think that Visual Studio 2003 just doesn’t work well with integrated source control.

]]> By: Chris Coughlin http://bobondevelopment.com/2007/05/12/working-with-cvs-and-visual-studio/comment-page-1/#comment-1840 Chris Coughlin Mon, 14 May 2007 13:12:46 +0000 http://bobondevelopment.com/2007/05/12/working-with-cvs-and-visual-studio/#comment-1840 I was in the same boat last year, and in my web meanderings I eventually found <a href="http://www.daveswebsite.com/software/tamtam/index.shtml" rel="nofollow">TamTam CVS SCC</a>. Seems to be actively developed, and in my experience it works well. Might be worth a look. <em>Bob responds: Thanks, but the problem with TamTam is that it requires a specific CVS server (CVSNT) which my client isn't using.</em> I was in the same boat last year, and in my web meanderings I eventually found TamTam CVS SCC. Seems to be actively developed, and in my experience it works well. Might be worth a look.

Bob responds: Thanks, but the problem with TamTam is that it requires a specific CVS server (CVSNT) which my client isn’t using.

]]>