Dependency Information at P&D Wizard
-
Hi all, I wrote a wrapper around an OCX (making it a dll) to make the interface simpler for others to program around the OCX. The problem is that when I try to use the Package & Deployment Wizard to package it, I get this message: "Below is a list of files for which dependency information could not be found. To proceed without the dependency information for the file(s) listed, click OK. To permanently mark a file as having no dependencies, select its checkbox.":confused: 3 Questions: 1) Is it unwise to wrap a DLL around an OCX? 2) How do I create a dependency file for the DLL? 3) If I don't need a dependency file, how can I be sure before actually building the project and installing it on some bare bones PC? :rolleyes: Thanks Guys and Gals, :-D Oh, yeah. I also get the dependency information message for: dao360.dll. How can I fix this, too?
-
Hi all, I wrote a wrapper around an OCX (making it a dll) to make the interface simpler for others to program around the OCX. The problem is that when I try to use the Package & Deployment Wizard to package it, I get this message: "Below is a list of files for which dependency information could not be found. To proceed without the dependency information for the file(s) listed, click OK. To permanently mark a file as having no dependencies, select its checkbox.":confused: 3 Questions: 1) Is it unwise to wrap a DLL around an OCX? 2) How do I create a dependency file for the DLL? 3) If I don't need a dependency file, how can I be sure before actually building the project and installing it on some bare bones PC? :rolleyes: Thanks Guys and Gals, :-D Oh, yeah. I also get the dependency information message for: dao360.dll. How can I fix this, too?
Here are the answers to the questions I provided (If anyone cares.) Let me just say that everyone has a purpose in life and sometimes that purpose is to set an example. This is a case of an example of something to NOT do. <<1) Is it unwise to wrap a DLL around an OCX?>> This could be argued for or against, i guess; but, be forwarned - It's a bitch to get the thing working in a distributable package. That being said, I killed the dll project. So, for a newbie VB Programmer, Yes. Without a doubt - don't try it. I'm sure someone knows how to do this, though it ain't me. <<2) How do I create a dependency file for the DLL?>> The package and deployment wizard has a dependency file wizard that works pretty well. It detected all the dependency information for another dll we wrote. However, the one I was working needed much more information than it could generate automatically. Since sometimes "less is more,' I'm going to end with that. <<3) If I don't need a dependency file, how can I be sure before actually building the project and installing it on some bare bones PC? >> Now that I know a little bit more about dependency files, I'm no expert therefore I shall not even try to submit information to someone else on this as I may 'bum-dope' someone. I have my theories; but, they are largely untested. In closing, it was a foolish idea to wrap an ocx in a dll and think that the interface I was writing would be 'easier.' But, hey, I learned something for it which is better than nothing. Later.
-
Here are the answers to the questions I provided (If anyone cares.) Let me just say that everyone has a purpose in life and sometimes that purpose is to set an example. This is a case of an example of something to NOT do. <<1) Is it unwise to wrap a DLL around an OCX?>> This could be argued for or against, i guess; but, be forwarned - It's a bitch to get the thing working in a distributable package. That being said, I killed the dll project. So, for a newbie VB Programmer, Yes. Without a doubt - don't try it. I'm sure someone knows how to do this, though it ain't me. <<2) How do I create a dependency file for the DLL?>> The package and deployment wizard has a dependency file wizard that works pretty well. It detected all the dependency information for another dll we wrote. However, the one I was working needed much more information than it could generate automatically. Since sometimes "less is more,' I'm going to end with that. <<3) If I don't need a dependency file, how can I be sure before actually building the project and installing it on some bare bones PC? >> Now that I know a little bit more about dependency files, I'm no expert therefore I shall not even try to submit information to someone else on this as I may 'bum-dope' someone. I have my theories; but, they are largely untested. In closing, it was a foolish idea to wrap an ocx in a dll and think that the interface I was writing would be 'easier.' But, hey, I learned something for it which is better than nothing. Later.
OK. Well, it was bugging me. I fixed my problem. Hmm, acutally, I worked around it. I wrote a script to copy the associated DLLs, TLBs and OCXs to the future installation directory then registered each and every one using regsvr32. Then I ran the setup.exe. It worked great on systems that didn't contain any of the DLLs, TLBs or OCXs. So, there! ;P