DLLImport

Waseem

Hi,
I have been experimenting with using DLL Import on user32.dll and kernel32.dll I have successfully put together my own way of working with the MessageBox as an experiment to learning the DLLs.

Could you enlighten me on what I could do or what advantages I could gain by working with such DLLs ?

also I would like to know what other DLLs I can work with.

NOTE:
Using C# 4.0

4 Replies

Know the answer? Post it — somebody with the same question will find it here.

Sam Hobbs14y ago
Accepted answer
I am only saying to not use DllImport if there is a more flexible way of doing the same thing. DllImport is good and necessary for everything that it must be used for.

An example of something that Windows does that is not part of .Net is functions that work with windows in other processes. For example you cannot use .Net to enumerate all windows (EnumWindows function) in a system.
Waseem14y ago
I see, Thank you
Waseem14y ago
Thank you, so from your experience / advice, it's best to avoid DLL Importing as much as possible ?
Sam Hobbs14y ago
You can use any DLL of many DLLs that are regular DLLs. There are very many types of DLLs and many of them are not regular DLLs. A .Net Library is not a regular DLL and neiher is a COM object DLL. Most of the most useful Windows functions have a .Net Class Library wrapper and those should be used when available. If a .Net Class Library is not available then a COM object should be used if available. There are some parts of Windows that are useful that do not have a .Net Class Library or a COM object wrapper so use of those functions require use of DllImport.