SetupWizard Help

SetupWizard Overview

How to Use the SetupWizard

SetupWizard Commands


SetupWizard Overview

See Also

Use the Visual Basic SetupWizard to create application setup and distribution media. You can use SetupWizard as is or you can modify it to customize your application's setup program.  The SetupWizard is a tool used with the Visual Basic Setup Toolkit.  The SetupWizard takes you through several steps to let you create a setup program and distribution media for your Visual Basic application.

The first time you run the SetupWizard, you are prompted for the location of several important files that are required for your application to run correctly.  This information is then kept in the SWDEPEND.INI file in your \Windows directory.

Based on the information you provide to the SetupWizard, it creates a standard SETUP.LST file.

The SetupWizard supports multiple disks and can split large files to fit on your distribution media.  Or, the SetupWizard can copy your files to a hard disk directory for distribution over a network or on CD-ROM.

Note   The SetupWizard is designed for Visual Basic developers and isn't a general Windows Setup Tool.  For those situations, use the GUI Setup Toolkit provided in the Windows SDK.

The SetupWizard is designed to handle most setup scenarios that a Visual Basic developer might encounter; however, some scenarios may require you to create a custom SETUP1.EXE file.

The SetupWizard is not a disk duplication tool.  Use the MS-DOS DiskCopy command, or from the Disk Menu in File Manager, choose the Copy Disk command to make copies of your master distribution disks.


See Also

How to Use the SetupWizard

SetupWizard Commands


How to Use the SetupWizard

See Also

Follow these steps when you are ready to create the master distribution media for your Visual Basic application.

First, double-click the SetupWizard icon in the Visual Basic program group.  Then follow these  steps:

Step 1.  The SetupWizard collects initial information

Step 2.  The SetupWizard collects data access driver information

Step 3.  The SetupWizard collects distribution media information

Step 4.  The SetupWizard lets you add OLE Automation files

Step 5.  The SetupWizard lets you remove dependency files

Step 6.  The SetupWizard lets you select the deployment mode for your application

Step 7.  The SetupWizard displays the files to be distributed and builds distribution media

Step 8.  The SetupWizard has finished creating the distribution media


See Also

SetupWizard Commands

SetupWizard Overview


Step 1.  The SetupWizard collects initial information

See Also

Enter the path and filename for the Visual Basic project (.VBP) file of the application that you want to distribute.  To browse the files on your disk, choose the Browse button to the right of the Project File field.

Choose the Next button to continue.

Specify the project file you want to distribute.

If an executable file (.EXE) or (32-bit Professional and Enterprise Editions only) in-process server dynamic-link library (.DLL) doesn't exist for the specified application, the SetupWizard automatically builds the application's .EXE or .DLL file.  To force a rebuild of the application's .EXE or .DLL file, select the Rebuild the Project's .EXE File check box.

Choose Open Template if you would like to use a pre-existing SetupWizard distribution template.  After running the SetupWizard, you can save all the settings to a SetupWizard template.


See Also

Step 2.  The SetupWizard collects data access driver information

Step 3.  The SetupWizard collects distribution media information

Step 4.  The SetupWizard lets you add OLE Automation files

Step 5.  The SetupWizard lets you remove dependency files

Step 6.  The SetupWizard lets you select the deployment mode for your application

Step 7.  The SetupWizard displays the files to be distributed and builds distribution media

Step 8.  The SetupWizard has finished creating the distribution media


Step 2.  The SetupWizard collects data access information

See Also

If your application uses the Data control or any of the data access objects, select the database drivers to include them in the distribution files.  For example, if your application uses Microsoft FoxPro data files, then select that option from the list.  You can make multiple selections from this list.

Choose the Next button to continue.

Choose the Back button to return to Step 1.

Note   Step 2 is skipped if your application doesn't use the Data control or any data access objects.


See Also

Step 1.  The SetupWizard collects initial information

Step 3.  The SetupWizard collects distribution media information

Step 4.  The SetupWizard lets you add OLE Automation files

