J-Man
06-15-2003, 04:24 PM
I have an application that requires the use of a DLL I created. Do you compile the DLL into your executable? Do you have to deliver the DLL with your application? Do you have to register the DLL on the target machines?
As you can tell, I'm new to the DLL world. Any help would be greatly appreciated! Thanks in advance!!
Squirm
06-15-2003, 04:32 PM
If the DLL was created with VB then it is almost certainly an ActiveX DLL, in which case it will need to be installed and registered on the target machine before your application will run. All VB programs have a number of dependencies by default, so we use things like the Package and Deployment Wizard or INNO Setup (www.innosetup.com) to create install packages.
J-Man
06-15-2003, 04:59 PM
If the DLL was created with VB then it is almost certainly an ActiveX DLL, in which case it will need to be installed and registered on the target machine before your application will run. All VB programs have a number of dependencies by default, so we use things like the Package and Deployment Wizard or INNO Setup (www.innosetup.com) to create install packages.
Which is simpler to use...and most professional looking:
Package and Deployment Wizard
OR
INNO Setup
Thanks much!
Squirm
06-15-2003, 05:56 PM
I got hooked on INNO while using VB5, because the P&DW then was really quite poor. I know it's much improved in VB6, but I still stick with INNO. Its slightly trickier to use since it uses install scripts rather than a visual wizard interface. However, it is much more flexible and powerful than the P&DW alone.
:)
J-Man
06-15-2003, 06:04 PM
I looked at INNO and it looks kind of complicated to use when deploying a VB application. Is it as difficult to use as it looks? What steps do you go through to deploy a VB application with INNO?