>I was just wondering...
>How does one go about determining what functions are in a dll?
You can extract the named entrypoints from the .DLL programmatically, but all that tells you is what the names published by the DLL are. If the .DLL publishes COM servers, it contains the type library data and you can view that with tools like OLEView or the VB Object Browser.
>Also how does one determine what parameters etc.. to pass to the above functions?
The documentation for the particular .DLL - the published Microsoft SDK APIs are in the MSDN Library documentation, but that doesn't help with other .DLLs, and the MSDN is not organized .DLL by .DLL; there's no standard document containing all the entrypoints, parameters and uses of all the DLLs ever created by anyone.
>
>Also, a good source of info on DLL's would be apreciated.
>
If you're looking ofr details on the Win32 API, there are a couple of entries in the UT FAQ on general topics. If you know C, I like the
Windows NT Win32 API SuperBible, and Dan Appleman's
Visual Basic Programmer's Guide to the WIn32 API is an excellent reference. As mentioned previously, the MSDN Library is the canonical reference to the WIndows SDKs, but it's a reference, not a teaching guide.
