new to vb, we recently rewrote a dll component. we would like to distribute it to users and replace the old dlls. We plan on packaging the dll on a .cab file to floppy disk and then provide the cab file and setup.exe file to users - i hope this is the way of doing this. is there a better way? if so, what would be best way of doing this? any help would be appreciated
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
DLL
- Thread starter sarahjane
- Start date
Make sure the DLL was compiled to be binary compatible with the one it's replacing, otherwise you'll break the existing app that uses it.
If you did have to break compatability, then you'll also have to distribute all modules and programs that depend on your DLL.
Using a setup program is a good way to do this. You get consistency and repeatability. You can use the Package & Deployment Wizard (I give it a B-), or use one of the commerically available setup creators like Wise or InstallShield.
Chip H.
If you did have to break compatability, then you'll also have to distribute all modules and programs that depend on your DLL.
Using a setup program is a good way to do this. You get consistency and repeatability. You can use the Package & Deployment Wizard (I give it a B-), or use one of the commerically available setup creators like Wise or InstallShield.
Chip H.
- Status
Similar threads
