DLLSelfRegister

[gravyboy]

I worked out that there must be a DLLSelfRegister API call in vb6stkit.dll - and luckily guessed at the declaration.

What I'd like to know is is there a way of breaking down or enumerating all the calls in a DLL?

I feel that there must be more that is available . . .

[ruyeno22]

hello:

im trying to see why the instalation of my programs doesn't work
when i try to register manually vb6stkit.dll i get an error.

did it happen to u to???

thanks

[parksie]

Things like DllSelfRegister are thoroughly documented in MSDN. You can get the names of all the functions exported in a DLL using Dependency Walker (or a similar tool). However, the only other information you can get is the number of bytesworth of parameters expected -- the DLL does not contain the parameter list. You'd need some kind of documentation for that.

You may already know this, but just in case This is because when the code is compiled, exported functions are set so that it receives a pointer (memory location) to it's first argument. Subsequent accesses to any parameters are found by addressing an offset off that pointer. Therefore when it's compiled, you lose and data type information