i just tried using the package and deploy wizard for the first time. i got a warning saying that dependencies were found but they are out of date. do you want to proceed anyway? i said yes, but i have no idea what it was telling me or if it means there is a problem
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
P&D wizard dependencies out of date
- Thread starter javaguy1
- Start date
- Thread starter
- #2
Some components which are included in your project need other components in order to run,
Such as with just a single reference to a component, this component itself may need (many) other components, and that of the correct version, in order to run correctly.
A dependency file for a component of your application will list up the other components and their versions it needs to run.
Your application it self has dependencies (and you can use the P&D to create a dependency file for it, and add additional files you decide are be a must to have).
If you add for instance a Rich Text box to it, then you cannot just copy your application over to another machine and expect it to run with-out the RichTextBox files to also be there, and of the same version.
The RichTextBox (RichTx32.ocx) also needs certain additional files in order to run. You cannot just copy the RichTx32.ocx over to the other machine and expect it to work, when these components are also missing.
And then further, these "other" components may also need additional components in order to run.
In order to determine which files and versions a Component needs to run (esp. if it needs additional components), a *.Dep file exists in the Windows folder for that component.
For the RichTx32.ocx you will find the RichTx32.DEP file, and can open it with a text editor to inspect what it needs.
If a Dependency file is missing for a component like this, you will get an appropiate message that it is missing.
If the *.Dep DOES exist, then a version comparison is made between the actual file versions on the system, which are to be added to the package, and the versions that are reported needed for those files in the Dependency file.
If these do not match, you will also get a message - as in your case.
Sometimes a component gets updated on your system with-out an updated dependency file being also installed (sloppy sloppy)
Usually you can get a depencency file update from the manufacter of the component, or, if it is a system or VB component, an Update to the most recent service pack may correct this.
Sometimes not.
If you know that the component still needs the same identified files as before, but just a different version, then you can manually change the dependency file yourself (don't forget to also check for dependency files for each of the components listed in the first dependency file - and make copies first), in order to surpress the message, or just ignor it all-together if you know everything is ok, or, as I've seem in some cases, a dependency file doesn't exist at all.
This advice is not a recommendation, (as you should get the proper dependency files which match the components onto your system), but as a last resort.
If ignor these steps, you basically risk that your program will not run properly, or at all, if some additional files needed are missing from the package, or if you possibly have two different versions of a file on your system and the wrong one is included in the package.
Such as with just a single reference to a component, this component itself may need (many) other components, and that of the correct version, in order to run correctly.
A dependency file for a component of your application will list up the other components and their versions it needs to run.
Your application it self has dependencies (and you can use the P&D to create a dependency file for it, and add additional files you decide are be a must to have).
If you add for instance a Rich Text box to it, then you cannot just copy your application over to another machine and expect it to run with-out the RichTextBox files to also be there, and of the same version.
The RichTextBox (RichTx32.ocx) also needs certain additional files in order to run. You cannot just copy the RichTx32.ocx over to the other machine and expect it to work, when these components are also missing.
And then further, these "other" components may also need additional components in order to run.
In order to determine which files and versions a Component needs to run (esp. if it needs additional components), a *.Dep file exists in the Windows folder for that component.
For the RichTx32.ocx you will find the RichTx32.DEP file, and can open it with a text editor to inspect what it needs.
If a Dependency file is missing for a component like this, you will get an appropiate message that it is missing.
If the *.Dep DOES exist, then a version comparison is made between the actual file versions on the system, which are to be added to the package, and the versions that are reported needed for those files in the Dependency file.
If these do not match, you will also get a message - as in your case.
Sometimes a component gets updated on your system with-out an updated dependency file being also installed (sloppy sloppy)
Usually you can get a depencency file update from the manufacter of the component, or, if it is a system or VB component, an Update to the most recent service pack may correct this.
Sometimes not.
If you know that the component still needs the same identified files as before, but just a different version, then you can manually change the dependency file yourself (don't forget to also check for dependency files for each of the components listed in the first dependency file - and make copies first), in order to surpress the message, or just ignor it all-together if you know everything is ok, or, as I've seem in some cases, a dependency file doesn't exist at all.
This advice is not a recommendation, (as you should get the proper dependency files which match the components onto your system), but as a last resort.
If ignor these steps, you basically risk that your program will not run properly, or at all, if some additional files needed are missing from the package, or if you possibly have two different versions of a file on your system and the wrong one is included in the package.
- Status
Similar threads
- Locked
- Question