|
|
|
|
Help on MioFactory
TechNotes related to MioFactory
Libraries related to MioFactory
Products
|
|
Help 07. Publishing Applications | Product: MioFactory |
| |
When your application is completed and tested, it is time to publish it.
Publishing Applications with MioFactory
|
Executable| |
Any windows application created with MioFactory uses the run time MioEngine.
When you publish your application, the run time file is embedded with the program files to create an autonomous application file.
An executable file can be run or installed on any computer running Windows 95 or later with no additional download.
Two executable formats are available:
Autonomous Exe File
Creates an EXE file embedding the run time and the application files.
The EXE file can be executed on any computer running Windows 95 or later.
The application is not installed on the computer.
Installer
An installer can be embedded to the Autonomous Exe file so your application can be installed permanently on the computer.
Shortcuts can be added to run or uninstall the application and you can store data locally.
More information: 06. MioFactory Installer.
|
Mio File| |
.mio Application File
A mio file contains a compressed copy of the application files and the MioScript code files necessary to run the application.
As MioEngine is not embedded in the .mio file, it must be installed separately on the computer.
To run a mio file, MioEngine must be located in the same folder and renamed so the .mio and the .exe files have the same name.
Mio Files are generally used to install applications manually, and cannot be opened from within MioFactory.
More information: Deploying an application remotely.
.mioa / .mio Archive File
Archive files are used to create a backup copy of a project.
When a .mioa or .mio archive file is opened from within MioFactory, the contained files are expanded in the project folder.
A Mio archive files cannot be executed.
|
|
|
|
