WinCVS Introduction

Installing WinCVS

Installing CVS Integration for Visual Studio

Working with WinCVS

CVS Home Page

For Administrators: Setting up CVS as a Server
under Linux

 

CVSln

CVS Integration Add-in for
Microsoft Visual Studio:

Working with the IDE

The User Interface

Toolbars.
    CvsIn Options - to invoke the Options dialog where you can change the CvsIn settings.
    Run WinCVS - launch WinCVS for the current file, or find already running one.

CVS commands toolbars:
   
CVS update - cvs update <active file>
    CVS commit - cvs commit <active file>
    Query CVS update - cvs -n update <active file>
    CVS diff - cvs diff <active file>
    CVS log - cvs log <active file>
    CVS status - cvs status <active file>
    CVS edit - cvs edit <active file>
    CVS unedit - cvs unedit <active file>
    CVS watch - cvs watch add <active file>
    CVS release watch - cvs watch remove <active file>
    CVS tag - cvs tag <active file>
    CVS untag - cvs tag -d <active file>
    CVS fork - cvs tag -b <active file>
    CVS unlock - cvs admin -u <active file>

    Addtional toolbars:
   
Graph - show the graph or revisions and tags (at the moment, this launches WinCVS.)
    Wizard - not frequently used CVS commands (add/delete etc.) and special tools (Not yet
    implemented)

Macro sheet in the Output Window. You will see all the messages from CvsIn here.

Status Bar - short information about the activated file will be displayed here. Currently it displays the information about file attributes in the following way:
    [rahs] - Read-only, Archive, Hidden, System.
   if the attribute is not set then the '-' is displayed.
   Example: [ra--] - Read-only, Archiv file.

Note:
You can use more commands and assign keybindings for easier access for all the functions.

A Few things to remember when using CVS commands:
If you receive an updated CVSln.DLL, you must uninstall the old one before installing the new one, and go through the complete setup procedure again.

You have to make sure CvsIn can see the cvs client (in our case, that would be WinCVS). Either add the location of the cvs.exe to your PATH, or specify the full path in the settings.

Remember that DevStudio doesn't scroll the output window - you will have to go to the "Macro" sheet of the Output window and place the cursor at the end - click there and then use "Ctrl+End".

Do NOT exit the DevStudio if the CVS command is running. If that happens - you will have to use the task manager and kill the process by hand. Remember, CVS is a separate thread. Try to be aware of when it's active and when it isn't.

If you use the Dial-up connection - it is better to select 'Dial-up' in the CvsIn Options->CvsIn or the Dial-up dialog won't popup - it's a Microsoft bug.

At the moment the graph button calls WinCVS to do the graphing. There is no self-contained graphing as of yet. The wizard bar isn't finished either, but we'll be getting updates as we go.

Controlling WinCVS Sessions

CvsIn options

You can easily manipulate your WinCVS sessions. By pressing the control keys while pushing the 'RunWinCVS' button you'll get various behaviors.


Ctr+'RunWinCVS' - this will invoke the sessions manager, which will allow you to:
    Refresh the list of running sessions
    Switch to selected seesions
    Open new session for the selected file - previous session is closed!
    Close the selected session
    Close all sessions
Note: The list control is hot - one click activate!Ctr+Shift+'RunWinCVS' - the list of active sessions will be printed to the Output Window

Shift+RunWinCVS - open the new WinCVS session without the attached file, regardless of the active file exists or not. It is useful to emulate the 'single instance of Browser (WinCVS)' working model model.