For the most part, many SDKs come with their own documentation.  That will
probably be your first source of information.

Hi,
Welcome to MSDN Newsgroup!

Header files contain many prototypes of function, macro and so on. If we
omit some relevant header files, the complier will report compile error,
just like undeclared identifier error. You could use "#include headerfile"
direction to add header files.
Lib and Dll contain the implementation of function. When we call a function
whose code is not in our program itself, such as any Windows API, we need
to tell the linker where the function is so it can store information about
the function in your EXE. This is done with an import library. An import
library is a LIB file that contains the list of functions exported from its
corresponding DLL. For example, kernel32.lib contains the exports for
kernel32.dll. When Windows loads your EXE, it reads this information, loads
the correct DLL, and resolves the function calls. The VC AppWizard creates
projects with the most commonly-used LIBs (such as kernel32.lib,
user32.lib, etc.) already listed in the linker options, but if we use call
APIs in other DLLs, we'll need to add the corresponding LIB files.
Let's take for example the API PathAddBackslash(). When you get an
unresolved external error on this API, you need to find out which LIB file
its definition is contained in. Read the MSDN page on PathAddBackslash(),
and at the bottom you'll see: "Import Library: Shlwapi.lib". That tells you
that you must add shlwapi.lib to your linker options. To add import
libraries to the linker options, click Project->Settings and go to the Link
tab. Set the Category combo box to General, then add the LIB filenames in
the Object/library modules edit box.

I hope the above information is helpful for you. If you have any questions,
please feel free to let me know. Thanks and have a nice day!

Best Regards,

Terry Fei [MSFT]
Microsoft Community Support
Get Secure! www.microsoft.com/security

--------------------