VB6 applications use FRX files to store binary data associated with various control properties. This includes things as simple as formatted text for a text boxes, to images, and icons, to large BLOBs of proprietary information associated with ActiveX controls.
Likewise, .NET applications use Resx files to store binary data associated with the application. Resx files are XML files that contain contain designer metadata as well as base-64-encoded binary information i.e., bitmaps, icons). These files may also contain legacy ActiveX control property settings and binary information needed for interoped controls (i.e., OCXState).
gmBasic handles the most common types of FRX data (formatted text and images) automatically. However, one commonly used type of FRX data that is not handled automatically is the graphics associated with ImageList controls. If your application uses graphics from an ImagesList, you will need to use a Author Resx Files operation from the tools menu. This operation will process the FRX files and create Resx files containing the ImageList data in base-64-encoded format.
To run generate Resx files for ImageLists
- Select the migration units fro which you want to create to Resx files
- Select [Tools/Author Resx Files] from the menu
This will create a resx files for each migration unit in the migration project and store them in the resx folder in your workspace.
To direct gmBasic to use the Resx data from your resx files in the resx folder, you must set the Resx attribute of the Compile command in your translation script:
The standard way to do this is to use the %ResxFolder% script variable.
<Compile Project="%SrcPath%" Resx="%ResxFolder%">
See the FileExplorer sample for an example.