Step 5.  The SetupWizard lets you remove dependency files

Step 6.  The SetupWizard lets you select the deployment mode for your application

Step 7.  The SetupWizard displays the files to be distributed and builds distribution media

Step 8.  The SetupWizard has finished creating the distribution media


Step 3.  The SetupWizard collects distribution media information

See Also

If you want to distribute the application on disks, select the Disk Drive option button, and then select the disk drive on which you want to create your master disks, and select the type of disks you want to use.

If you want to distribute over a network or on CD-ROM, select the Directory Path option button, and then select a destination drive and directory into which you will copy the distribution files.  To distribute over a network or on CD-ROM, you can copy the distribution files from the directory path to the network directory or CD-ROM generation system.

Choose the Next button to continue.

Choose the Back button to return to Step 2

Note   The Back button will return to Step 1 if you are not using the Data control or any data access objects.


See Also

Step 1.  The SetupWizard collects initial information

Step 2.  The SetupWizard collects data access driver information

Step 4.  The SetupWizard lets you add OLE Automation files

Step 5.  The SetupWizard lets you remove dependency files

Step 6.  The SetupWizard lets you select the deployment mode for your application

Step 7.  The SetupWizard displays the files to be distributed and builds distribution media

Step 8.  The SetupWizard has finished creating the distribution media


Step 4  The SetupWizard lets you add OLE Automation files
Step 4.  The SetupWizard lets you add OLE Automation files

See Also

The SetupWizard searches your project file (.VBP) to find any references to OLE Automation components used in your application, and then displays these files in the Step 4 dialog box.  You can also add files by clicking the Add OLE Servers button and browsing for an OLE component.  You may also need to add or remove files in this list by selecting or clearing the check box next to each filename.

(Enterprise Edition only)  If you select a remote OLE Automation server registration file (.VBR), the Remote Server Details dialog box will appear, prompting you for the proper information.

You may want to remove files that you know will already exist on the user's machine. You must also remove any files for which you do not have distribution rights.  List in your release notes the files you remove from this screen so that users can be sure they have all necessary files.

Choose the Next button to continue.

Choose the Back button to return to Step 3.

'


See Also

Step 1.  The SetupWizard collects initial information

Step 2.  The SetupWizard collects data access driver information

Step 3.  The SetupWizard collects distribution media information

Step 5.  The SetupWizard lets you remove dependency files

Step 6.  The SetupWizard lets you select the deployment mode for your application

Step 7.  The SetupWizard displays the files to be distributed and builds distribution media

Step 8.  The SetupWizard has finished creating the distribution media

Remote OLE Server Details dialog


Step 5  The SetupWizard lets you remove dependency files
Step 5.  The SetupWizard lets you remove dependency files

See Also

The SetupWizard determines that certain files, which are displayed in this list, are required for your application to function properly.  The Dependency Of field shows you which file(s) depend on the presence of any file you select in the list box.

You may want to remove files that you know will already exist on the user's machine. You must also remove any files for which you do not have distribution rights.  List the files you remove from this screen in your release notes so that users can be sure they have all the required files already installed.

Note   If you plan to distribute your application without using the SetupWizard and Setup Toolkit provided with Visual Basic, be sure that the controls and references (and their dependent files) used in your application are installed on the user's machine and registered in the system registry.  You can register files as part of your setup script, or you can ask users to do this manually.  The file dependencies and references included with Visual Basic are listed in the SWDEPEND.INI file located in the \WINDOWS directory.  The SWDEPEND.TXT file describes these dependencies in more detail.

Choose the Next button to continue.

Choose the Back button to return to Step 4.


See Also

Step 1.  The SetupWizard collects initial information

Step 2.  The SetupWizard collects data access driver information

Step 3.  The SetupWizard collects distribution media information

Step 4.  The SetupWizard lets you add OLE Automation files

Step 6.  The SetupWizard lets you select the deployment mode for your application

Step 7.  The SetupWizard displays the files to be distributed and builds distribution media

