newObjects Active Local Pages - support area
|last updated 28 May 2002|
ALPInstall 1.1 notes
Version 1.1 of ALPInstall adds some new features and deals with much more situations automatically. the best way to review it in action is the ALPRedistApp.zip package which implements setup example - containing ALP and an application. To build your own you just need to put your application(s) in the package, change texts in the setup.cfg and modify paths and other settings where needed.
The new features:
In the sample BASEDEST variable is used as BasicAppLocation (see the main section). This directory is used by the setup to store the uninstall information and install/uninstall logs. When testing or solving problems consult these log files - in most cases any problem can be caught for a seconds by finding the error listed in the log.
Avoid changing the variables used by the ALP components. Better add more variables if you need to define more locations. Note ALPRoot option in the InstallCG sections. It points the directory where the default alp.site, alp.application and alp.directory files are copied. This is required by these components because they must be registered in these files - therefore if you change the ALP locations you will need to check if this option is still correct.
It is strongly recommended to leave ALP to install itself as it is defined in the sample file. If the user obtains another ALP application from another vendor it will try to update the ALP engine and keeping ALP engine in its standard location will prevent multiplication of the ALP files in many locations.
See the TESTPC directory included in the setup. It contain example ASP pages which test the system for the most commonly used MS ActiveX-es by the ASP pages. Read the comments in them and tune the pages for your application. Do not spend to much time to redesign them - they are shown only once (and only if component is missing or is older then specified) thus only the texts describing what to do are important. If you want to design an online page containing the updates on your site use the update.asp as an example. Or if you want to put these updates on the CD get them (see the comments in the page) and put them in a subdirectory of TESTPC and alter the paths in the update.asp to point them. What instructions to write there? Tell the user to install everything listed and if restart is required by one of the setups to select "no", install the resting files and then restart the system. Also if you want to provide files for non English OS versions - see on the MS site if they are available and put more links with appropriate description.
|Copyright 2001 newObjects|