Using FileTransfer2
13
FileTransfer2
All Projects and associated Systems and System files are linked to the Workspace, so that you can
add and remove Projects and Systems without having to make copies of the files. NetLinx Studio
also allows you to copy and paste Projects within the Workspace; in the case that you need to create
several similar Projects you can quickly generate multiple Projects and modify each one as
necessary.
Workspace files also allow you to build (compile) multiple Projects/Systems. The Build Workspace
command (in NetLinx Studio) compiles every file contained in the Workspace.
It is important to note that in NetLinx Studio (v2.0 and later), there is no concept of Projects outside
the context of a Workspace. A Project can only be opened by adding it to a Workspace. This is to
support the file linking aspect of the program.
Other features of the Workspace file include:
You can import other Project or Systems folders from previously saved Workspace files.
You can copy and paste existing Projects and Systems within a Workspace.
You can edit the identifier that is used to display the workspace name in the tree display
along with the description for the Workspace file via the Workspace Properties dialog.
You can export all the files associated with the Workspace (including the Workspace file)
into a .ZIP file.
Workspace-To-Go Files (*.AXW)
The Export Workspace Files To Go option (in NetLinx Studio v2's Project menu) allows you to
export the currently open Workspace for distribution as a Workspace-To-Go (*.AXW) file.
AXW files preserve all relative file path information for the Projects, Systems and System files
contained in the Workspace, making them ideal for distribution to remote sites.
As is indicated in the Export Workspace Files To Go dialog (in NetLinx Studio v2), there are three
major points to understand when exporting your Workspace files:
All files will reside in the same directory as the APW file upon extraction of the AXW
file.
No directory/path information is required for the "To Go" APW File Name.
You may enter non-existing folders - NetLinx Studio will create them for you.
Since all System files are linked to the Workspace, when you open a file for editing,
you are opening and editing the actual file, not a local copy. It is important to
understand that in the event that the file is linked to multiple Systems, any changes
made to the file will be reflected in every instance that the file is used (not just the
System that you were in when the changes were made). Even if you don't have
multiple links to the same file, you should still be careful about altering the file. If you
are linking to a file that other people might use, they will be affected by the changes
you make to the file. So, if you intend to make changes to a System file, and you want
those changes to be specific to only one System in the Workspace, you should make
a copy of the original file (under a different name), make your changes, then remove
the original file from the System and link the new file to the System.