Step 8.  The SetupWizard has finished creating the distribution media


Step 6  The SetupWizard lets you select the deployment mode for your application
Step 6.  The SetupWizard lets you select the deployment mode for your application

See Also

Here the SetupWizard determines the deployment mode for your application setup, whether you plan to distribute your application as a separate application or as a shared OLE component.

If you select the first option, the OLE component will be installed as a stand-alone file into the application directory specified.

If you select the second option, the OLE component will be installed as a shared OLE component into the shared components directory (\OLESVR).

If you check the OLE Automation Provider check box, then the Automation Manager support files (AUTMGR32.EXE, AUTPRX32.DLL and RACMGR32.EXE plus its dependency files) will be added to the file list.  Since remote OLE Automation servers can only be installed on 32-bit operating systems, the last check box will only appear in the 32-bit Enterprise Edition.

As in Step 5, you should remove any files that you know will already be on the user's machine or for which you don't have distribution rights.  For information on which remote automation setup files can be distributed and under which conditions, please see "Implementing OLE Servers," in Chapter 7 of the Enterprise Edition book Building Client/Server Applications with Visual Basic.  List the files you remove from this screen in your release notes so that your users can be sure they have all the files that you expect them to have.


See Also

Step 1.  The SetupWizard collects initial information

Step 2.  The SetupWizard collects data access driver information

Step 3.  The SetupWizard collects distribution media information

Step 4.  The SetupWizard lets you add OLE Automation files

Step 5.  The SetupWizard lets you remove dependency files

Step 7.  The SetupWizard displays the files to be distributed and builds distribution media

Step 8.  The SetupWizard has finished creating the distribution media


Step 7  The SetupWizard allows file removal before building the distribution media
Step 7.  The SetupWizard allows file removal before building the distribution media

See Also

The SetupWizard determines that certain files, which are displayed in the list box, are required for your application to function properly.  The Dependency Of frame shows you which file(s) depend on the presence of any file you select in the list box.

As in Steps 4 and 5, you should remove any files that you know will already be on the user's machine, and remove files for which you do not have distribution rights.  List in your release notes the files that you remove from this dependencies list so that your users can be sure they have all necessary files.

You can add a file to the distribution list, even if it is not required by the application, by choosing the Add Files button.  You cannot have duplicate filenames in this list.  If you try to add a duplicate file, a message box will prompt you to change that file's name.

If you try to remove one of the files required by every Visual Basic application, when you choose the Next button, a message box will ask you to confirm that you want to remove the required file(s).  If you choose No, the Step 7 dialog box will be redisplayed so that you can reconsider your choices.

Choose the Summary Info button to see the storage size and number of files that have been selected.

Choose the File Details button to see the file size, file date, version information, current location, and the install destination information for the selected file.  You can now change the Installed Location for the selected file..  However, changing the installed location of a shared file or remote OLE Automation server may adversely affect its functionality.

You may now save your work to a template file (.VBZ) by clicking the Save Template button.  You can return to the template later using the Open Template button when you next start the SetupWizard.

To continue, choose the Finish button.


See Also

Step 1.  The SetupWizard collects initial information

Step 2.  The SetupWizard collects data access driver information

Step 3.  The SetupWizard collects distribution media information

Step 4.  The SetupWizard lets you add OLE Automation files

Step 5.  The SetupWizard lets you remove dependency files

Step 6.  The SetupWizard lets you select the deployment mode for your application

Step 8.  The SetupWizard has finished creating the distribution media


Finished  The SetupWizard finishes creating the distribution media
Finish.  The SetupWizard finishes creating the distribution media

See Also

The SetupWizard now begins compressing your distribution files, listing them as they are compressed.  Once the file compression is complete, SetupWizard will copy the files to their destination directory.

If you chose to build the installation disks to a directory path, the SetupWizard asks whether you want to delete any existing files in the destination directory before it creates the compressed files.

The SetupWizard creates the SETUP.LST file.

If, in Step 3, you selected a disk drive as the target of the setup files, the SetupWizard creates disks:

