Testing Component Download on Development Machines

You can test your component download on your development machines to make sure that the download file installs correctly. However, because your development machines are likely to have some of the necessary components or files already installed, you may not experience the same download as your end users will. In addition to testing on your machines, it is important to also test your installation on a machine that does not have Visual Basic installed.

Note   If you do not have a machine without Visual Basic installed, you can simulate one. See "Simulating a Clean Machine" for instructions.

Testing Installation of the Component on the Development Machine

The simplest way to check your download is to remove the software registration from the registry, then access the page generated by the wizard.

Note   The procedures in this section require a copy of regsvr32.exe to be installed on your machine. If it is not, you can find it on the Visual Basic installation CD-ROM.

To test installation on the development machine

• If you are using Internet Explorer 4.0 or later, access the Downloaded Program Files folder in either the Windows or the Winnt40 directory, right-click the control, and select Remove. The system automatically removes and unregisters the item and any of its dependencies.
  
  
• If you are using a version of Internet Explorer prior to 4.0, run Regsvr32 to unregister the component, as in the following example:

  regsvr32 /u controldemo.ocx
  

If regsvr32.exe is not in your path, provide the full path to the file in your statement. Access the Web page the Package and Deployment Wizard created. The component should download.

Note   Remember to select Binary Compatibility in your Visual Basic project settings to prevent multiple, different class IDs for your software.

Note   If you leave the DestDir= line in the .inf file blank, the component file should appear in your Occache  or Downloaded Program Files directory. You may find other copies in subdirectories called conflict directories, such as Occache\Conflict.2. The date and time of each file will differ, indicating different builds of the control and different class IDs. Care must be taken to ensure that the Class ID remains the same between the builds.

For More Information   See "Version Compatibility in ActiveX Documents" in the Component Tools Guide for more information on binary compatibility.

Testing the Installation of Support Files on the Development Machine

In addition to removing the component registry, you should test that all of the necessary support files also install and register correctly. To do so, temporarily unregister everything in your system directory and your Occache or Downloaded Program Files directories.

Note   The procedures in this section require a copy of regsvr32.exe to be installed on your machine. If it is not, you can find it on the Visual Basic installation CD-ROM.

To test installation of support files on the development machine

1. Unregister the support files:
   • If you are using Internet Explorer 4.0 or later, access the Downloaded Program Files folder in either the Windows or the Winnt40 directory, right click the file, and select Remove. The system automatically removes and unregisters the item and any of its dependencies.
     
     
   • If you are using a version of Internet Explorer prior to 4.0, run Regsvr32 to unregister the files. Use the following command line in each applicable directory to unregister the necessary files:

     for %f in (*.ocx *.dll) do regsvr32 /u /s %f
     

2. Once all of the support files have been unregistered, access the Web page the Package and Deployment Wizard created. The component should download.

To reregister support files after testing

• Use the following command to restore the original entries:

  for %f in (*.ocx *.dll) do regsvr32 /s %f