List of Figures


Chapter 1: Deployment Fundamentals

Figure 1. How successful do you think NASA would be if it waited until the moment it was ready to release a satellite into orbit to plan the deployment?
Figure 2. Creating an installation setup places your application in the same professional league as the shrink-wrapped software your clients purchase on the Internet or at a local computer store.
Figure 3. Cleaning out the report metadata before moving the application reports into production is a lesson most developers learn the hard way.
Figure 4. Visual FoxPro stores relative paths in the Database property of the cursor object. This can create errors in your application if you do not change the property at runtime or locate the database in the same relative folder structure in production as it is on the development machine.
Figure 5. Backend databases like SQL Server give database administrators the ability to set security down to the column level for application users. This security can affect your application in a negative manner if it is not accounted for during testing.
Figure 6. Marking files as excluded in a project means they will not be included in the executable during the build process. In this project the free table and one report would need to be deployed along with the executable.
Figure 7. The Visual FoxPro 8 Code References Tool gives developers the ability to search for strings and open the code in the appropriate editor.

Chapter 2: Planning for Success

Figure 1. The Microsoft System Information application provides an inside look at the computer including hardware configuration and software settings.
Figure 2. We have all run into the situation when the hardware infrastructure is a bit underpowered. This is a picture of an IBM PC from the early 1980s.
Figure 3. You can edit the Config.NT file using a standard text editor to update the file handles option to something more in line with what your applications require.
Figure 4. You can add the files statement for Windows 98, 98 SE, Me, and XP via the Microsoft System Configuration Utility. Otherwise you need to edit the SYSTEM.INI file via a text editor.
Figure 5. It came highly recommended that all the memory settings for the shortcut (or the PIF file) be set to Auto for better stability. Additionally you can set the compatibility mode to a specific operating system on the Compatibility page.
Figure 6. Organizing the network wires lowers the overall support costs, but requires up front planning.
Figure 7. Icon Studio is an excellent tool to create icons.
Figure 8. Microangelo is highly recommended by fellow Visual FoxPro developers.
Figure 9. Image editors allow you to crop images, fix flaws, adjust contrast, change color , and add some special effects.
Figure 10. The EXE Version Dialog.
Figure 11. The development tradeoff triangle

Chapter 3: Packaging the Installation

Figure 1. The Build Options Dialog is critical to determine the contents of the executable you are going to deploy.
Figure 2. Selecting the Debug Info bloats your executables by including the source code for the application into the EXE file.
Figure 3. Selecting the icon on the Project Information page determines the icon that displays in Windows Explorer.
Figure 4. Opening an ActiveX control in the Visual FoxPro Object Browser and selecting the top node displays the file name of the ActiveX control (in this case you can see the DynaZip ZIP ActiveX Control) in the lower pane.
Figure 5. FoxBox is indispensable when debugging support issues on a customers computer that does not have Visual FoxPro installed.
Figure 6. The Microsoft Word Envelopes and Labels wizard is a quick and simple way to create a CD-ROM label for your install CDs. On this dialog select the Avery Standard 5824 CD Label and click the New Document button to open up a document ready for you to create your label.
Figure 7. The Microsoft Word Envelopes and Labels wizard creates a Word table so you can create two labels per sheet which is standard from label providers.
Figure 8. Downloading files from the Internet via the Internet browser has become commonplace.
Figure 9. File transfer feature of pcAnywhere in action.
Figure 10. File transfer available in Terminal Services and Citrix (shown here) via the drives mapped to the local client computer in Windows Explorer.

Chapter 4: Setup Tool Roundup

Figure 1. ActiveDelivery has a wizard to make the initial script settings. This is the ActiveDelivery Script Editor used to make changes to the initial settings.
Figure 2. Ghost Installer combines a project wizard with an interactive user interface to set various properties for generating the installation package.
Figure 3. Inno Setup generates a script file using a wizard style interface. This script file can be edited directly to alter the way your applications are installed.
Figure 4. InstaFox is the only installer in the roundup completely written in Visual FoxPro.
Figure 5. The full version of InstallShield Express is more powerful and more flexible than the limited version that ships with Visual FoxPro 7 and 8.
Figure 6. Setup Factory has a comprehensive development environment and creates compact deployment packages.
Figure 7. Tarma Installer has a comprehensive development environment and creates compact deployment packages.
Figure 8. Wise for Windows Installer creates Windows Installer based deployment packages.
Figure 9. InstallShield Express Visual FoxPro Limited Edition (from VFP 7) installations require the removal of the previous installation before reinstalling.