The SetupWizard notifies you of the number of blank, formatted disks needed.

The SetupWizard prompts you to insert each blank, formatted disk.

If you selected a directory path (for later distribution over a network or on CD-ROM) as the destination for the setup files, the SetupWizard copies the distribution files to the distribution directory.

The SetupWizard notifies you when it has finished creating the distribution media.

To save the SetupWizard settings to a template, choose Save Template.

If you are distributing on disks and need to create additional sets of disks, start the SetupWizard again, open the saved SetupWizard template, and then choose Finish again.  The SetupWizard creates a new set of disks from the compressed distribution files.

Choose Exit to close the SetupWizard.


See Also

Step 1.  The SetupWizard collects initial information

Step 2.  The SetupWizard collects data access driver information

Step 3.  The SetupWizard collects distribution media information

Step 4.  The SetupWizard lets you add OLE Automation files

Step 5.  The SetupWizard lets you remove dependency files

Step 6.  The SetupWizard lets you select the deployment mode for your application

Step 7.  The SetupWizard displays the files to be distributed and builds distribution media


SetupWizard Commands

See Also

You can use the following commands in the SetupWizard.

Help Button

Add Files Button

Add OLE Servers Button

Back Button

Exit Button

File Details Button

Finish Button

Next Button

Open Template Button

Rebuild the Project's EXE File Check Box

Save Template Button

Select VBP File Button

Summary Info Button


See Also

SetupWizard Overview

How to Use the SetupWizard


Select VBP File Button
Browse for Project .VBP File Button

See Also

The SetupWizard works from your Visual Basic application's project file, also known as a .VBP file.  The Browse for Project .VBP File button appears as a gray button with ellipses (three dots) on it, to the right of the Project File text box.

When you choose this command button in the Step 1 dialog box, you are prompted for the location of the .VBP file for the Visual Basic application that you want to distribute.  The SetupWizard reads the .VBP file for information on which objects, references, resources, dynamic-link libraries, and so forth need to be included in the distribution files, as well as the location of your .EXE or .DLL file.


See Also

Add Files Button

Add OLE Servers Button

Back Button

Exit Button

File Details Button

Finish Button

Help Button

Next Button

Open Template Button

Rebuild the Project's EXE File Check Box

Remote OLE Server Details Button

Save Template Button

SetupWizard Commands

Summary Info Button


Rebuild the Project's EXE File Check Box
Rebuild the Project's .EXE File Check Box

See Also

In the Step 1 dialog box, you can select this check box to force a rebuild of your application's executable (.EXE) or in-process OLE .DLL (32-bit Professional and Enterprise Editions only) file.


See Also

Add Files Button

Add OLE Servers Button

Back Button

Exit Button

File Details Button

Finish Button

Help Button

Next Button

Open Template Button

Remote OLE Server Details Button

Save Template Button

Select VBP File Button

SetupWizard Commands

Summary Info Button


Exit Button

See Also

You can choose the Exit button from any step to stop and exit from the SetupWizard.


See Also

Add Files Button

Add OLE Servers Button

Back Button

File Details Button

Finish Button

Help Button

Next Button

Open Template Button

Rebuild the Project's EXE File Check Box

Remote OLE Server Details Button

Save Template Button

Select VBP File Button

SetupWizard Commands

Summary Info Button


Summary Info Button

See Also

From Step 7, you can choose the Summary Info button to see the storage size and number of files that have been selected.


See Also

Add Files Button

Add OLE Servers Button

Back Button

Exit Button

File Details Button

Finish Button

Help Button

Next Button

Open Template Button

Rebuild the Project's EXE File Check Box

Remote OLE Server Details Button

Save Template Button

Select VBP File Button

SetupWizard Commands


Add Files Button

See Also

From Step 7, you can choose the Add Files button to add file(s) to the file list box.  You can make multiple selections from the Add Files dialog box.

You cannot have duplicate filenames in this list box.  If you try to add a duplicate file, a message box prompts you to change that file's name.


See Also

