WinWrap® Basic is an embedded macro language component available for .NET and COM 32/64 bit Windows applications. The WinWrap® Basic Component is an alternative to Visual Basic for Applications (VBA), ActiveX (e.g. VBScript, JScript, PerlScript, Rexx-based WSH engines and others), and VSTA for this purpose. The WinWrap® Basic Component is compatible with VBA, Sax Basic, VB.NET and Visual Basic 6.0 style scripts.
Reading and writing files is a convenient feature, however, there are times when accessing the local file system in not desirable. In that case your application can redefine how the scripts are stored. In essence the VirtualFileSystem is merely a wrapper for file actions. This allows the "name" of script to be uncoupled from the "name" of the file. Of course, a complete uncoupling from the file system is possible. The virtual file system does not affect how script names starting with '*' are handled.
The following implementation of IVirtualFileSystem treats script names as simple names. Simple names are translated into full path names in the virtual file system implementation. This is a useful approach for virtualizing storage location within the actual file system.
The File Open and Save As menu choices request a file name from the user. If the file system is virtualized then GetMacroName event must be implemented also.
With the virtual file system the host application can read and write scripts anywhere. A database table mapping script names to script contexts can be where scripts are stored.
It can be important to isolate scripts from the rest of the real file system. When using Sandboxed true, virtualizing script storage completely away from the file system is desirable.
With the virtual file system script names can be "redirected" based on application context. For example, reading and writing scripts to the user's documents directory is easily achieved.
See WinWrap Examples for instructions on how to download and run "Example 7 - Virtual File System".
Copyright Polar Engineering, Inc.