CVS in VC IDE
-
Can anybody can integrate CVS version control with the Visual Devstudio IDE? My company is migrating there right now(BIG mistake), so I am trying to find a civilized way to work with it instead of the command line or WinCVS things...
Preston Bannister (http://members.home.net/preston) is leading an effort to write a wrapper that will integrate WinCVS (www.wincvs.org) with the Visual C++ IDE. The project so far can be found at http://members.home.net/preston/cvsscc.html, but it's not really functional yet. If you open a VC++ workspace with Preston's CVSSCC installed, the icons in the VC++ workspace window reflect whether the files in the project are under source control and whether they're modified, but the actual CVS functionality is not yet implemented (i.e., you can't get histories, logs, or diffs; can't check in, commit, or update). Part of the problem with this is that while there is a desire for this to be an open source project, the actual specifications for the Source Code Control (SCC) interface to VC++ are a trade secret of Microsoft and are available only under Nondisclosure Agreement, so Preson can't release the source willy-nilly. That said, Preson's site requests volunteers to help with the task and there are a number of things that can be done even without signing Microsoft's NDA for the pieces that hook into the VC++ IDE. Preston's architecture is to make WinCVS a COM Automation server and call it from a small DLL that hooks into the IDE. The IDE part is pretty much done and the COM Automation interface is stubbed out in WinCVS, so the real work is to hook up the COM automation functionality. I will also note that while I am helping out on that project in my copious spare time, I am also finding WinCVS so easy to use in conjunction with VC++ that I don't really miss the integration with the VC++ IDE.
-
Preston Bannister (http://members.home.net/preston) is leading an effort to write a wrapper that will integrate WinCVS (www.wincvs.org) with the Visual C++ IDE. The project so far can be found at http://members.home.net/preston/cvsscc.html, but it's not really functional yet. If you open a VC++ workspace with Preston's CVSSCC installed, the icons in the VC++ workspace window reflect whether the files in the project are under source control and whether they're modified, but the actual CVS functionality is not yet implemented (i.e., you can't get histories, logs, or diffs; can't check in, commit, or update). Part of the problem with this is that while there is a desire for this to be an open source project, the actual specifications for the Source Code Control (SCC) interface to VC++ are a trade secret of Microsoft and are available only under Nondisclosure Agreement, so Preson can't release the source willy-nilly. That said, Preson's site requests volunteers to help with the task and there are a number of things that can be done even without signing Microsoft's NDA for the pieces that hook into the VC++ IDE. Preston's architecture is to make WinCVS a COM Automation server and call it from a small DLL that hooks into the IDE. The IDE part is pretty much done and the COM Automation interface is stubbed out in WinCVS, so the real work is to hook up the COM automation functionality. I will also note that while I am helping out on that project in my copious spare time, I am also finding WinCVS so easy to use in conjunction with VC++ that I don't really miss the integration with the VC++ IDE.
The Preston approach goes to far perhaps, since I don't quite care about the icons in the project files view if M$ is making so big deal about that. The quite simple ADDIN could solve the problem, together with, let's say, Window Tabs Oz addin... There is one tool called CVSThings, but this one is an external tool, I want addin, no need to be integrated at first (can't have it all see)... ================== The original message was: Preston Bannister (http://members.home.net/preston) is leading an effort to write a wrapper that will integrate WinCVS (www.wincvs.org) with the Visual C++ IDE. The project so far can be found at http://members.home.net/preston/cvsscc.html, but it's not really functional yet. If you open a VC++ workspace with Preston's CVSSCC installed, the icons in the VC++ workspace window reflect whether the files in the project are under source control and whether they're modified, but the actual CVS functionality is not yet implemented (i.e., you can't get histories, logs, or diffs; can't check in, commit, or update).
Part of the problem with this is that while there is a desire for this to be an open source project, the actual specifications for the Source Code Control (SCC) interface to VC++ are a trade secret of Microsoft and are available only under Nondisclosure Agreement, so Preson can't release the source willy-nilly.
That said, Preson's site requests volunteers to help with the task and there are a number of things that can be done even without signing Microsoft's NDA for the pieces that hook into the VC++ IDE. Preston's architecture is to make WinCVS a COM Automation server and call it from a small DLL that hooks into the IDE. The IDE part is pretty much done and the COM Automation interface is stubbed out in WinCVS, so the real work is to hook up the COM automation functionality.
I will also note that while I am helping out on that project in my copious spare time, I am also finding WinCVS so easy to use in conjunction with VC++ that I don't really miss the integration with the VC++ IDE.
-
The Preston approach goes to far perhaps, since I don't quite care about the icons in the project files view if M$ is making so big deal about that. The quite simple ADDIN could solve the problem, together with, let's say, Window Tabs Oz addin... There is one tool called CVSThings, but this one is an external tool, I want addin, no need to be integrated at first (can't have it all see)... ================== The original message was: Preston Bannister (http://members.home.net/preston) is leading an effort to write a wrapper that will integrate WinCVS (www.wincvs.org) with the Visual C++ IDE. The project so far can be found at http://members.home.net/preston/cvsscc.html, but it's not really functional yet. If you open a VC++ workspace with Preston's CVSSCC installed, the icons in the VC++ workspace window reflect whether the files in the project are under source control and whether they're modified, but the actual CVS functionality is not yet implemented (i.e., you can't get histories, logs, or diffs; can't check in, commit, or update).
Part of the problem with this is that while there is a desire for this to be an open source project, the actual specifications for the Source Code Control (SCC) interface to VC++ are a trade secret of Microsoft and are available only under Nondisclosure Agreement, so Preson can't release the source willy-nilly.
That said, Preson's site requests volunteers to help with the task and there are a number of things that can be done even without signing Microsoft's NDA for the pieces that hook into the VC++ IDE. Preston's architecture is to make WinCVS a COM Automation server and call it from a small DLL that hooks into the IDE. The IDE part is pretty much done and the COM Automation interface is stubbed out in WinCVS, so the real work is to hook up the COM automation functionality.
I will also note that while I am helping out on that project in my copious spare time, I am also finding WinCVS so easy to use in conjunction with VC++ that I don't really miss the integration with the VC++ IDE.
If you don't want to hook up with the MS SCC API, then why bother with an add-in? To me, running WinCVS and switching between it and VC IDE is no pain. It's not clear what you would want the Add-In to do. ================== The original message was: The Preston approach goes to far perhaps, since I don't quite care about the icons in the project files view if M$ is making so big deal about that. The quite simple ADDIN could solve the problem, together with, let's say, Window Tabs Oz addin... There is one tool called CVSThings, but this one is an external tool, I want addin, no need to be integrated at first (can't have it all see)...
-
If you don't want to hook up with the MS SCC API, then why bother with an add-in? To me, running WinCVS and switching between it and VC IDE is no pain. It's not clear what you would want the Add-In to do. ================== The original message was: The Preston approach goes to far perhaps, since I don't quite care about the icons in the project files view if M$ is making so big deal about that. The quite simple ADDIN could solve the problem, together with, let's say, Window Tabs Oz addin... There is one tool called CVSThings, but this one is an external tool, I want addin, no need to be integrated at first (can't have it all see)...
>>why bother with an add-in? Because it does not require NDA... >>It's not clear what you would want the Add-In to do. I want it to perform the basic operations on the open documents to begin with, also tell me the status, install watches on the file etc. Later on it can evolve of course... >>To me, running WinCVS and switching between it and VC IDE is no pain. To me it is, and more-other, it is dangerous! We already have two accidental removal of the files from repo, and some missing changes as well. It is not correct to launch the external tool to do the job. This is good example of something I call UNIX syndrom (with all respect) - why I need a windows, I have a command line!? The truth is that the command line tools are powerful indeed, but without the GUI wrappers are source of troubles. That is why you like WinCVS, isn't it? So, to stuff the thing into your IDE environment is just the same thing, but gives even more security! This is the next step, and the only way to make the job done. Yes, I don't like CVS. But if I have to use it, I will use it properly, make it working for me, not me working for it. Because it is a computer who is going to do the job, not me wasting my time and doing the things should be done automatically. Simple. COMPUTER IS FOR SERVING THE HUMAN, NOT THE HUMAN IS TO SERVE THE COMPUTER!!! Otherwise, we don't need this things at all, lets just use pencil and paper!? ================== The original message was: If you don't want to hook up with the MS SCC API, then why bother with an add-in? To me, running WinCVS and
switching between it and VC IDE is no pain. It's not clear what you would want the Add-In to do.