Fog Creek Software
g
Discussion Board




The site that told you the purpose of a DLL

Sorry for this question, but guys I have searched Google but to no avail.

Where's that site wherein you typed a dll file name and it told you the purpose of the dll?

You are free to delete this thread if it is just too annoying.

Sathyaish Chakravarthy
Friday, January 9, 2004

Maybe you mean this site for Microsoft DLLs:
http://support.microsoft.com/servicedesks/fileversion/default.asp

This database contains information about DLL files that ship with selected Microsoft products. DLL Help exists to assist developers, system administrators, and other IT professionals who face file version conflicts with Microsoft software. Use DLL Help to identify which software installed a specific version of a DLL.

Philip Dickerson
Friday, January 9, 2004

Yup! Thanks, that's the one.

Sathyaish Chakravarthy
Friday, January 9, 2004

Nice, but incomplete database.

For instance, comct232.ocx ships in version 6.0.81.77 with VB6 (Not absolutely positive, but I think it doesn't come with a SP), but this site stops are release 6.0.80.22, which, unlike that newer version, doesn't contain the month/date picker object and the flat scroll object.

Frederic Faure
Friday, January 9, 2004

The control comct232.ocx does stop at version 6.0.80.22, as shown at the Microsoft site.

The date picker (DTPicker) and flat scroll bar are actually in the control mscomct2.ocx, and the Microsft site lists the following versions for that control:
mscomct2.ocx    6.0.88.4
mscomct2.ocx    6.0.84.18
mscomct2.ocx    6.0.81.77
mscomct2.ocx    6.0.81.40

Version 6.0.81.77 of this control was provided with Visual Basic 6.0 (no service pack). The latest version (6.0.88.4) was provided in SP4 for Visual Studio.

Philip Dickerson
Friday, January 9, 2004

Mmm... To find out which controls the various standard OCXs contained, I registered/unregistered each in turn. Could it be that comct323 works in pair with mscomct2?

BTW, since it's also on my to-do list : What is the consequence of moving to plain VB6 to VB6SP4? Do I need to distribute the updated controls to our customers, or will the apps compiled with our updated VB6 work with legacy controls?

Frederic Faure
Friday, January 9, 2004

*  Recent Topics

*  Fog Creek Home