Chapter 5: Windows Installer Inside and Out

Figure 1. This is the registry information from the installation of the demo application. The name and location of the cached MSI file are stored in the LocalPackage value.
Figure 2. In Windows Installer, a product consists of one or more features, as illustrated by Microsoft Office. Some of the features may have sub-features. Behind the scenes, each feature consists of one or more components .
Figure 3. The components of the DeployFox Demo App are organized into three features.
Figure 4. The directory structure of the CD-ROM build of the demo application shows how the product will be installed on the users computer.
Figure 5. The Summary Information of an MSI file can be viewed in Orca.
Figure 6. The Property table is a good place to start when exploring an MSI file.
Figure 7. The Feature table contains one row for each feature in the product.
Figure 8. Each component in the product has a row in the Component table.
Figure 9. The Feature-Components table relates each component to the feature(s) with which it is to be installed.
Figure 10. The Directory table determines where files are to be installed.
Figure 11. The AdminExecuteSequence table shows the steps taken during the core portion of the installation sequence.
Figure 12. The package code GUID is shown as the Revision Number on the property sheet of an MSI file.
Figure 13. An MSI database open in Orca with the Property table selected. The product code GUID and the upgrade code GUID are highlighted. This is the MSI file for the Windows Installer Clean Up utility mentioned later in this chapter.
Figure 14. The Product Version remains unchanged at 1.0.0 for a small update.
Figure 15. The Product Version changes from 1.0.0 to 1.1.0 for a minor upgrade to the sample application.
Figure 16. The Upgrade table is used by major upgrades to specify the minimum and maximum versions the upgrade applies to, as well as other information.
Figure 17. In InstallShield Express, you can mark a file as Permanent on the Advanced tab of the Properties dialog.
Figure 18. Command line parameters can be specified on the CmdLine entry in the Startup section of the STARTUP.INI file. This is the STARTUP.INI file for the small update for version 1.0.1 of the demo app.
Figure 19. The cached copies of MSI files are stored in the {Windows}\Installer folder.
Figure 20. The dreaded Another version of this product is already installed error message.
Figure 21. This wording of The feature you are trying to use is unavailable message is displayed when the source was a CD or other removable media.
Figure 22. This wording of The feature you are trying to use is unavailable message is displayed when the source was a local or network folder.
Figure 23. If Windows Installer cant find the installation source and you cant provide access to it, the result is this error message.

Chapter 6: Workstation and Traditional LAN Applications Step-By-Step

Figure 1. The Customer Information step of most Windows Installer based deployment packages provides the option to install the application for anyone who uses this computer, also known as the All Users option.
Figure 2. The option to show the All Users option in InstallShield Express is found under the Customer Information Dialog settings under Customize the Setup Appearance node.
Figure 3. The database container files must be deployed to the same relative folder structure as you have on your development machine.
Figure 4. The applications About form is one place to put details such as where the temporary files are directed.
Figure 5. The Inno setup process allows users to determine if they want a desktop icon included as part of the installation.
Figure 6. The Scheduler control from DBi Technologies provides a simple interface that would be difficult to create in a short time with native Visual FoxPro controls. It is also easy to deploy with your installations.
Figure 7. You want to include both VFP data merge modules (VFPODBC.MSM and VFPOLEDB.MSM). This example shows the Wise for Windows Installer selection dialog.
Figure 8. Setting up an ODBC DSN using a Windows Installer deployment tool is as easy as checking one of the existing DSNs from the source machine and setting properties.
Figure 9. You can add ad hoc reporting to your applications if you follow some basic steps and include the proper menu options for your users.
Figure 10. Step 1Specify Engine Access Methods.
Figure 11. Step 2Export Formats.
Figure 12. Step 3Export Destinations .
Figure 13. Step 4Database Connections.
Figure 14. Step 5Additional Components.
Figure 15. Step 6Summary.
Figure 16. The results from making selections in the Crystal Reports 8.5 Object Wizard is a number of Crystal Report merge modules being selected within InstallShield Express. The Crystal Report Object Wizard item is highlighted in the list on the right.
Figure 17. The settings we typically make for the General Information section.
Figure 18. After creating features, you determine which features install for a specific setup type. You can assign features to more than one setup type and alter the description for each of the setup types.
Figure 19. Assigning files is accomplished by selecting the feature, and then dragging files from the source computer to the destination computer folders.
Figure 20. Setting file properties is important if you want to control the operating system the file is installed on, or make sure files are not overwritten, never deleted, or deleted only when it is the last application uninstalled .
Figure 21. Creating shortcuts is important to provide users with access to the application.
Figure 22. If you do not want the end user to specify where the data is located and it is under the INSTALLDIR, alter the DATABASEDIR property in the General Information and skip the Database Folder dialog.
Figure 23. You can change the graphic displayed at the top of the installation wizard by changing the Banner Bitmap property.
Figure 24. The custom banner for dialogs that display the banner across the top need to be dimensioned 499 pixels wide by 58 pixels high.
Figure 25. The custom banner for dialogs that display the banner on the left side need to be dimensioned 499 pixels wide by 312 pixels high.
Figure 26. Each of the media options has properties you can select that determine how the final build is generated and what Windows Installer engine files are included.
Figure 27. The goal of each build is to get zero errors and warnings. This build has problems so you have to review the output to see exactly what the problems are and fix them.
Figure 28. Testing the build allows you to review the selected dialogs to validate the images and text changes you included in the package.

