Kbase 17006: ACTIVEX - Deployment Progress Application on NT & 95
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
1/4/2006 |
|
Status: Unverified
GOAL:
How to deploy a an ActiveX Progress application.
FACT(s) (Environment):
Windows 32 Intel
Windows NT 32 Intel/Windows 2000
FIX:
An ActiveX Progress application consists of a Progress application containing ActiveX controls. To deploy:
1) Save the Progress windows .WRX, .W and .R files on the machine
where the application was developed. By default, the UIB assumes
that .WRX files are in the same directory location as the .W file.
If you plan to separate the .WRX file from the .W file, please
ensure that either the .WRX file can still be located via the
PROPATH, or that you have changed the location of the .WRX file
via the UIB's Procedure property sheet.
2) Copy the .WRX and .R files (or encrypted source files); and the
ActiveX control files (DLL's or OCX's, for example), as well as
other associated files, to the deployment machine. See the
documentation for a list of the associated files required with
Progress. Also, refer to your ActiveX documentation for the list
of files you need to ship along with your .OCX files. Typically,
there is a list of DLL's which a control requires to be on the
deployment system. Please refer to the section called "Installing
system-wide shared files" below for additional information.
NOTE: The ActiveX controls shipped with the PROGRESS UIB are
automatically installed and registered with the PROGRESS
Runtime and Query products.
3) Register the ActiveX controls. This is done in the DOS Shell using
REGSVR32.EXE. This will allow Progress to use the control at
runtime. If this is not done, then licensing error messages will
be displayed and the control will NOT be instantiated/created at
runtime.
4) At the DOS Shell enter: PROWIN32 -p <filename.R>
5) The application should run without error.
6) When the user uninstalls your application, aside from removing all
the files belonging to your application, you must also unregister
any ActiveX components which you have registered. Please refer
to the section "Uninstalling system-wide shared files" below for
more information.
INSTALLING SYSTEM-WIDE SHARED FILES
===================================
A system-wide shared file is typically a file (i.e. DLL or OCX) which
is shared by more than one program on the users system. An example
of such a file is MFC42.DLL. There are a number of steps to follow
when installing system-wide shared files on a users system. These
are best handled with the assistance of a third-party installation
program such as InstallShield or Wise. OCX and DLL files are
typically installed into the users <windows dir>\SYSTEM (Win95) or
<windows dir>\SYSTEM32 (WinNT) directory. Make sure that you check
the version of any existing file before replacing it. Only attempt
to replace an existing file if the file version you are installing is
greater than the one already on the users system. When you are
attempting to install a more recent file, you must ask for
confirmation from the user before overwriting it. When a shared file
is busy and therefore cannot be replaced, you must ask the user to
reboot the system and replace the files during reboot. Windows
maintains a usage count of shared files in the Windows Registry. The
usage count represents the number of programs which depend on the
file. Any shared file you install must be looked up under the
registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVers
ion\SharedDlls. If it exists, you should increase the count by 1. If
it does not exist, you must create an entry for the file and set its
usage count to 1.
UNINSTALLING SYSTEM-WIDE SHARED FILES
=====================================
When the user uninstalls your application, you need to remove the
files which you installed. This includes the system-wide shared
files you installed into the users <windows dir>\SYSTEM or
<windows dir>\SYSTEM32 directory. You'll need to look up the usage
count for the file and decrement it by 1. If the usage count becomes
zero (0) as a result, you must get co.nfirmation from the user before
you delete it. If you delete the file also remember to delete the
registry key. NOTE: Not all software programs correctly maintain the
usage count for shared files. As a result, you should warn the user
that deleting the file may disable other software programs on their
system. If the file was registered on the system during install, you
must unregister it before you delete it. Use the command "regsvr32 /u
<filename.ocx>" to unregister the file..