Hey guys I am not too famalier with the packwage deployment wiz that Vb 6 has, but can it find all the dependcy files that my .exe file needs?
It also needs a database file and a .wav file, but will the package deployment wizard find it?
thanks!
Printable View
Hey guys I am not too famalier with the packwage deployment wiz that Vb 6 has, but can it find all the dependcy files that my .exe file needs?
It also needs a database file and a .wav file, but will the package deployment wizard find it?
thanks!
The PDW basically begins with a set of base dependencies (the setup kit and the VB6 runtime components). Then it scans your Project (VBP) file for added references (both those added as "References" and "Components" via the IDE) and adds those. Then for each of those it looks for a DEP file, which is supposed to be provided along with and COM library you might add, and it adds anything that a DEP file lists. Then it looks for DEPs for each of those, etc.
If along the way it finds MDAC components it should instead include the MDAC_TYP package instead of individual MDAC libraries.
It will give you a chance to "knock out" some of these, because many may be system components that should not be resitributed. PDW also has a few other "cheat sheets" it looks to to determine what should not be distributed.
PDW knows nothing about your program's data or media files. It gives you the chance to add them to the package on one of its user interface panels though, and to specify where you want them deployed on target systems.
Nothing will find the extra files you add for your app to work. PDW will find some dependencies but most are out dated and wrong in what you need to deploy. It's whole concept was based on Windows 98 deployment and lots of things have changed since then.