Prev: What Does it Mean Microsoft No Longer Supports VB?
Next: Need VB5 code to interface with vbSendMail.dll
From: chris on 26 Jan 2010 10:05
Hi,

is there any way I can delete and add a file (replace) in CAB file created
by Package & Deployment Wizard of VB6, in order not to create SETUP files
again ? It seems that CAB file is locked.

The DLL I need to replace will not create any problem to the rest of files,
it just includes a corrected bug.

Thanks a lot in advance.
From: mayayana on 26 Jan 2010 10:42

> is there any way I can delete and add a file (replace) in CAB file created
> by Package & Deployment Wizard of VB6, in order not to create SETUP files
> again ? It seems that CAB file is locked.
>
There are a couple of ways. You can use software that
rebuilds the CAB, but CABs store files in sequence, and
I think the setup.lst file depends on that sequence with
its file numbering. So you need to be sure to get the same
sequence.

Another, probably easier, method is to use the provided,
but poorly documented, features of PDW itself: Look in the folder
where the package was made. You should have setup.exe,
setup.lst, the CAB, and a folder named Support.

That folder holds copies of all your
files. There's a .DDF file in there that specifies the CAB
content. There's also a .BAT file that will rebuild the CAB,
based on the DDF file, and using the files in the Support folder.
(You can alter the CAB by editing the DDF file, if necessary.)

So you put the new DLL in the Support folder and run
the BAT file. But before you run the BAT you also need
to edit the setup.lst file with the new size/date/version for the
replaced DLL. You can do that in Notepad. Then put the
updated file in the Support folder. (Also copy it outside the
Support folder. I don't remember offhand whether the BAT
file ops will replace that version of setup.lst with the version
in the Support folder, and the version outside is the one that
ends up getting shipped.)

After the BAT runs you'll have an updated CAB file outside
the Support folder.

> The DLL I need to replace will not create any problem to the rest of
files,
> it just includes a corrected bug.
>
> Thanks a lot in advance.


From: CY on 26 Jan 2010 10:43
Hmm, the easy way should be to add it to the project, and rerun P&DW,
isnt there a .bat file for that already?
or for a runaround replace the dll afterwords, and NO, I havent tried
playing with the CAB so I dont know, it opens in sorts of packing
programs but there is a sid key too. some {alto-or-numbers-here}
stuff.
Why dont do it the right way?
//CY

On 26 Jan, 16:05, chris <ch...(a)discussions.microsoft.com> wrote:
> Hi,
>
> is there any way I can delete and add a file (replace) in CAB file created
> by Package & Deployment Wizard of VB6, in order not to create SETUP files
> again ? It seems that CAB file is locked.
>
> The DLL I need to replace will not create any problem to the rest of files,
> it just includes a corrected bug.
>
> Thanks a lot in advance.

From: Ralph on 26 Jan 2010 14:45
chris wrote:
> Hi,
>
> is there any way I can delete and add a file (replace) in CAB file
> created by Package & Deployment Wizard of VB6, in order not to create
> SETUP files again ? It seems that CAB file is locked.
>
> The DLL I need to replace will not create any problem to the rest of
> files, it just includes a corrected bug.
>

To add to the pile.

When you create a specific build you are given an opportunity to name and
save that build-script. You can then use the command line options for PDMan
to rebuild your project non-interactively and silently. (Take a close look
at what the .bat file is doing as well.) I find this just as easily done as
running the bat file.

[The next step is to place all of this in an .mak file (nmake). <g>]

-ralph


 | 
Pages: 1
Prev: What Does it Mean Microsoft No Longer Supports VB?
Next: Need VB5 code to interface with vbSendMail.dll