Native Project Files which can be directly opened by TLIB 5.54c
---------------------------------------------------------------

    Borland C++ Builder Project (*.BPR)
    Borland Delphi (*.DPR)
    CodeWright project (*.PJT)
    CodeWright project space (*.PSP)
    Help Magician Pro project (*.HMP)
    Microsoft C# (C-Sharp) .NET project (*.CSPROJ)
    Microsoft Developer Studio / VC++ 5.0-6.0 project (*.DSP)
    Microsoft Developer Studio / VC++ 5.0-6.0 workspace (*.DSW)
    Microsoft VC++ .NET project (*.VCPROJ)
    Microsoft Visual Basic 3.0 (*.MAK)
    Microsoft Visual Basic 4.0-6.0 (*.VBP)
    Microsoft Visual Basic .NET project (*.VBPROJ)
    Microsoft Visual Studio .NET solution file (*.SLN)
    MultiEdit project (*.PRJ)
    SlickEdit project (*.VPJ)
    SlickEdit workspace (*.VPW)
    Symantec Visual Cafe (*.PRJ)
    Watcom C/C++ individual target (*.TGT)
    Watcom C/C++ project (*.WPJ)
    HTML web site files (*.HTML and *.HTM)
    SSI web site files (*.SHTML)
    plain file list (*.LIS)

    Note: if your tool's project file is not currently supported,
    give us a call.  We can probably add it.



TLIB's native project file support lets you manage your projects
with just one type of "project," rather than having to specify
the source files you use separately to your compiler and your
version control system.



For many native project files, one or more options can also be
specified to TLIB, such as "include binary files."

In the TLIB for Windows GUI, options are specified by checkboxes
when you open the project file.

In command-line versions of TLIB, native project mode is specified
by an "@@" prefix in front of the project file name, and options are
specified by numbers in [brackets] at the end.  For example, to
Update (check-in) all the files in a Microsoft Visual Basic 6.0
project, includng the binary source files, you would need to
specify the "include binary files" option as [1], like this:

  tlib32c u @@my_VB_program.vbp[1]



In addition, .LIS files can reference one or more other native
project files, also using the @@ syntax.  For example, this 3-line
.LIS file specifies a Borland C++ Builder project, a Borland Delphi
project, and a Microsoft Word documentation file, which can all be
handled as a one big project:

-------------- begin COMB_PROJ.LIS --------------
@@my_Cplusplus_program.bpr[2]
@@my_Delphi_program.dpr[1]
UserManual.doc
--------------- end COMB_PROJ.LIS ---------------

Once you've created COMB_PROJ.LIS, you can "open" it in the TLIB
for Windows GUI to manage the C++, Delphi and .doc files all
together.  Or you can use it with the @@ syntax to specify all
the files to command-line versions of TLIB, like this:

  tlib32c u @@comb_proj.lis



TLIB handles Web site "projects" by parsing the .html, .htm, and
.shtml files to find the references to other files, and then
parsing those files, etc..  In most cases, even file names embedded
in javascript will be found.  This means that you can simply use
your index.html or index.shtml file as a project file, and TLIB
will find all the files used in your web site.

Note, however, that you must have "drive letter" access to your
web site files.  Current versions of TLIB cannot retrieve them
via HTTP or FTP.





(C) Copyright 2001-2003, Burton Systems Software