Visual APL provides significant support for the legacy Share File System as a separate assembly

To meet the demands of IT environments Visual APL, unlike legacy APL's, does not require access to the file subsystem.

Legacy APL's all require access to the file subsystem because of the built in Share File System.

More and more IT departments are requiring that applications not include file access of any kind, and with .Net they have the tools to enforce this requirement.

To meet this need Visual APL provides the Share File System as a separate assembly.

This means when you build an application or DLL with Visual APL you meet this requirement automatically.

If your application does need file access, simply include the Share File System assembly in your project and you are set. Nothing more to it.

The Share File System in Visual APL implements not only what you expect, but a lot more.

No longer are your Share Files proprietary, any other .Net language can read and write to your Share Files.

You can store any serializable object into your share file. That means new datatypes like Hashtables and Dictionaries can be saved to file.

In addition, since all non primitive data is stored using the .Net standard ISerializable your data is not stored in a proprietary format.

This means that even APL nested arrays, which can now contain any object, will be saved in a standard ISerializable format which any other .Net application can read.

The Visual APL Share Files also supports virtual directories and multiple Share Files in one physical file.

This means that you can have a single project file for all your share files and then when the user needs to copy his project all that is needed is to copy a single file.