Hi, very good question, it depends on your application and involves some planing and categorizing:
-New installation, -User defined installation -Update of an existing system How did we solve that problem? -The planning starts by starting the devellopment. Always thing of an easy installation and deployable methods. i.e. we did not change anything on the cache configuration that needs later on human involvment during the installation process. -we installed cache by recording the clicks using the installshield methods descriped in the Silent installation process of cach�. -we created our own methode for checking which class and methode to select into a distribution file by modules for deploying and updating an existing version and create an update file that contains all the help files, classes, system globals and methods. This procedure also helps for the automated version control and is part of our customer service module (which customer has which version) - we created our own install shield. Here is a small (not total) script that maybe helps you or give some hints: a) start CD with autorun, introduce Company and the install process b) ask for "licence" and let the user check the "read me file" c) ask for drives, and needed space, check needes disc space d) ask for installation method (new, user defined, update) e) check for internet information server, If not, than branch to apache installation (if you have CSP) f) if methode = new, start auto silent installation of cache if not jet installed g) if methode = new, shut down cach� h) if methode = new, copy your cache.dat (your distribution environment) into the customers directory i) if methode = new, start cach� j) look for the update file, and load the update file, notify existing online user of the update. k) start your cach� methode for unzip the update file into classes and methode. start other automated procedures needed in your new version (recreate Index, update Customers files,and so on...) l) start compiler for all methods and classes. m) copy icons, pdf documentation to the desktop and program groups for easy access. n) install the uninstaller o) congratulate the user p) finish, prompt user for restart the system (if installation method= new) once you compile such a install shield you can reuse the install environnment for all the installations and updates if you do not comile the variable files (cache.dat and updatefile) into the installation process. Then you simply change the 2 files and distribute a new versions over and over without recreating the installer. Ditmar "haiphy" <[EMAIL PROTECTED]> schrieb im Newsbeitrag news:[EMAIL PROTECTED] > when i complete the develope work, > and need to release myself system, > > How to release my db to customer's cache System? > > thanks! > >