Add OLE Servers Button

Back Button

Exit Button

File Details Button

Finish Button

Help Button

Next Button

Open Template Button

Rebuild the Project's EXE File Check Box

Remote OLE Server Details Button

Save Template Button

Select VBP File Button

SetupWizard Commands

Summary Info Button


Help Button

See Also

The Help button is available from any step in the SetupWizard and from any of the dialog boxes.  Choosing the Help button displays online Help for the current step or task.


See Also

Add Files Button

Add OLE Servers Button

Back Button

Exit Button

File Details Button

Finish Button

Next Button

Open Template Button

Rebuild the Project's EXE File Check Box

Remote OLE Server Details Button

Save Template Button

Select VBP File Button

SetupWizard Commands

Summary Info Button


Back Button

See Also

The Back button is available from any step in the SetupWizard except Step 1 and the Finish screen.  Choosing the Back button from any other step takes you to the previous step.


See Also

Add Files Button

Add OLE Servers Button

Exit Button

File Details Button

Finish Button

Help Button

Next Button

Open Template Button

Rebuild the Project's EXE File Check Box

Remote OLE Server Details Button

Save Template Button

Select VBP File Button

SetupWizard Commands

Summary Info Button


Next Button

See Also

The Next button is available from any step in the SetupWizard except Step 7.  Choosing the Next button takes you to the next step in the SetupWizard.  In Step 1, this button isn't available until a valid, existing project name is entered.


See Also

Add Files Button

Add OLE Servers Button

Back Button

Exit Button

File Details Button

Finish Button

Help Button

Open Template Button

Rebuild the Project's EXE File Check Box

Remote OLE Server Details Button

Save Template Button

Select VBP File Button

SetupWizard Commands

Summary Info Button


Finish Button

See Also

The Finish button is available in the SetupWizard in Step 7 once all of the required information has been entered.  When you choose the Finish button, the SetupWizard attempts to complete the setup process with the given information.


See Also

Add Files Button

Add OLE Servers Button

Back Button

Exit Button

File Details Button

Help Button

Next Button

Open Template Button

Rebuild the Project's EXE File Check Box

Remote OLE Server Details Button

Save Template Button

Select VBP File Button

SetupWizard Commands

Summary Info Button


File Details Button

See Also

From Steps 4 or 5, you can choose the File Details button to display file size, file date and time, and current and destination location for a file you select in the file list boxes.  Version information is also displayed if available.  If you select more than one file, only the information for the first file is displayed.

When you choose the File Details button in 16-bit versions of Visual Basic, no information about 32-bit files is displayed.

From Step 7, you can use the File Details dialog box to change the installation destination of the selected file.  Select the desired file, choose the File Details button and change the Destination Directory information in the text box.  You may also select or deselect the Install as a Shared File check box if you want to change this file's private or shared status.

Caution   Changing either the private/shared file status or the Destination Directory of a shared file or remote OLE Automation server may adversely affect that component's capabilities and impair the removal of that component later.  For example, if two OLE Automation components with the same name are installed to different directories, the removal of one of them may result in removal of the registry information that makes each of them accessible, rendering the remaining component inaccessible.


See Also

Add Files Button

Add OLE Servers Button

Back Button

Exit Button

Finish Button

Help Button

Next Button

Open Template Button

Rebuild the Project's EXE File Check Box

Remote OLE Server Details Button

Save Template Button

Select VBP File Button

SetupWizard Commands

Summary Info Button


Save Template Button

See Also

The Save Template button is available from Step 7 of the SetupWizard.  The SetupWizard template is a handy way to save information for often-used disk images.  When you are satisfied with the distribution files listed, you can save the information in a template file (.VBZ).  You can then open this template file to rebuild the same disk images.


See Also

Add Files Button

Add OLE Servers Button

Back Button

Exit Button

File Details Button

Finish Button

Help Button

Next Button

Open Template Button

Rebuild the Project's EXE File Check Box

Remote OLE Server Details Button

Select VBP File Button

SetupWizard Commands

