"Little Setup Builder" and Dependency Files

[koala15]

Hello all,

After searching through this forum, "Little Setup Builder" (LSB) has been recommended a number of times as an alternative to the very bland PDW (LSB is also free).

What LSB does not do (unlike PDW), is to automatically include all the depenency files. So I used PDW to generate both a .dep file and also the setup.lst file for my app.

The .dep file is as follows
[blue]
[Version]
Version=0.9.0.2

[testing.exe <0009>]
Dest=$(AppPath)
Date=7/06/2004
Time=10:37
Version=0.9.0.2
CABFilename=
Uses1=MSVBVM60.DLL
Uses2=OLEAUT32.DLL
Uses3=OLEPRO32.DLL
Uses4=ASYCFILT.DLL
Uses5=STDOLE2.TLB
Uses6=COMCAT.DLL
Uses7=dao360.dll
Uses8=scrrun.dll
Uses9=msstdfmt.dll
Uses10=msflxgrd.ocx
Uses11=Hot.ocx
Uses12=mscomct2.ocx
Uses13=mscomctl.ocx
Uses14=TABCTL32.OCX
Uses15=MCI32.OCX
Uses16=comdlg32.ocx

[dao360.dll <0009>]
Dest=$(WinSysPath)
Date=19/06/2003
Time=11:05
Version=3.60.6508.2

[Hot.ocx <0009>]
Dest=$(WinSysPath)
Date=13/07/2003
Time=13:11
Version=4.0.0.0
[/blue]

The "Files" sections of the .lst is as follows:
[blue]
[Bootstrap Files]
File1=@VB6STKIT.DLL,$(WinSysPathSysFile),,,3/26/99 12:00:00 AM,101888,6.0.84.50
File2=@COMCAT.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),,5/31/98 12:00:00 AM,22288,4.71.1460.1
File3=@STDOLE2.TLB,$(WinSysPathSysFile),$(TLBRegister),,6/19/03 11:05:04 AM,16896,2.40.4522.0
File4=@ASYCFILT.DLL,$(WinSysPathSysFile),,,6/19/03 11:05:04 AM,143632,2.40.4522.0
File5=@OLEPRO32.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),,6/19/03 11:05:04 AM,164112,5.0.4522.0
File6=@OLEAUT32.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),,6/19/03 11:05:04 AM,626960,2.40.4522.0
File7=@MSVBVM60.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),,6/19/03 11:05:04 AM,1385744,6.0.96.90


[Setup1 Files]
File1=@comdlg32.ocx,$(WinSysPath),$(DLLSelfRegister),$(Shared),1/21/00 1:14:38 PM,140288,6.0.84.18
File2=@MCI32.OCX,$(WinSysPath),$(DLLSelfRegister),$(Shared),6/24/98 12:00:00 AM,198456,6.0.81.69
File3=@TABCTL32.OCX,$(WinSysPath),$(DLLSelfRegister),$(Shared),6/24/98 12:00:00 AM,209192,6.0.81.69
File4=@mscomctl.ocx,$(WinSysPath),$(DLLSelfRegister),$(Shared),5/22/00 4:58:10 PM,1066176,6.0.88.62
File5=@mscomct2.ocx,$(WinSysPath),$(DLLSelfRegister),$(Shared),1/21/00 1:14:38 PM,645616,6.0.84.18
File6=@Hot.ocx,$(WinSysPath),$(DLLSelfRegister),$(Shared),7/13/03 1:11:30 PM,123517,4.0.0.0
File7=@msflxgrd.ocx,$(WinSysPath),$(DLLSelfRegister),$(Shared),1/21/00 1:14:36 PM,244232,6.0.84.18
File8=@msstdfmt.dll,$(WinSysPath),$(DLLSelfRegister),$(Shared),6/6/01 4:51:37 AM,118784,6.0.88.4
File9=@msvcrt.dll,$(WinSysPathSysFile),,,6/19/03 11:05:04 AM,286773,6.1.9844.0
File10=@scrrun.dll,$(WinSysPath),$(DLLSelfRegister),$(Shared),6/26/01 3:39:42 PM,151601,5.6.0.6626
File11=@dao360.dll,$(WinSysPath),$(DLLSelfRegister),$(Shared),6/19/03 11:05:04 AM,561424,3.60.6508.2
File12=@testing.exe,$(AppPath),,,6/7/04 10:37:22 AM,2220032,0.9.0.2
[/blue]

On reading the doco from MS (namely MSDN article 178354), it seems that according to the .dep file none of the dependency files need to be registered BUT the .lst file says that nearly all need to be "self registered".

Am I reading this correctly or does the $(DLLSelfRegister) just mean that it is capable of self registration?

Also, am I correct in assuming that only the files mentioned in the .dep file are dependency files. For example, "msvcrt.dll" is mentioned (file 9) in the .lst but not in the .dep - is msvcrt.dll a dependent file and therefore needs to be included in the LSB package?

Then again may be I just do not understand.

Any help would be appreciated.

Thank you.

&quot;Life is full of learning, and then there is wisdom&quot;