Does anyone have a good API reference?

[Das Mad]

Does anyone have a good API reference?

I would prefer if it's for VB
With examples not like the one that comes with Visual Studio (API Text Viewer)

I'am trying to make a include file 4 asm with the most common API functions

Please add a URL

[oetje]

http://www.vbapi.com
http://www.allapi.net

[oetje]

For all api's, check out http://msdn.microsoft.com.

[Das Mad]

Thanks I will check em' out

Oetje: Actually they do not list all API's, however, it does list most of them.

Das Mad: After you go to the MSDN site, go to Platform SDK for all the API's.

[DanR]

There can be only one...

My longtime favorite is "Visual Basic Programmers's Guide to the Win32 API" by Dan Appleman. SAMS ISBN 0-672-31590-4.

Don't leave your code without it.

Enough of the cliches... One of the things I really like about Mr. Appleman's book is that it clearly states if a given API call is going to cause you any problems when you call it from VB (and usually gives you a method to work around the problem). It also gives you a good set of instructions and methodologies on how to interface with future API's as you encounter them.

My only beef? Like many books that lists constants used. It names the constant and the usage but doesn't give you the value of the constant. Unless you happen to have C++ installed (so that you can get the values form the header files), you will be poking around the internet looking for instancess where some other programmer had the same problem and was good enough to list the constants with thier code. In my case, I'm calling the Win32 registry API routines. As a twist, I'm calling them from a VB4 16-bit autorun program via thunking routines. No bult-in API constants here...

[gabriel.hege]

DanR: You wrote that the problem with the book would be that it doesn't list the constant's values. Can't you just tell Visual Basic to print out that constant's value? Kind of like:

debug.print NAME_OF_CONSTANT

or do I misunderstand your problem?


Gabriel

[DanR]

This really only affects me personally.

If I was working in VB6 I could. In my case I'm in VB4 16-bit using thunking to get to some 32-bit API routines. VB4 16-bit has no idea what the 32-bit API constants are.

[PaulLewis]

DanA's book is tops.

Personally I don't like the "old style" naming convention but I agree with his reasons for using them.

Even in VB6 you don't get all the constants. But I happen to also have MSDN and all the SDK's etc so I get around it that way on the rare occasion it happens.

Regards