Chapter 7: Client/Server Applications Step-By-Step

Figure 1. The database restore process in SQL Server provides numerous options. The key to installing a new database is the restoration of the complete database.
Figure 2. The Options page of the Restore database dialog has the critical setting Force restore over existing database if you need to overwrite a beta database.
Figure 3. The SQL Server Generate SQL Scripts dialog allows you to generate one script with all the Transact-SQL code necessary to regenerate an empty database.
Figure 4. The SQL Server Generate SQL Scripts dialog displays a progress bar when you start the scripting process.
Figure 5. Step 1 Choose a Data Source.
Figure 6. Step 2 Choose a destination.
Figure 7. Step 3 Specify Table Copy or Query.
Figure 8. Step 4 Select Objects to Copy.
Figure 9. Step 5 Save, schedule, and replicate package.
Figure 10. SQL Server Enterprise Manager can see database servers on the workstation (local), the local area network (RASSolo9300 and PSgp6450001), and those connected through the Internet and a VPN (Alpha).
Figure 11. Use the SQL Query Analyzer to run scripts and execute queries on a remote database, both network connected and those accessed over the Internet.
Figure 12. Microsoft Access XP and 2003 have basic tools to administer a MSDE database server.
Figure 13. MSDE Admin allows administrators basic access to an MSDE installation.
Figure 14. MSDE Manager offers most of the functionality found in the SQL Server Enterprise Manager.
Figure 15. MSDE Manager has a TSQL window utility that looks and acts just like the SQL Query Analyzer.
Figure 15: Setting permissions for an application role is very similar to setting permissions for other objects in a SQL Server database.
Figure 16. One way to install the MDAC components is to select the available merge modules, and then select the features you want it installed for.
Figure 17. Another way to install the MDAC components is to install the raw installation setup executables and have a user or support individual manually run the install.
Figure 18. You need to install the SQL-DMO files if your application performs any ActiveX automation control over SQL Server. The figure displays the Files and Features view inside InstallShield Express.
Figure 19. Adding a DSN to the deployment is easy if you have a DSN to model the DSN you want created on the target computer. First, select the existing DSN in the ODBC Resource pane, determine which feature you want the DSN installed, and then configure the Database and Server properties in the Properties pane if they differ from your system configuration.

Chapter 8: Release and Post-Release Tips

Figure 1. This is a sample checklist for installing an application in production.
Figure 2. This is an example of a database conversion routine running.
Figure 3. This is an example of documenting release history for an application.
Figure 4. You can use a software applet like ClockRack (free to subscribers of PC Magazines online Utility Library) to show what time it is in different time zones where you have customers running your applications.
Figure 5. A Frequently Asked Question list provides the users with a common list of questions other users have asked technical support to address.
Figure 6. The Wise Solutions support site is one of the better product download sites we have used. The Web site first has a customer login, and then displays the full versions of the products you registered and any update versions you can download.
Figure 7. BugCentral.com is one example of a Web-based bug tracking application.
Figure 8. Some bug tracking packages like Microsofts older Anomaly Tracking System have just a desktop component.
Figure 9. Several bug tracking packages like IssueView have both a desktop and Internet component.

Chapter 9: Support and Ch-Ch-Changes

