Files available for source control

The following schema shows a directory structure for files in the local PocketBuilder workspace and on the source control server. Directories and files in the local root path that can be copied to the source control server from PocketBuilder are displayed in bold font. Asterisks indicate a variable name for a file and italic print indicates a variable name for a file or folder.

Figure 5-1: Directory structure in local path and source control server

At left is a box labeled Local Root Path. In regular type, because they cannot be copied to Source Control, are Workspace dot P K W and Workspace dot P K C. The P K C file is created if you indicate that you sometimes work off line. It contains source control status information. Also under the Local Root Path are asterisk dot P K T in bold font, asterisk dot P K L, dot P B G, and dot S R asterisk. The asterisk dot S R asterisk entry is also in bold font. At right is a box labeled Source Control Project. It lists the file extensions P K T, P K G, S R asterisk, and P R P. The P R P files are for P B Native source control only. . In regular type under the Web Target Directory are the Build Directory and Deployment Config, which are not under Source Control. All entries in bold also appear in the same order at right in a rectangle labeled Source Control Project.

Typically, the source control server files are stored in a database but preserve the file system structure.

Temporary files in local root path When you add or check in a PowerScript object to source control, PocketBuilder first exports the object as a temporary file (*.SR*) to your local target directory. For some source control systems, you might choose to delete temporary files from the local root path.