Visual APL provides significant support for the legacy Native 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 Native 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 Native 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 Native File System assembly in your project and you are set. Nothing more to it.

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

You can store any serializable object in your native 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.

This means you never have to store your data in a proprietary format again, just write the data to the native file and you are done. Any other .Net language or application can read and write your data, even nested arrays.