Figure 1. This is Recover from Abri Technologies, the most recommended product to repair corrupted tables.
Figure 2. The configuration options available from Recover are extensive and allow you to repair various types of corruption.
Figure 3. SQL Compare evaluates the difference between two databases and visually represents if the objects match or if they are different. After you select the objects to script, SQL Compare generates the change script.
Figure 4. SQL Compare generates script to update each of the databases. You can save this script to a file and include the file as part of the deployment package.
Figure 5. xCase database synchronizer shows the differences between the data model and the database, and synchronizes the changes directly or creates a script to run at a later time.
Figure 6. SQL Servers Query Analyzer allows the database administrator to run scripts to update the production database with changes from development.
Figure 7. MSDE Query allows database administrators, developers, and sophisticated end users to run scripts on MSDE, which does not have tools built in like the full license of SQL Server.
Figure 8. FoxBox is a very versatile tool for supporting customers who do not have Visual FoxPro loaded on their computer.
Figure 9. The Fox6Command runtime command window looks and feels just like Visual FoxPro 6.0.
Figure 10. You use the original settings of the Product Version and the Product Code if your changes are a small update.
Figure 11. You change the Product Version and leave the Product Code if your changes are a minor upgrade.
Figure 12. You change both the Product Version and the Product Code if your changes are a major upgrade.
Figure 13. Each Upgrade Path represents a previous version potentially installed on the target computer. This install package example can remove two previous versions before installing the major upgrade.
Figure 14. The Add/Remove Programs support link allows you to include an uninstall readme file. Use this to relay important details to users who uninstall your application.

Chapter 10: Security

Figure 1. The project file used to test decompilation has at least one file of each type of source code file used by Visual FoxPro.
Figure 2. The ReFox user interface immediately exposes the main program, even with an encrypted executable.
Figure 3. The differences in a simple program when compared side-by-side are obvious. The original program is on the left side, the decompiled version on the right.
Figure 4. yRecover is a free developer tool that extracts the forms, classes, and reports from a Visual FoxPro executable.
Figure 5. yRecover does not extract files from encrypted executables.
Figure 6. The decompiler parses apart any CHM file into the original files and stores them in a specified folder.
Figure 7. KeyTools does a better job at decompiling a HTML Help file than HTML Help Workshop, plus it has a number of other features that assist HTML Help authors.

Chapter 12: Legalese

Figure 1. Sample installation package indicating this program is protected by copyright law.
Figure 2. Sample Splash Screen with Licensing Information.
Figure 3. Sample About Screen
Figure 4. Sample of a Fatal Error Message for a Bug
Figure 6. Sample of an End User License Agreement (EULA) for a vertical market product

Appendix A: How To: InstallShield Express

Figure 1. InstallShield ExpressVisual FoxPro Limited Edition is installed from the VFP CD, but as a separate step from installing VFP itself.
Figure 2. You are prompted to overwrite ISX VFP7 LE when you install ISX VFP8 LE.
Figure 3. ISX VFP8 LE offers to convert your older projects from ISX VFP7 LE.
Figure 4. To create a new InstallShield Express project for your VFP application, choose the Project Wizard or choose a Blank Setup Project. This screenshot was captured from InstallShield Express 4.0, which provides for other project types not found in ISX VFP LE.
Figure 5. The first step in the Project Wizard is to give your project a name.
Figure 6. The Project Wizard automatically supplies the [ProgramFilesFolder] property as the first part of the default destination folder for your product.
Figure 7. InstallShield Express supplies the Always Install feature by default, but you can add additional features if your applications architecture calls for them. You should specify a Destination Folder for each feature.
Figure 8. The files DEMOAPP.EXE and README.TXT are installed as part of the Always Install feature.
Figure 9. When you select the target for a shortcut, you are pointing to the location of that file on the destination computer, not on your own computer.
Figure 10. This step of the Project Wizard defines a Desktop shortcut and points to the EXE file (DEMOAPP.EXE) for the application on the destination computer.
Figure 11. The final step in the Project Wizard summarizes the basic information for the setup. If changes are necessary after this step, they can be made directly to the project file via the InstallShield Express IDE.
Figure 12. The project file is opened for editing when the Project Wizard finishes. The Organize Your Setup interface is the same interface you use when you open an existing project manually, or when you create a Blank Setup Project.
Figure 13. The Product Name, Product Version, default values for INSTALLDIR and DATABASEDIR, among other things, are specified in the General Information view.
Figure 14. The Setup Types view is used to link the products features to the setup type(s) with which they are to be installed.
Figure 15. In the Files view, first select a feature from the drop-down list at the top. Next, select the source files from the upper panes and drag them to the appropriate folder in the lower panes.
Figure 16. Files can be marked as Never Overwrite and/or Permanent on the Properties sheet available from the Files view. Properties can be set for multiple files at the same time.
Figure 17. You can add new destination computer folders to your setup using the Files view.
Figure 18. Merge modules are added to the project in the Redistributables view. Use the upper right pane to associate each selected merge module with the desired feature.
Figure 19. InstallShield Express 4.0 can show you whats inside a merge module. This is very useful for confirming a particular merge module includes the file(s) you want to install. The VFP8 Runtime Libraries merge module installs three files.
Figure 20. The value for a shortcuts Working Directory can be selected from a drop- down list in the Shortcuts/Folders view.
Figure 21. You can use the Registry view to create registry entries on the users computer. The entry shown here stores the path to the folder where the product is being installed by capturing the runtime value of the [INSTALLDIR] property.
Figure 22. Add a DSN to your project by selecting it from the tree in the ODBC Resources view.
Figure 23. Add the Visual FoxPro ODBC merge module to your project using the Redistributables view. Note that the contents of this merge module are shown in the lower left pane in ISX 4.0.
Figure 24. When building your release, you can choose the type of setup package you want. You can also decide whether to include the Windows Installer setup engine(s).
Figure 25. The Distribute Your Release view makes it easy to copy your setup file(s) to the desired distribution media.
Figure 26. The files created when you build a release are placed in a sub-folder beneath the folder where the setup project itself is located. The root of the sub-folder structure for a particular build is the folder whose name is the same as the build type.
Figure 27. The QuickPatch Project Wizard prompts you for a project name and for the location of the original setup package.
Figure 28. The QuickPatch Project Wizard performs an administrative install of the original setup package and writes the files to the BASEIMAGE folder.
Figure 29. The QuickPatch IDE has three steps. In the General Information step, the Product Properties view identifies the path to the original setup package on which the patch is based.
Figure 30. The Files view is where you specify the files to be patched.
Figure 31. After the patch is built, the projects folder tree contains sub-folders for the updated image files, the patch creation file and a log file, and the patch package itself.

