After you create an ATEasy application, you can distribute it to your users. Marvin Test Solutions gives you complete rights to distribute any application you create with ATEasy. You can distribute your applications on floppy disk, on CD ROM, or over a network.
ATEasy executable application requires the ATEasy Run-Time to be present on the target machine in order to run. You will need to install ATEasy Run-Time on the target machine. This can be done in two ways:
Install ATEasy
and select the Run-Time installation
type
Incorporate the ATEasy setup to your setup, thus installing ATEasy in silent (automated) mode
The run time is installed to the ATEasy Installation Folder: for version 9 or newer it is installed to the system 32 bit Program Files folder, ATEasy x.0 folder (for example C:\Program Files (x86)\ATEasy 9.0, for 32 bit machines C:\Program Files\ATEasy 9.0, for version 8 or older it is installed to ATEasy folder below the system program files..
The ATEasy run-time contains all the run time files requires to run an ATEasy EXE or DLL including:
● ATERT.DLL - ATEasy Run-Time and Internal Library, for ATEasy version 9 or newer it installed to the ATEasy Installation Folder, for ATEasy 8 or older it is installed to Windows system folder.
● ATECTL.DLL - ATEasy Control Library, for ATEasy version 9 or newer it installed to the ATEasy Installation Folder, for ATEasy 8 or older it is installed to Windows system folder.
● ATEasyPanel.cpl - ATEasy Run-Time Configuration, used to configure ATEasy interfaces (for example GPIB or VXI interface boards), for ATEasy version 9 or newer it is installed to the ATEasy Installation Folder and can be opened from the Windows Start menu, for ATEasy 8 or older it is installed to Windows system folder and can be opened from the Windows Control Panel. See Adding and Configuring External Interfaces - Options Tab for more information.
● Interface DLLs for GPIB, VXI interfaces, installed to ATEasy Installation Folder.
If your application uses external libraries such as DLLs, ActiveX components or .NET assemblies, you need to distribute these components as well. See Distributing a DLL for information on distributing DLLs. If you have imported type libraries (ActiveX) from other vendors into your application, you need to either distribute these type libraries to your users or require that they have the necessary components installed on their systems. See Distributing a Type Library for information on distributing type libraries.