Summary Info Button


Open Template Button

See Also

The Open Template button is available from Step 1 of the SetupWizard.  The SetupWizard template is a handy way to save information for often-used disk images.  When you are satisfied with the distribution files listed, you can save the information in a template file (.VBZ), using the Save Template button.  You can then open this template file to rebuild the same disk images.


See Also

Add Files Button

Add OLE Servers Button

Back Button

Exit Button

File Details Button

Finish Button

Help Button

Next Button

Rebuild the Project's EXE File Check Box

Remote OLE Server Details Button

Save Template Button

Select VBP File Button

SetupWizard Commands

Summary Info Button


Remote OLE Server Details Dialog

See Also

This dialog is reached by choosing the Remote OLE Server Details button at Step 5 of the SetupWizard.  Enter the network address, network protocol and any required authentication information for the registry to be correctly modified in order for the OLE Automation component to work correctly.

The Network Address refers to the server name upon which the OLE Automation Server resides.  The Network Protocol refers to the type of network through which the OLE Client and OLE Server will be communicating; SetupWizard generates this list from those listed in the SWDEPEND.INI file.  If at the time of the disk build the Network Protocol field is left at its default setting, "[End user must specify]," then the installing end user will have to choose the network protocol at run time.  The Authentication field allows six valid options, listed in the drop-down box.  For further details, refer to the Remote Automation documentation (in the Enterprise Edition only).

Once you are done filling in the server information, choose the OK button to continue.


See Also

Add Files Button

Add OLE Servers Button

Back Button

Exit Button

File Details Button

Finish Button

Help Button

Next Button

Rebuild the Project's EXE File Check Box

Save Template Button

Select VBP File Button

SetupWizard Commands

Summary Info Button


Add OLE Servers Button

See Also

The Add OLE Servers button is available at Step 5 of the SetupWizard.  Use this button to add OLE Automation components to the list of files to be distributed with your application.

(Enterprise Edition only)  If the file chosen is an OLE Automation registry information file (.VBR), SetupWizard will display the Remote OLE Server Details dialog.


See Also

Add Files Button

Back Button

Exit Button

File Details Button

Finish Button

Help Button

Next Button

Rebuild the Project's EXE File Check Box

Remote OLE Server Details Button

Save Template Button

Select VBP File Button

SetupWizard Commands

Summary Info Button


Remote OLE Server Details Button

See Also

The Remote OLE Server Details button is available at Step 5 of the SetupWizard.  Use this button to add the network address, network protocol, and authentication information needed in order for the remote OLE Automation server to function correctly.


See Also

Add Files Button

Add OLE Servers Button

Back Button

Exit Button

File Details Button

Finish Button

Help Button

Next Button

Open Template Button

Rebuild the Project's EXE File Check Box

Save Template Button

Select VBP File Button

SetupWizard Commands

Summary Info Button


Using SetupWizard on 16-bit vs. 32-Bit Platforms

See Also

There are several differences in SetupWizard functionality, depending on which version of Visual Basic you are using.

Long Filename Support

All 32-bit (Standard, Professional and Enterprise) Setup Toolkit components support long filenames, but the 16-bit setup toolkit will only work correctly with short filenames.

Application Removal

Only the 32-bit versions of Setup Toolkit support application removal functionality.

Remote OLE Automation Server Distribution

The 32-bit Enterprise Edition Setup Toolkit supports client and server-side installation of remote OLE Automation Servers under 32-bit operating systems.  The 16-bit Enterprise Edition Setup Toolkit supports client-side OLE Automation server installations for 16-bit applications. Remote Procedure Call services are intrinsic to 32-bit operating systems, but to run 16-bit client components on 16-bit or 32-bit Windows operating systems, or to run client components on 16-bit computers, 16-bit RPC support is required.  When you use the SetupWizard to create the distribution media for your 16-bit application and you specify a .VBR file (Remote Support file) by using the Add OLE Servers button, the RPC files are automatically included in the setup media.  These files are listed in the SWDEPEND.INI. and may be distributed under the conditions of the RPC File Redistribution Agreement.

