The information in this article applies to:
SYMPTOMS
When creating a setup program with the Visual Basic Package and Deployment
Wizard (PDW), the following message is received:
Below is a list of files for which dependency information could not be found. To proceed without the dependency information for the file(s), click OK. To permanently mark a file as having no dependencies, select its checkbox. This article describes why this warning is received. CAUSEThe project includes a component such as the Microsoft Script Control 1.0 (MSSCRIPT.OCX), which does not have a .dep file and has no pertinent information in VB6DEP.INI. RESOLUTION
In the case of a control such as MSSCRIPT.OCX, which does not need any
additional files to be distributed with it, the message regarding "Missing
Dependency Information" may be safely ignored.
STATUSThis behavior is by design. MORE INFORMATION
The Package and Deployment Wizard checks for component dependency
information in both the VB6DEP.INI and in the directory where the component
is located. Dependency information (.dep) files list the files required for
a component to run correctly.
REFERENCESIf a dependency file needs to be created manually for the component, please see the following article in the Microsoft Knowledge Base: Q178354 INFO: Dependency Files and How Setup Wizard/PDW Use ThemFor additional information, please see the following article(s) in the Microsoft Knowledge Base: Q198052 PRB: 'Out-of-Date Dependency' Warning in Setup Wizard and PDWFor additional information about how the Package and Deployment Wizard uses dependency information, refer to the "Dependency Files" topic in Online Help for Microsoft Visual Basic. Additional query words: PDW dependencies kbdss
Keywords : kbwizard kbAppSetup kbInternet kbVBp kbVBp600 kbGrpVB kbPDWizard |
Last Reviewed: January 5, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |