none
Interop: When, why and how to use functions' unicode names? RRS feed

  • Question

  • There are some functions with unicode names, for example SetWindowsHookExW for SetWindowsHookEx, and UnhookWindowsHookExW for UnhookWindowsHookEx.

    As general knowledge I choose to use unicode names since I think they are designed for future uses, but when calling some of them are causing exceptions for example:

    Unable to find an entry point named 'UnhookWindowsHookExW' in DLL 'user32'.

    When, why and how to use functions' unicode names?


    Do my best in .Net learning.
    Thursday, May 6, 2010 12:51 PM

Answers

All replies