Article ID: 198052
Article Last Modified on 9/30/2007
APPLIES TO
- Microsoft Visual Basic 5.0 Learning Edition
- Microsoft Visual Basic 6.0 Learning Edition
- Microsoft Visual Basic 5.0 Professional Edition
- Microsoft Visual Basic 6.0 Professional Edition
- Microsoft Visual Basic 5.0 Enterprise Edition
- Microsoft Visual Basic 6.0 Enterprise Edition
This article was previously published under Q198052
SYMPTOMS
When running the Visual Basic 5.0 Setup Wizard, you receive the following warning message:
NOTE: You can choose to ignore this for now by clicking Next, but your setup and application may not work correctly.
When running the Visual Basic 6.0 Package and Deployment Wizard (PDW), you receive the following warning message:
CAUSE
Each component listed below the warning message has a dependency (.dep) file that contains information about all the files required by that component. However, the version number of the component as specified in the .dep file does not match the version number of the component itself.
In other words, the .dep file was created for a different version of the component, so the wizard is unable to determine which files the component requires.
RESOLUTION
If the indicated file comes from a third party, contact that party for the updated .dep files.
If the indicated file is a Visual Basic component that you created, follow these steps to create a .dep file:
- Restart the Setup Wizard or PDW.
- In the Setup Wizard, select the project file for this component, the Generate Dependency File Only option, and continue through all the steps to create the dependency file.
-or-
In the PDW, select the project file for this component, and choose the Dependency File option on the Package Type screen. Continue through all the steps to create the dependency file.
NOTE: Save the .dep file in the same folder as the component file.
- Restart the Setup Wizard or PDW and try the current project again.
STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.
This bug was corrected in Visual Studio 6.0 Service Pack 3.
For additional information about Visual Studio service packs, click the article numbers below to view the articles in the Microsoft Knowledge Base:
194022 INFO: Visual Studio 6.0 Service Packs, What, Where, Why
194295 HOWTO: Tell That Visual Studio 6.0 Service Packs Are Installed
MORE INFORMATION
If you are unable to obtain a .dep file for the component(s) indicated in the warning message, you can ignore the warning message in the following two cases:
- You are confident that no other files are required by the component. -or-
- You know which files are required and can add them manually in the File Summary screen in the Setup Wizard or the Included Files screen in the PDW.
NOTE: Check the end-user license agreement and redistributable files list for information about which files are redistributable. (In Visual Basic 5.0, check the License.txt and Redist.txt files, both located in the "Program files\DevStudio\VB" folder. In Visual Basic 6.0, check the Eula.txt file in the "Program Files\Microsoft Visual Studio\Common\Setup\1033" folder and the Redist.txt file in the "Program Files\Microsoft Visual Studio" folder.)
You can use a utility, such as Dependency Walker, to determine file dependencies. However, it is important to note the following when using Dependency Walker:
- You do not need to distribute all the files listed as dependencies in the utility. Many of the listed files are operating system files. If you are unsure about which files to distribute, check the end-user license agreement (License.txt in 5.0, Eula.txt in 6.0) and Redist.txt files.
- The utility cannot determine dynamic module dependencies. For example, if Module A dynamically loads Module B via a LoadLibrary-type technique, Module B becomes a run-time dependency of Module A, but will not be listed in Module A's import table. Because Dependency Walker depends on information in the import table to determine dependencies, it will not detect that Module A is dependent upon Module B.
If you have Microsoft Visual Studio 6.0 and installed the Win32 SDK Tools, you can start Dependency Walker using the following steps:
- Click the Start button, point to Programs, point to Microsoft Visual Studio 6.0, and then point to Microsoft Visual Studio 6.0 Tools.
- Click Depends.
If you do not have the Win32 SDK Tools installed, follow these steps to install them:
- Click the Start button, point to Settings, and then click Control Panel.
- Double-click the Add/Remove Programs icon.
- Click the Install/Uninstall tab, and then double-click Microsoft Visual Studio 6.0.
- In the Setup dialog box, click Add/Remove.
- In the Options list, select Tools (do not click the check box), and then click Change Option.
- Click the Win32 SDK Tools check box to select it, and then click OK.
- Click Continue.
If you have the standalone Visual Basic 6.0 product, you can find Dependency Walker in the COMMON\TOOLS\VB\UNSUPPRT\DEPEND folder on Disk 1.
The Dependency Walker, among other tools, is included with the Platform SDK under the Tools\Platform SDK Tools in the installer. After installing the needed portions of the SDK, you can find Depends.exe on the Start menu under Microsoft Platform SDK\Tools\Depends. (The utility works on Microsoft Windows 95, Microsoft Windows 98, Microsoft Windows Millennium, Microsoft Windows NT, and Microsoft Windows 2000.) The documentation for the utility is in Depends.hlp, which can be found in \Program Files\Microsoft Platform SDK\Bin.
REFERENCES
For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base:
178354 INFO: How Setup Wizard and PDW Uses Dependency Files
172888 PRB: ComCtl32.ocx - The Dependency File is Out of Date
190777 BUG: PDW: Out-of-Date Dependency Information COMCT332.OCX
Additional query words: kbfix
Keywords: kbappsetup kbbug kbfaq kbfix kbfix kbvs600sp3fix kbwizard KB198052