Appendix B: How To: Wise for Windows Installer

Figure 1. Use the predefined Windows Application template when creating a new setup project file for your VFP application.
Figure 2. The Installation Expert view is your primary interface to the setup project.
Figure 3. Use the General Information page to specify the setups properties as seen by Windows Explorer.
Figure 4. Use the Features page to define the features in your product. A new project file has one predefined feature named Complete.
Figure 5. Use the Feature Details dialog to specify the name and other information about each feature.
Figure 6. The completed feature tree shows all three features for the demo app. The appearance of this tree in WfWI is very similar to what the user sees during a custom installation.
Figure 7. Use the Merge Modules tab of the Preferences dialog to tell WfWI about other directories containing merge modules, such as those for VFP 8.
Figure 8. Add a merge module to the project by selecting its check box in the list. Additional information about the selected merge module is presented in the lower portion of this dialog.
Figure 9. The Main Program feature installs the Visual FoxPro 8 Runtime Libraries merge module and its dependencies. It also installs the MSCOMCTL merge module, which in turn requires the COMCAT and OLEAUT32 merge modules.
Figure 10. On the Files page, first select the desired feature from the drop-down list at the top. Next, add directories and files for that feature as required.
Figure 11. The folders defined on the Files page appear in the drop-down list when you click the Change button to set the default directory on the Product Details page.
Figure 12. To protect data files from being overwritten or uninstalled, mark the component containing them as Never overwrite if key path exists and Leave installed on uninstall.
Figure 13. Use the Registry page to define registry keys and values to create on the destination computer during installation of your product.
Figure 14. Add registry keys manually with the Registry Details dialog.
Figure 15. Registry keys to add at installation time appear in the destination computer portion of the Registry page.
Figure 16. To create a shortcut to a file, choose File in this installation in the first step of the shortcut wizard.
Figure 17. Select the shortcuts target file from the list of files associated with the selected feature.
Figure 18. To place a shortcut on the users desktop, choose Desktop under Windows\Profiles in step three of the shortcut wizard.
Figure 19. The Shortcut Details page provides access to the shortcuts properties.
Figure 20. You can easily import a DSN by selecting it from the list of data sources registered on your machine.
Figure 21. The ODBC Data Source Details dialog shows the information from the DeployFoxSample DSN we imported.
Figure 22. Each project must define at least one release. A new project automatically contains a release named Default, which you can modify to suit your needs.
Figure 23. Use the Release Details dialog to specify the release name, MSI file name, and description for each release.
Figure 24. The Release Setting page lets you specify which features to install with each release.
Figure 25. Use the Build Options page to determine the type of build (.EXE Options) and whether to install Windows Installer on Windows 9x/NT machines (Pre-install Options).
Figure 26. Use the Media Details dialog to provide the Media Name and to specify the destination directory for the media output file(s).
Figure 27. Click the Compile button to build the release package.
Figure 28. The Package Distribution tool helps you deploy your setup package.
Figure 29. The final step is to specify the destination disk where your setup package is to be copied .
Figure 30. To create an upgrade, update the Version number and generate a new Product Code GUID.
Figure 31. Wise for Windows Installer fills in the Upgrade Details page with information it reads from the original MSI file.
Figure 32. Creating a patch requires you to specify the MSI file for the original version of the product.
Figure 33. Creating a patch also requires you to specify the MSI file for the updated version of the product.
Figure 34. You can specify the name for the patch (MSP) file as well as choose other settings to determine how the patch file is compiled.