For more information on Remote Procedure Call services and file distribution, see Chapter 7, "Implementing OLE Servers," in the Building Client/Server Applications with Visual Basic book, included with Enterprise Edition documentation.


See Also

RPC File Redistribution Agreement


RPC File Redistribution Agreement

"With respect to the identified files, in addition to the rights granted in the development license for the MS code, Microsoft grants you a nonexclusive, royalty-free right to internally use such files.  With respect to these files, Microsoft grants you a non-exclusive, royalty-free right to use, reproduce, and distribute the object code version of such files provided that you:

1.	Distribute the Redistributables only in conjunction with and as part of your software application product which is designed to operate in the Windows environment;

2.	Do not use Microsoft's name, logo, or trademarks to market your software application product;

3.	Include a copyright notice for your software application product sufficient to protect Microsoft's interest in the Redistributables;

4.	Agree to indemnify, hold harmless, and defend Microsoft from and against any and all claims or lawsuits, including attorney's fees, that arise or result from the use or distribution of your software application product;

5.	Do not permit further distribution of the Redistributables by your end-user customers.

You are encouraged to test previous beta versions of your software using this release, but you are solely responsible for updating your customers with a version of RPC and your software application product that work with this commercial release and subsequent releases of RPC.  You acknowledge that Microsoft will not be obligated to make RPC or any of the Redistributables available as a final commercial product.

THE REDISTRIBUTABLES ARE PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE AND WARRANTY AGAINST INFRINGEMENT."


Install As Remote OLE Server

If you check this option, then the Automation Manager support files (AUTMGR32.EXE and AUTPRX32.DLL) will be added to the file list.  Since remote OLE Automation servers can only be installed on 32-bit operating systems, the last check box will only appear in the 32-bit Enterprise Edition.


Install OLE component as a standalone file
Install OLE component as stand-alone file

If you select this option, the OLE component will be installed as a stand-alone file into the application directory specified.


Install OLE component as a shared file
Install OLE component as shared component

If you select this option, the OLE component will be installed as a shared OLE component into the shared components directory (\OLESVR).


Help Files


Documents the SetupWizard application.  For information
about the Setup Toolkit, see the Visual Basic Help file.


Documents Visual Basic for Windows.


Documents the Data Access application.


Documents the Data Manager application.


Tutorials for learning to use Visual Basic for Windows.


Documents Microsoft Support Services.


Lists the applications written in Visual Basic that demonstrate
techniques discussed in the printed documentation.


Documents the custom controls provided with the
Professional Edition.


Documents the Crystal Reports application.


Documents the segmented hypergraphic editor for creating
hotspots within graphics for use in authoring Help files.


Documents the installation tools for ODBC.


Documents the ODBC driver for SQL Server databases.


Documents the VisData sample application.


Documents Windows functions as used in the C programming language.


Documents the Code Profiler add-in.


Documents Remote Automation, the Component Manager,
Remote Data Objects (RDO), and the RemoteData control
provided with the Enterprise Edition.


Documents the SourceSafe add-in for administrators.


Documents the SourceSafe add-in for users.


Text Files

Microsoft Visual Basic 4.0 includes additional information in the following files:

Text File	Description

APILOD.TXT	Describes how to use the API Text Viewer.

LABELS.TXT	Contains information about mailing labels.

PACKING.LST	Lists all files on the distribution disks provided with Visual Basic.

VB4DLL.TXT	Contains additional information about developing dynamic link libraries (DLLs) to use with Visual Basic.

VB4Q&A.WRI	Contains frequently asked questions concerning Visual Basic version 4.0 and the appropriate answers.

WIN31API.TXT	Contains procedure, constant, and type declarations for 16-bit versions of Windows API functions.

WIN32API.TXT	Contains symbolic constants for 32-bit versions of Windows API functions.

WINMMSYS.TXT	Contains procedure, constant, and type declarations for Windows 3.1 multimedia API functions.