Prev: Suggection on Image box
Next: Windows must be restarted after Pgm installed
From: Dennis Rose on 9 Feb 2010 13:44
In the VB5 setup wizard, it lists 3 files with Out of date Dependencies,
comdlg32.ocx, crystl32.ocx and comctl32.ocx. I have read about this in
Google, but still have the following question using the "Comctl32.ocx"
component(as an example) which is out of date.

In Windows/System32, the OCX has a version of 6.0.81.5 but the dependency
file for this ocx has a version of 6.0.80.22 listed. Since this a MS
component, how do I know if there are new depencencies or if I just need to
change the version number in the existing DEP file for this component?? Dep
code shown below:

; Dependency file for setup wizards.

[Version]
Version=6.0.80.22

; Dependencies for ComCtl32.ocx

; Default Dependencies ----------------------------------------------

[ComCtl32.ocx]
Dest=$(WinSysPath)
Register=$(DLLSelfRegister)
Version=6.0.80.22
Uses1=ComCat.dll
Uses2=
CABFileName=ComCtl32.cab
CABDefaultURL=http://activex.microsoft.com/controls/vb6
CABINFFile=ComCtl32.inf

[ComCat.dll]
Dest=$(WinSysPathSysFile)
Register=$(DLLSelfRegister)
Uses1=
From: Ralph on 9 Feb 2010 14:15

"Dennis Rose" <DennisRose(a)discussions.microsoft.com> wrote in message
news:C3DD8A93-9932-442C-A83A-69801B8EEEB3(a)microsoft.com...
> In the VB5 setup wizard, it lists 3 files with Out of date Dependencies,
> comdlg32.ocx, crystl32.ocx and comctl32.ocx. I have read about this in
> Google, but still have the following question using the "Comctl32.ocx"
> component(as an example) which is out of date.
>
> In Windows/System32, the OCX has a version of 6.0.81.5 but the dependency
> file for this ocx has a version of 6.0.80.22 listed. Since this a MS
> component, how do I know if there are new depencencies or if I just need
to
> change the version number in the existing DEP file for this component??
Dep
> code shown below:
>
<snipped>

..DEP files are only used by a few MS Utilities and only to provide
'packages'. Today mostly by just P&D. You can update the .dep file manually,
or you can simply run the P&D wizard against a component to create a new
..DEP file. You can also simply ignore the warning as it is highly unlikely
you want to include the components these components are dependent on in any
package anyway.

-ralph


From: Paul Clement on 10 Feb 2010 10:05
On Tue, 9 Feb 2010 10:44:06 -0800, Dennis Rose <DennisRose(a)discussions.microsoft.com> wrote:

� In the VB5 setup wizard, it lists 3 files with Out of date Dependencies,
� comdlg32.ocx, crystl32.ocx and comctl32.ocx. I have read about this in
� Google, but still have the following question using the "Comctl32.ocx"
� component(as an example) which is out of date.
�
� In Windows/System32, the OCX has a version of 6.0.81.5 but the dependency
� file for this ocx has a version of 6.0.80.22 listed. Since this a MS
� component, how do I know if there are new depencencies or if I just need to
� change the version number in the existing DEP file for this component?? Dep
� code shown below:
�
� ; Dependency file for setup wizards.
�
� [Version]
� Version=6.0.80.22
�
� ; Dependencies for ComCtl32.ocx
�
� ; Default Dependencies ----------------------------------------------
�
� [ComCtl32.ocx]
� Dest=$(WinSysPath)
� Register=$(DLLSelfRegister)
� Version=6.0.80.22
� Uses1=ComCat.dll
� Uses2=
� CABFileName=ComCtl32.cab
� CABDefaultURL=http://activex.microsoft.com/controls/vb6
� CABINFFile=ComCtl32.inf
�
� [ComCat.dll]
� Dest=$(WinSysPathSysFile)
� Register=$(DLLSelfRegister)
� Uses1=

I would still recommend switching to Inno Setup:

http://www.jrsoftware.org/isinfo.php

If you do happen to use the VB 5.0 Setup Wizard make sure not to deploy any system files (such as
ComCat.dll).


Paul
~~~~
Microsoft MVP (Visual Basic)
 | 
Pages: 1
Prev: Suggection on Image box
Next: Windows must be restarted after Pgm installed