Appendix C: How To: InstaFox

Figure 1. Our new sample installation folder E:\DemoInstall with the contents of D:\InstaFox\InstaFox copied into it (including subfolders ).
Figure 2. The InstaFox Tool folder D:\InstaFox\InstaFox.
Figure 3. The APPDIR folder structure.
Figure 4. Step 1 of InstaFox Wizard prompts you for the basic information about your application.
Figure 5. Step 2 of the InstaFox wizard asks for the optional files.
Figure 6. Step 3 of the InstaFox wizard asks for the base registry information.
Figure 7. Step 4 of the InstaFox wizard asks for additional registry entries.
Figure 8. Step 5 of the InstaFox Wizard Contact Information.
Figure 9. Step 6 of the InstaFox Wizard Tables to Update.
Figure 10. Step 7 of the InstaFox Wizard Files to Remove.
Figure 11. Step 8 of the InstaFox Wizard Files to Install. Results immediately after clicking Load Files.
Figure 12. Step 8 of the InstaFox Wizard Files to Install. Results after removing the WIZDIR folder files.
Figure 13. Sample of WZ_INS.DBF
Figure 14. InstaFox Installer missing runtime file component error message.
Figure 15. The Welcome page identifies the application to be installed.
Figure 16. If a license agreement is included, the user cannot install the application without accepting it.
Figure 17. The user can select the destination directory for the application.
Figure 18. InstaFox Installer application shortcuts selection form.
Figure 19. InstaFox Installer Selected Installation Options form.
Figure 20. InstaFox Installer Cancelled Installation form.

Appendix D: How To: Inno Setup

Figure 1. The script wizard makes it easy to create a new setup script.
Figure 2. Step 2 of script wizard prompts you for the basic information about your application.
Figure 3. Step 3 of the script wizard asks for the default installation directory.
Figure 4. The script wizard allows you to easily specify the main executable file and any other files to be installed.
Figure 5. The CUSTOMERS.DBF table will be installed to a sub-directory named Data under the directory where the application itself is installed.
Figure 6. Inno Setup lets you give the end user a choice about which Start Menu items and other icons are created at installation time.
Figure 7. If a license file is specified in step 6 of the script wizard, the end user will have to accept the terms of the license at installation time before setup proceeds.
Figure 8. When the script wizard finishes, the generated script automatically opens in the Inno Setup edit window.
Figure 9. This dialog can be turned off by adding DisableStartupPrompt=Yes to the Setup section of the script.
Figure 10. The Welcome page identifies the application being installed. The image shown is the bitmap specified as the WizardImageFile in Listing 3.
Figure 11. If a license agreement is included, the user cannot install the application without accepting it.
Figure 12. Use the InfoBeforeFile to tell the user anything you want them to know before installing the application.
Figure 13. The user can select the destination directory for the application.
Figure 14. Shortcuts are created in the Start Menu folder specified on this page of the Setup Wizard.
Figure 15. The user can choose whether or not to create a desktop icon.
Figure 16. The Ready To Install page displays the choices made in the preceding steps and gives the user the chance to confirm them before actually installing the application.
Figure 17. Use the InfoAfterFile to tell the user anything else you want them know after installation but before the setup wizard terminates.
Figure 18. The last page can be configured to allow the user to view the ReadMe file and/or to automatically launch the application when setup is finished.



Deploying Visual FoxPro Solutions
Deploying Visual FoxPro Solutions
ISBN: 1930919328
EAN: 2147483647
Year: 2004
Pages: 232

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net