CVS and Source Control Plug-Ins

Question

Hey all,

I have been using a CVS-NT server installed on a Windows Server 2003 box for source control. I was also using the PuskOK CVS-SCC proxy plug in (from www.pushok.com) to access the repository from the IDE on a networked WinXP machine, and access the repository using sspi and windows authentication. It worked well under VS2003. I have not made any changes (indeed, it still works well under VS2003), but VS2005 Team System does not remember that I am using the PushOK proxy when I restart the IDE, it will not bind back to the CVS repository for source control when I open the project from my local checked out version, it will not check out files from the repository when I edit them, and it does not show edited files as checked out from the CVS repository. I can open the solution from the CVS repository, but after that I might as well not have source control.

I guess I am curious if I am the only one with this problem, or if there is something I am not setting correctly in VS2005 (it just worked in VS2003). I just fear my only option is moving everything to VSS or maintaining everything with Tortoise CVS.

Thanks,

Bill

Answer 1

Unfortunately, I have yet to find a good CVS SCC plugin for VS.  Despite the horrid user interface, I've found WinCVS to be the least objectionable way to access a CVS repository from Windows.  Tortise works too, but with WinCVS, you can apply filters to see all changed files underneath a given directory to make it easy to commit them all at once.

--Oren

Answer 2

OK, I played with some options and think I got the pushok plug-in to work. In the Source Control Environment options, I selected independent developer source the environment settings then unchecked the box for "Keep items checked out when checking in" (this changed the combo box to custom). Then, when I open a solution, I open it from source control (not the convenient start page link). I think the key was actually opening the solution from source control. It seems loading the solution from the start page link causes the IDE to forget about the source control settings.

Now, when I edit the code, it checks the file out of the repository, and checks things in when I close VS.

BTW, Oren, I also have WinCVS. The GUI is as aweful as you say. Thats why I like TortoiseCVS. It is an add-on to Windows Explorer. Items under source control show up with icons indicating if they are up to date or not. Also, you can add CVS related details (such as modified and revision number) to the detail list in Windows Explorer, and sort files by them. WinCVS just seems the most powerful of all of the tools, and is a must-have to fix things when nothing else will work. I also like WinCVS's revision graph.

Bill

Answer 3

I've been developing a new CVS SCC plugin for Visual Studio.Net called TamTam that is currently in beta that you may want to check out. I've used other products before but I wanted to write my own that was faster, cleaner, more efficent, and automated as much as possible. 

You can download the latest beta and the final version which I hope to have ready by late October here ...

http://www.daveswebsite.com/software/tamtam/default.shtml

dave.

Answer 4

Is there anything stopping you from still using somthing like tortiose cvs by "right-clicking" in  Explorer to "check-out", "Up-date" and "Commit". your VS2005 projects or does VS dirty all the files ever time they are opened.

Answer 5

We are using cvs-suit.  Which Includes a vs-add-in and tortoise.   But It does not work well on x64 (in fact it is very broken)

The add-in seems to require tortoise and tortoise is a 32 bit extension that only works in the open dialog box.

It does not seem to work nativley in 64 bit mode.