Eh, nevermind (25 October, 2006)
So, as Mathieu so kindly pointed out in the comments section, PushOK does a VS.NET 2003 add-in for CVS rather inexpensively. While I was looking forward to actually creating an add-in for VS.NET, the time I have to play with it just doesn't exist, so I'm scrapping this one. I may play with it some in VS.NET 2005 at home (I don't have 2003 installed at home anymore), so this might actually go somewhere, but who knows where and when.
Starting Out (06 October, 2006)
My company is switching is source control from the woefully in adequate Visual SourceSafe to CVS. I don't know why they refuse to go to Microsoft Team Server, but I suspect that it has a great deal to do with CVS being free, and TeamServer being expen$ive.
Specifically, we are instructed to use the WinCVS client to access the source code in CVS. After plenty of reading, I realized there is currently no way to access WinCVS through the VS.NET IDE like there is for VSS. I have never created an Add-In for VS before, and thought it sounded somewhat interesting task to tackle. I know it is possible to create one because I see them for sale online for anywhere from $10 to over $200.
I did some queries on Windows Live search looking for add-in information. I got a lot of places selling add-ins, but nothing in the way of how to create one. Then I got the bright idea thinking that if any place would have information on creating an add-in for VS, it would be VisualStudio Managzine.
3 comments:
There is CVSProxy from PushOK that worked for me on VS2003, just in case you want to take a look!
oh... sounds like its not "free" but not crippled either... anyway you might want to take a look at it!
http://www.pushok.com/soft_cvs.php
Thanks mathieu, the powers that be decided to use just that. But I'm still going to play with it since I have never created an add-in and now I have a reason to actually do that.
Post a Comment