|
-
Oct 20th, 2001, 12:56 PM
#1
Thread Starter
New Member
Packaging Dependency Question - HELP!!
I'm fairly new to packaging/deployment. When I go to package the application, I get a message that there is dependency information that is out of date, with 3 .OCX files listed as out of date.
What do I need to do to resolve this problem so that I can successfully package this app?
Thanx in advance for any help!
Celubrius
-
Oct 20th, 2001, 01:00 PM
#2
Member
It's probably not an issue; I get tons of errors when using the VB5 equivalent of the PDW and my programs always install just fine.
-
Oct 20th, 2001, 01:10 PM
#3
Well ...
Originally posted by Celubrius
I'm fairly new to packaging/deployment. When I go to package the application, I get a message that there is dependency information that is out of date, with 3 .OCX files listed as out of date.
What do I need to do to resolve this problem so that I can successfully package this app?
Thanx in advance for any help!
Celubrius
Yep, as filburt1 said, these errors are most of the times harmless. To correct the situation, you can install the latest service pack.
Dependency files simply list out the runtime dependencies of the components you are using in your project. It is highly unlikely that these change over a period of time, so it's probably some version conflict with the version of the control being newer than that listed in the dependency file. In most cases, you can ignore these errors. Sometimes even if dependency information is not available, you can proceed with the packaging/installation.
However, if you are using any custom/third party controls or freeware controls, then there could be trouble. Again, it doesn't mean there always is.
.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|