Hi,
this is the list of DLL/OCX files that my application needs and their
versionthat I have:
COMCAT.DLL, Version 4.71.1460.1
stdole2.tlb, Version 2.40.4275.1
asycfilt.dll, Version 2.40.4275.1
olepro32.dll, Version 5.0.4275.1
oleaut32.dll, Version 2.40.4275.1
msvbvm60.dll, Version 6.0.9782
mscomct2.ocx, Version 6.1.97.82
comdlg32.ocx, Version 6.1.97.82
mscomctl.ocx, Version 6.1.97.86
QTOControl.dll, Version 7.1.0.210
winhttp.dll, Version 5.1.2600.1557
QTOLibrary.dll, Version 7.1.0.210
msvcrt.dll, Version 6.0.9782.0
scrrun.dll, Version 5.6.0.6626
Thanks,
Dee
dee - 31 Jul 2006 22:20 GMT
Hi,
Since I made my application in Visual Basic 6 SP6, I need to include
visual basic 6 runtime files with my installation package. I used PDW
to determine the files that my applicatin needs. I also downloaded the
vbrun60sp6.exe from Microsoft and extracted VB runtime files to a
folder using vbrun60sp6.exe /c /t:c:\vbfiles at command line.
My question is when I was comparing the version of files installed on
my system and the version of files extracted into folder from
vbrun60sp6.exe, I found that the extracted files were an older version.
Which files should I include in my setup package?
Also I have heard people recommend that I should create my setup
package on lowest OS version supported by my application and include
its dlls in my setup package so that there are min chances of replacing
the dlls already present on user's system. What would be a better
approach. I am concerned because my application is going to be
distributed to a huge number of customers who most likely will not have
visual basic installed on their system. Please advise me.
Thanks,
Dee