-
Let me start by saying that I am a relative VB novice and am not the most efficient or structured programmer around or I would not have this problem. Anyway, I have a very large project which uses numerous references and components. Over time, I’ve had a tendency to add some of these references/components in order to see if it was needed for my application. For example, the DBGRID ocx file needs to be added to your project before you can use the DBGRID control. Even though a particular reference or component may not have been needed for a specific problem I may have been having while coding, I may have inadvertently left the reference/component turned on. Now, when it comes time to distribute my project to other platforms, I’d rather not have to port a whole bunch of unnecessary ref/com files. The only way I know how to check to see if one of these files is actually necessary is successively remove each of these ref/com and rerun the code. I would rather not have to this since it will take forever to check that everything in the entire application is still functioning properly. Is there any “debugging” capability in VB that would list all the external references that are necessary for the entire code??? Thanks very much in advance.
-
I have program like this.
It's called Dependency Walker (DepWalker). It's very good program. It tells all loaded libraries that uses the program you're examining.
You load exe to it and then run it through that program. It'll tell you all required files (and a lot of other stuff). You can find it somewhere on MS' site.
-
First make sure your settings are correct. Select Project --> Properties. On the Make tab there's a checkbox that says 'Remove information about unused ActiveX Controls'. Make sure this checkbox is checked.
Next you can make a dependency file with the Package and deployment wizard (VB6) or the Setup Wizard (VB5). The dependancy file will list all dll's and ocx's that are required by your program.
-
Thanks very much. I'll give them a try.
KBH
