I developed this project for own purpose and I thought this will prove equally helpful to you all as well, hence posting it on PSC. Upon selection of Visual Basic 6.0 Project File (*.vbp); this tool will scan the Project and list out all the OCXs, DLLs, TLBs which you have referenced from your Project and it will copy all Project dependency files to one single folder on one button click! There are few options provided to make it more useful and handy. Please read the included ReadMe.txt file for further details.
======================================================
## Update 12th Feb 2006. Right-click Popup menu for Dependency List, press Esc key to close Splash screen, Open dependency file's folder from application interface. Please see Update_Log.pdf file for complete list of updated features.
======================================================
Update 23rd Feb 2006. This is a very useful update. Two new features added. [1] Now you can access Properties dialog for Dependency File listed in List of Dependency Files. [2] Shell menu integration for VBP files.
======================================================
Note: Due to the size or complexity of this submission, the author has submitted it as a .zip file to shorten your download time. Afterdownloading it, you will need a program like Winzip to decompress it.Virus note:All files are scanned once-a-day by Planet Source Code for viruses, but new viruses come
out every day, so no prevention program can catch 100% of them. For your own safety, please:
Re-scan downloaded files using your personal virus checker before using it.
NEVER, EVER run compiled files (.exe's, .ocx's, .dll's etc.)--only run source code.
Scan the source code with Minnow's Project Scanner
If you don't have a virus scanner, you can get one at many places on the net
including:McAfee.com
Terms of Agreement:
By using this code, you agree to the following terms...
You may use
this code in your own programs (and may compile it into a program and distribute it in compiled format for languages that allow it) freely and with no charge.
You MAY NOT redistribute this code (for example to a web site) without written permission from the original author. Failure to do so is a violation of copyright laws.
You may link to this code from another website, but ONLY if it is not wrapped in a frame.
You will abide by any additional copyright restrictions which the author may have placed in the code or code's description.
Under Options & Settings, the first three options are added specifically for PSC users who use some DLLs or OCX files in their projects and either forget or fail to upload those with their Project on PSC. The first option will rename DLL/OCX/TLB files to _ll/_cx/_lb ; the second option will automatically create a Batch file in same folder which, on execution, will rename all files back to their normal extensions. The third option will make the Application to add regsvr32.exe which will make the users not to search for this tool to register components on their system ... just to make everything set for the show! Please let me know if you like it and find useful. At least leave comments, if not finding it worth to vote for! Thanks. (If this comment was disrespectful, please report it.)
Thanks Ian and Eagle for your comments. Glad to see that you find it useful in your work. I have updated the Tool on DLL path recognition. Few more updates are due; once done, I will post it here. Thanks to all of those who have voted for this tool. Please keep visiting this Project page as many feature-updates are due! Thanks. (If this comment was disrespectful, please report it.)
How are you suppose to use the RegSvr32.exe ? Clicking on it just says the dll is missing. Nice program by the way. (If this comment was disrespectful, please report it.)
Hello Kenneth, Thanks for your nice words about the program. To use RegSvr32 to register a component without going to Command Prompt, just drag-n-drop the component which you want to register over regsvr32.exe file. This will register your component. That's why to make it easy, Application puts RegSvr32.exe in the same folder of dependency files. Try it. It always worked on my XP and 2000 systems. By the way, if you feel this tool is useful, then please come back and vote for it and give me some encouragement to update this tool with better and better features implemented. Thanks. (If this comment was disrespectful, please report it.)
Very handy tool! Thanks Rutaraj for your effort! Two minor suggestions: (1) add a "select/deselect all" option for the dependency file checkboxes. (2) Set lblSize.Caption ="0" each time a new project is loaded (else the kb are accumulated). Thanks again! (If this comment was disrespectful, please report it.)
Thanks Stavros for your comments and suggestions. I have already added Select All/Deselect All options to Dependency List as a next update. But I missed out to make the Size to Zero on new Project load! I will rectify this issue as well and post the update on PSC. Thanks. (If this comment was disrespectful, please report it.)
Ruturaj this is really nice! This is great for people who write freeware/shareware apps and wish to make sure their installation CD's contain all dependencies that the user may not have. Logical, easy to use interface and does exactly what it says it does. 5 dependencies from me, thanks again! (If this comment was disrespectful, please report it.)
Thanks Matt and Richard for your appreciation and votes. Encouragement from from such an experienced programmers such as you guyes is much valuable thing for me. Thanks. The next update of this utility is getting ready. In this update, I have implemented Shell Menu integration (Scan for Dependencies, Collect Project Dependencies menu items will be added to shell's right click menu for *.vbp files) and HTML Report generation for Project Dependencies. I will post it as soon as I complete its testing. Please keep visiting this Project page as few more important updates are due. Thanks a lot to you all for your votes and comments. (If this comment was disrespectful, please report it.)
Hello Danny and Jim; I'm glad to see that you found this tool useful! Currently I'm little busy in my work; so not able to spend time on development of this tool. As soon as I get some time, I will update this project and post it here. Once again thanks a lot for your votes and comments guys! (If this comment was disrespectful, please report it.)
Hello Rusman; Thanks for your whole hearted appreciation and comment. I have already sent you email regarding your requirement. Please vote if you liked this tool. Thanks. (If this comment was disrespectful, please report it.)
hallo Ruturaj, thanks for email 5 G! vote from me.great tool but i hope you cant help ruturaj? thanks. (If this comment was disrespectful, please report it.)
Hello Ruturaj, That's great tool, that tool is the one that I wont to builded before. One's again that's an Excellent tool. (If this comment was disrespectful, please report it.)
Thanks gregw and Erwin for your comments. Thanks to all of you who have voted for this project which eventually fetched my first PSC Coding Award! Thanks a lot. I have updated this tool to further which now includes many useful advancements. I will post it to PSC once I complete it. Once again thanks to all of you for your comments and votes! (If this comment was disrespectful, please report it.)
I know an util called Depends.exe, but your utility it's excellent to use join to inno setup!! excellent work!! (If this comment was disrespectful, please report it.)
The new version of this tool is getting ready for public release. In that, I have already implemented the Inno Setup feature. The next version of Project Dependency Collection Tool writes Inno Setup script lines for you to simply copy and paste in your Inno Setup Script. BTW, Oliver I tried to send you Email but it didn't work. I request you (and all PSC coder's account owners) to please keep your account info updated. It's so nice for a person like me to be able to contact the talented people like you! So, please see that your account Email addresses are working and alive. Thanks. (If this comment was disrespectful, please report it.)
Not to burst anyone's bubble here, but if people get around PSC's limitations on uploading OCX / DLL files, wouldn't that just encourage malicious tricksters into uploading all manner of viruses / trojans? The reason PSC banned OCXs and DLLs was because it was too easy for hackers and script kitties to do real damage to unwitting coders. Their removal is a protection for the PSC community. I know its frustrating for the 99% that follow the rules as no one likes to have to download a dll offsite, but this program could empower malicious coders. (If this comment was disrespectful, please report it.)
Hello Brian! Thanks for your fair words regarding the use of this Program. I have something to say on the issue which you have raised. Well, if the reason for you, to consider this tool being handy for hackers, is the fact that it can collect DLLs/OCXs and rename it so PSC ZIP scanner will not detect it then I tell you there are several other ways already in use on PSC. PSC ZIP scanner is not RAR compatible; one also may add components in Resource File and get distributed with project file; PSC scanner will not detect it. Firstly, You will never get to see the actual presence of file if that's in RAR or RES file (especially RES file); with this tool, at least you come to see those actual files. (If this comment was disrespectful, please report it.)
Secondly, this tool renames the component files; and COM DLLs/OCXs are nothing when those are not with OS recognizable file extension; so no harm from renamed components. Thirdly, you need to manually rename those components which will be action taken by you at your own will; components from RES can be automatically installed on Form_Load event on your machine (if you are one of those many PSC uses who simply load project and run rather than first going through the code; then see how much dangerous it is!). So, by no means I find this tool to be more handy for malicious coders than for talented ethical programers here-around. After all use of any tool depends on how ethical the user is ... hackers anyhow find out many ways to do their task; right? (If this comment was disrespectful, please report it.)
Secondly, this tool renames the component files; and COM DLLs/OCXs are nothing when those are not with OS recognizable file extension; so no harm from renamed components. Thirdly, you need to manually rename those components which will be action taken by you at your own will; components from RES can be automatically installed on Form_Load event on your machine (if you are one of those many PSC uses who simply load project and run rather than first going through the code; then see how much dangerous it is!). So, by no means I find this tool to be more handy for malicious coders than for talented ethical programers here-around. After all use of any tool depends on how ethical the user is ... hackers anyhow find out many ways to do their task; right? (If this comment was disrespectful, please report it.)
Oh yes and one more thing ... it's not for you only but for all ... please don't feel that you are bursting a bubble when commenting on my project. I'm always open for wise and fair comments/suggestions. So, please feel free to convey your thoughts to me; we will discuss it here. No problem at all; just make sure that you are descriptive in your comments if you feel this tool is not useful for some reason. I thank you all for your comments and votes.
Regards,
Ruturaj. (If this comment was disrespectful, please report it.)
I appreciate the response and understand the ways in which the program is not dangerous. The only thing I'm concerned about is the program could be used maliciously if desired. Most people (perhaps not yourself, but MOST) do not scroll through every line of code to determine if it is going to be malicious. It takes time and a great deal of effort especially when there's thousands of lines of code to consider. I don't doubt that this could be a great tool for distributing DLL/OCX. I'm also aware that there are other ways of subverting the safeguards PSC has put in place. It will have to be up to each user to decide if they are comfortable downloading code so cleverly "packaged". As for me, I'd rather not take any risks... (If this comment was disrespectful, please report it.)
First of all great code and great tool. My comments are as follows: 1. It seems to me that this tool is basically replicating what is already available in the P&D Wizard that comes with the VB6 install. 2. Users have to be VERY careful in how they package their support files. Just blindly copying the OCXs/DLLs from the system directory could prove to be very dangerous. There are some support files that are meant only for certain OS's. You have to make sure that the support files you are packaging are the redistriburabel versions for the appropriate OS version. 3. Some DLLs if pulled from a deelopers system and blindly copied to a users system may render it unbootable. It is still up to the developer to research each and every support file that is packaged with their app to make sure it is safe and appropraite to distribute.
AGP (If this comment was disrespectful, please report it.)
I'm very sorry to see that Dependency Collection tool did not work for you! If possible, can you please send me the VBP file (no need of sending complete project)? Please send that to my email: mailme_friends@yahoo.com
This will surely help me to improve the code and see where exactly it's going wrong. It worked for me till the date and for others, the success rate of this tool over 98%. I'm eager to see where exactly the tool is not working for you.
Waiting for your reply ...
Regards,
Ruturaaj. (If this comment was disrespectful, please report it.)
Anybody who is facing trouble while using this tool then please let me know your opinion directly to: mailme_friends@yahoo.com
It will be best for me to see where exactly it's going wrong if you can send e the VBP file of your project. Please note that no need of sending me the complete project (forms, classes, modules etc.) Just send me the VBP file and that will be enough for me to see where the tool is going wrong for you. Otherwise it's next to impossible for me to judge why this tool didn't work for you. It worked for me till the date without fail. Curious to know your test results, too. Currently, busy in some other projects; but I will surely improve this tool as soon as I get some free time. Thanks to all for your interest and cooperation! (If this comment was disrespectful, please report it.)
Hi Thanx for sharing this tool with us. (If this comment was disrespectful, please report it.)
Add Your Feedback
Your feedback will be posted below and an email sent to
the author. Please remember that the author was kind enough to
share this with you, so any criticisms must be stated politely, or they
will be deleted. (For feedback not related to this particular code, please
click here instead.)
By 28 Users
Download code
2/11/2006 7:15:06 AM: 
