---------------------------------------------------------------------
 TLIB Version Control Add-In for Visual Basic 5.0 Installation Guide
---------------------------------------------------------------------

 Table of Contents

1 - Requirements for Operation

2 - Installing the TLIB Add-In for Visual Basic 5.0

3 - TLIB Commands added to Visual Basic 5.0

4 - Visual Basic's problems with read-only files


---------------------------------------------------------------------
 Chapter 1 - Requirements for Operation
---------------------------------------------------------------------

 1) The TLIB Add-In for Visual Basic ("TLIB/VB") uses the TLIB for
    Windows engine, so make sure TLIB Version Control for Windows is
    installed and working.  (TLIB for Windows needn't be running when
    you install and use the TLIB Add-In for VB, but it does need to be
    installed.)

 2) TLIB/VB is intended for use with TLIB's check-in/out locking feature
    enabled (to coordinate multiple programmers), i.e., with LOCKINGY
    or LOCKING B configured in the TLIB.CFG file.  TLIB/VB will operate
    fine with locking disabled, but you will not see some of the features.

 3) Do not attempt to use the TLIB/VB from the "VB Add-in Toolbar"
    add-in.  If users request this ability, it may be added later.
    (Be sure to let us know if this is important to you).

 4) TLIB/VB adds commands to your 'Tools' and several sub-menus.  If you
    have manually modified (or removed) these menus too extensively,
    TLIB/VB may not integrate correctly.

    To restore the original VB menu(s), shut down TLIB/VB from the
    add-ins menu.  Then, right click anywhere on the VB menus, and
    choose 'customize' from the popup menu.  Choose the menu you need
    to restore from the list and then click the 'reset' button.

 Note: This version of the TLIB/VB supports all three "regular" versions
    of Microsoft Visual Basic 5.0:  Learning Edition, Professional
    Edition, and Enterprise Edition.  However, it does not support the
    free Control-Creation Edition of Visual Basic 5.0.


---------------------------------------------------------------------
 Chapter 2 - Installing the TLIB Add-In for Visual Basic 5.0
---------------------------------------------------------------------

 Step 0)  Make sure your TLIB Version Control for Windows is installed
   and working.  (However, TLIB needn't be running when you install and
   use the TLIB/VB.)

   Note: The SETUP.EXE program that installs TLIB can also install
   TLIB/VB; in that case, you can skip steps 2 & 3, below.

 Step 1)  Shut down Visual Basic 5.0.

 Step 2)  Install the TLIB/VB Add-In:

   The TLIB Add-In for VB 5.0 is TLIBVB5.EXE.  Copy or PKUNZIP it into
   the directory which already contains TLIB.EXE, WTLIB16.EXE, and
   TLIBDLL.DLL.  DO NOT put it anywhere else!

 Step 3)  Set up the Registry and VBADDIN.INI entries:

   Just run TLIBVB5.EXE.  You can use Start-Run, or double-click on it
   in Windows Explorer, or run it from a DOS Box prompt.

   If this is the first time you've installed a TLIB Add-In for VB 5.0,
   you will see the message:

     "TLIB add-in installed..."

   Click OK.

   Note that no message will appear if TLIB/VB was already listed in the
   'vbaddin.ini' file.

 Step 4)  Enable the TLIB Add-In within the VB 5.0 environment:

   Start VB 5.0.  Click Add-Ins.  Click Add-In Manager.  There will be a
   new Available Add-In listed, "TLIB Version Control for Visual Basic
   5.0."  Click on it, to make the check mark appear.  Click OK.  You
   should see the TLIB/VB progress window appear and begin to check your
   project.  (If you do not have locking enabled, this will happen so fast
   you will only briefly see this window.)  TLIB for VB 5.0 is installed!

   TLIB/VB will automatically start whenever you run VB as long as it is
   enabled (checked) in the add-ins menu.


---------------------------------------------------------------------
 Chapter 3 - TLIB Commands added to Visual Basic
---------------------------------------------------------------------

  After TLIB/VB is installed, TLIB Version Control commands appear on
  your tools menu.  We've used Microsoft terminology for some of these:

     "Get" means browse-mode extract ("EB" or "EBF").
     "Check Out" means extract for modifications ("E").
     "Check In" means update ("U")
     "Undo Check Out" means "Update/Discard ("UD").
     "Version Control Options" means TLIB Configuration Options.

  Also, some TLIB commands are available on various VB 5.0 right-button
  menus.  Open a VB project, and in the project window select one of
  the modules, forms, classes, user controls, or property pages.  Then
  click the right mouse-button.  The menu contains:

     "Delta Compare" lets you compare versions of a module, form, etc.
     "Version History" lets you view the TLIB version history
     "Check Out" (same as Check Out on the Tools menu)
     "Check In" (same as Check In on the Tools menu)

  Note that not all TLIB commands are accessible through the TLIB Add-In
  for VB 5.0.  For some operations (like creating snapshots or new
  libraries), you'll need to run TLIB for Windows directly.


---------------------------------------------------------------------
 Chapter 4 - Visual Basic's problems with read-only files
---------------------------------------------------------------------

  VB occasionally attempts to write a read-only file, even though
  'strict read-only mode'** is set and the file should never have been
  allowed to change.

  TLIB/VB intercepts these write requests and does not allow them.  You
  will get a notification message when this happens.  With SROM** Visual
  Basic will not allow you to change anything that REALLY matters; i.e.,
  if you attempt to edit code or move a control on/in a read-only file
  it will not let you (try it and see)..

  So how does it ever happen; when does VB allow Read-Only files to change?

  The most common scenario is when do not you have the project file (.VBP)
  checked out (it is read-only) and 'auto-increment' version # on the
  'make exe' dialog in VB.  In this case, VB will mark the Read-Only VBP
  file as 'Dirty'## every time you make an EXE, so the next time you try
  to save after this it will fail and prompt you for a new name for the
  project.

  Note that if you do not have the TLIB add-in running and you are working
  on a still-checked out (read-only) project, you are on your own --
  TLIB/VB can only intercept and correct these problems for you when it is
  running.

** Strict Read-Only Mode is a little-known, almost secret hidden feature in
   VB -- You cannot toggle it from anywhere in the VB GUI.  It is always
   set when TLIB/VB is running and TLIB's check-in/out locking facility
   is enabled (in tlib.cfg).

## A file is 'Dirty' when the property 'IsDirty' is true -- It means 'This
   file has been changed since it was last saved.'


---------------------------------------------------------------------
[TLIBVB5.TXT] 3-May-97
