Or click the "Mode" button to switch from normal (file-oriented) mode into compiler-native project mode.

Compiler-native project mode lets you “open” your compiler's native project file in TLIB, avoiding the need to use wild-card specifications or file-lists. Just click the "Mode" button to switch between compiler-native project mode and normal (file-oriented) mode.

TLIB currently supports the compiler-native project files of MS Visual Basic 3.0-5.0, Watcom C/C++, Borland Delphi, MS Developer Studio 5.0 (VC++/VJ++/etc.), Symantec Visual Cafe, the MultiEdit editor, the Codewright editor, and Help Magician Pro. Support for additional compilers and editors is planned.

The TLIB Version Control Add-Ins for Visual Basic 4.0 and 5.0 integrate the most commonly-used TLIB commands seamlessly into the Visual Basic 32-bit IDE.

(In VB 4.0, the TLIB Add-In creates a TLIB Version Control sub-menu under Visual Basic's Add-Ins menu. In the Professional Edition of Visual Basic 4.0, TLIB also enables the Check-In and Check-Out menu items on the Tools menu. Those menu items are not present in the Standard Edition of Visual Basic 4.0, but we have duplicated them in the TLIB Add-In sub-menu, so you do not need the Professional Edition of Visual Basic 4.0 to use TLIB's Add-In.)

To check-in (update) or check-out (extract) a source file, or to compare versions or view the revision history of a file, simply pick the appropriate menu item from within VB. Or, for less commonly-used functions, such as taking a "snapshot" version label of your project, just run TLIB for Windows in compiler-native project mode and open the VB project file. Version Control for Visual Basic programmers has never been easier!

D

PO Box 4157
Cary, NC 27519-4157  USA
Tel: (919) 481-0149 or (919) 481-6658
Fax: (919) 481-3787
Email: tlibinfo@burtonsys.com (or support@burtonsys.com for technical support)

Last modified: 23-Dec-01 (version 20)
Copyright © 1997-2001, Burton Systems Software.