Note The following Microsoft Knowledge Base article contains the latest versions of the Microsoft Visual Basic run-time files included with Visual Studio 6.0 Service Pack 6.
For additional information about the Service Pack 6 version of the Visual Basic 6.0 run-time files, click the following article number to view the article in the Microsoft Knowledge Base:
Release Date: September 18, 2000
For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
VBRun60.exe installs the following core files. These files are included with Visual Basic 6.0.
|ASycFilt.dll||2.30.4261.1||144KB (147,728 bytes)|
|ComCat.dll||4.71.1460.1||21.7KB (22,288 bytes)|
|MSVBVM60.dll||188.8.131.52||1.34MB (1,409,024 bytes)|
|OLEAut32.dll||2.30.4261.1||584KB (598,288 bytes)|
|OLEPro32.dll||5.0.4261.1||160KB (164,112 bytes)|
|STDOLE2.tlb||2.30.4261.1||17.5KB (17,920 bytes)|
These files are the base dependencies for any component or application created in Visual Basic 6.0. In addition, the following files are also installed by VBRun60.exe:
|ADVPack.dll||4.71.1015.0||73.2KB (74,960 bytes)|
|W95Inf16.dll||4.71.704.0||2.21KB (2,272 bytes)|
|W95Inf32.dll||4.71.0016.0||4.50KB (4,608 bytes)|
|VBRun60.inf||N/A||1.04KB (1,069 bytes)|
These files are supporting files for the VBRun60.exe self-extracting file.
For information about the command-line arguments available for the VBRun60.exe file, enter the following at the command-line:
For additional information about documentation on command-line arguments, click the following article number to view the article in the Microsoft Knowledge Base:
Do I need the VBRun60.exe file?The VBRun60.exe file is not intended to replace the Package and Deployment Wizard (PDW) for distributing Visual Basic applications. For example, if your application includes components, such as ActiveX controls or DLLs, you should use the PDW or a third-party setup package for distribution. However, if your Visual Basic application only depends upon the files included in the VBRun60.exe file, you can distribute your application by providing end users with the executable (.exe) file and VBRun60.exe.
To determine whether your application requires additional files for distribution, you can use the PDW to create a set of setup files as a test. When the PDW creates a setup package, it creates a Setup.lst file. You can open the Setup.lst file in any text editor (for example, Notepad). If the [Setup1 Files] section of the resulting Setup.lst file only lists your .exe file, end users should be able to run your application after running VBRun60.exe to install the core run-time files. However, if the [Setup1 Files] section contains multiple files, you should consider using the PDW or a third-party setup package for distribution instead.
In addition to distributing simple executables, you can also use the VBRun60.exe file for the following:
- To minimize the size of Internet downloads of Visual Basic applications
By running the Vbrun60.exe file ahead of time, users can download your application from the Web faster.
- As a troubleshooting step when an installation of Visual Basic or a Visual Basic application fails
If Setup fails with an error message that mentions one of the core files or if registration of a component fails during Setup, the core files on the target computer might be mismatched. If the versions of the files in the VBRun60.exe file are newer than the versions on the target computer, you might resolve the problem by running the VBRun60.exe file before you run Setup.
Note The version of the VBRun60.exe file that is included in this Knowledge Base article contains the same run-time file as the one on the installation CD-ROM.
For additional information about how to get the files for Visual Basic 6.0 SP6, click the following article number to view the article in the Microsoft Knowledge Base: