Package Management
In twinBASIC, a package is a collection of components that you can reference from another twinBASIC project. The components can be modules, classes or interfaces.
twinBASIC comes complete with a package manager service called TWINSERV1, allowing you to share and distribute TWINPACK packages to other twinBASIC developers.
A twinBASIC package is distributed as a TWINPACK file that contains everything needed by the components in that package. A project that references a TWINPACK package, imports the whole package into the file system of the root project, resulting in no external dependencies.
With TWINPACK packages you group common components together into their own namespace whilst allowing for convenient code reuse without any of the problems often associated with using external DLL libraries.
Please be aware that TWINPACK files currently contain the full source code of your packaged components. It is planned that we will in future allow for creating binary (compiled) TWINPACK files for developers that hold an Ultimate edition licence of twinBASIC.
Topics
- Creating a TWINPACK Package – packaging twinBASIC components into a distributable TWINPACK file.
- Importing a Package from TWINSERV – browsing and installing packages from the TWINSERV online repository.
- Importing a Package from a TWINPACK File – installing a package from a local TWINPACK file.
- Linked Packages – storing a package in a shared location rather than embedding it in each project file.
- Updating a Package – removing an outdated package and installing a newer version from TWINSERV.
- TWINPACK File Format – binary format specification for
.twinprojand.twinpackfiles. - Import/Export Tool – standalone command-line tool for unpacking and repacking
.twinprojand.twinpackfiles.
-
A service of TWINBASIC LTD offered to the user community. ↩