Is there any way of packaging part of a DLL or do I always have to package the whole thing?
Say I had a simple program with only a form and text boxes, can I have a tiny DLL that only has the needed bits?
ummm....
To USE only part of a dll, Craig is right...
However... to PACKAGE a program... the whole DLL is required in the package no matter if you use only 1 function or all of the functions and subs in the DLL... the whole dll is required for Package and Deploy process...
this goes back to the theory of the design of the DLL's ...
They were intended to break down a huge program into smaller parts that can be used by multiple programs, dynamically... which means they do not have to be linked during compilation to create the EXE...
In doing this you want to DLL's by sometype of categories...
where the functions are all related in some way...
You don't want to dump your whole program into 1 DLL...
You want to split it up into several DLL's with related functions...
this way, you don't have to worry about the problem of packaging a 10meg DLL and only using 100k of it in your program...
like USER32 and GDI32 ... those 2 are "usually" used together... but you CAN use one without the other... so you wouldn't have to package 1 big DLL when you are using only half of the stuff in it...
If you are asking if you can split a DLL into smaller DLLs, I'm not sure if you can do this without the source code...
I believe there are some issues of copywrites... that avoid making this possible... To where you could rip off a few functions from a commercial DLL and put them in your own and say that you made them, without paying for them...
If you DO have the source code...
I STRONGLY suggest spliting it up into smaller ones...
Thanks for the comments everyone.
What I want to do is to package a very small app for sale on the internet ((its Exe is only 32k)and it only uses form,text box, label and oval shape controls.
It is an idea that millions of people could find useful.
If I can sell 100,000 for $5 each I will be very happy!
I want to make the download zip file as small as possible so I wondered if there was some utility that would create a DLL that only contained the vital bits as it could be much smaller.
C++ does this in effect with its library but I dont want to have to struggle anymore with that!
You would think all copies of windows would already have some of them but the package ends up over 1mb big.
Ted
Taking CubeE101's idea further, is there a way of determining if the required DLL files exist in the user's computer (say a Java thingy or something) before downloading any VB type DLL's or application program?
Then this thingy would only download what was needed.
Also how can you automatically register such seperately downloaded DLLs??
If it were me I would write it so I could maintain only one set of code. Turn on the items for those who pay and leave those items unchecked, off, false, or otherwise useless for those who don't fork over the dough, salmolies, casharoonies, or nuggets of gold from their fort knox's.
IMHO
So maybe if you tell us what this program is, and does? Just Kidding...
What I suggest for getting the files needed is to Create a Package using the PDW. Then simply look in the CAB file it creates. You can open CAB files with WinZip. That will list all the files that are needed.
Good luck with it.
Craig
"I feel sorry for people who don't drink. When they wake up in the morning, that's as good as they're going to feel all day." ~Frank Sinatra
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.