extern "C" __declspec(dllexport) int LOGON_LogOn(void);
我的方法:
VB6不能使用相對路徑來呼叫。。。
so我用了LoadLibrary
代碼如下:
Private Declare Function FreeLibrary Lib "kernel32" (ByVal hLibModule As Long) As Long
Private Declare Function LoadLibrary Lib "kernel32" Alias "LoadLibraryA" (ByVal lpLibFileName As String) As Long
Private Declare Function GetProcAddress Lib "kernel32" (ByVal hModule As Long, ByVal lpProcName As String) As Long
Private Declare Function CallWindowProc Lib "user32" Alias "CallWindowProcA" (ByVal lpPrevWndFunc As Long, ByVal hWnd As Long, ByVal Msg As Any, ByVal wParam As Any, ByVal lParam As Any) As Long
Private Sub Form_Load()
On Error Resume Next
Dim lb As Long, pa As Long
Lb = LoadLibrary("LogOn.dll")
pa = GetProcAddress(lb, "LOGON_LogOn")
CallWindowProc GetProcAddress(lb, "LOGON_LogOn"), Me.hWnd, 0, 0, 0
FreeLibrary lb
End Sub
我就是不想使用這個,我想把dll和組態檔,exe等放在一個檔案夾下,這樣在其他機器上使用時直接拷貝過去就可以了。
如果直接顯式呼叫,Private Declare Function
我怎么還會這么煩呢。。
uj5u.com熱心網友回復:
確實不行啊,或者你給我段代碼參考一下?
Private Declare Function LOGON_LogOn Lib "LogOn" () As Long
Private Declare Function LOGON_LogOn Lib ".\LogOn" () As Long
Private Declare Function LOGON_LogOn Lib "\LogOn" () As Long
都不行,
必須是絕對路徑
'在 Microsoft Windows(16 位)中:
Declare Sub MessageBeep Lib "User" (ByVal N As Integer)
'假設 SomeBeep 是該程序名的別名。
Declare Sub MessageBeep Lib "User" Alias "SomeBeep"(ByVal N As Integer)
'在 Alias 子句使用順序號來呼叫 GetWinFlags。
Declare Function GetWinFlags Lib "Kernel" Alias "#132"() As Long
'在 32 位 Microsoft Windows 系統中,指定的庫應是 USER32.DLL,
'而不是 USER.DLL。可以使用條件編譯來撰寫
'既可在 Win32 又可在 Win16 環境運行的代碼。
#If Win32 Then
Declare Sub MessageBeep Lib "User32" (ByVal N As Long)
#Else
Declare Sub MessageBeep Lib "User" (ByVal N As Integer)
#End If
至于 VB 提供的 Windows 路徑,Windows System 路徑, Visual Basic 路徑,都時一些附送的便利。此外,微軟認為你使用的 DLL 可能是公用的,放在系統路徑中,當你卸載程式時,DLL 仍會保留。
uj5u.com熱心網友回復:
LoadLibrary
The LoadLibrary function maps the specified executable module into the address space of the calling process.
HINSTANCE LoadLibrary(
LPCTSTR lpLibFileName // address of filename of executable module
);
Parameters
lpLibFileName
Pointer to a null-terminated string that names the executable module (either a .DLL or .EXE file). The name specified is the filename of the module and is not related to the name stored in the library module itself, as specified by the LIBRARY keyword in the module-definition (.DEF) file.
If the string specifies a path but the file does not exist in the specified directory, the function fails. When specifying a path, be sure to use backslashes (\), not forward slashes (/).
If the string does not specify a path, the function uses a standard search strategy to find the file. See the Remarks for more information.
Return Values
If the function succeeds, the return value is a handle to the module.
If the function fails, the return value is NULL. To get extended error information, call GetLastError.
Remarks
LoadLibrary can be used to map a DLL module and return a handle that can be used in GetProcAddress to get the address of a DLL function. LoadLibrary can also be used to map other executable modules. For example, the function can specify an .EXE file to get a handle that can be used inFindResource orLoadResource. Do not use LoadLibrary to "run" a .EXE file.
If the module is a DLL not already mapped for the calling process, the system calls the DLL's DllMain function with the DLL_PROCESS_ATTACH value. If the DLL's entry-point function does not return TRUE, LoadLibrary fails and returns NULL.
It is not safe to call LoadLibrary from DllMain. For more information, see the Remarks section in DllMain.
Module handles are not global or inheritable. A call to LoadLibrary by one process does not produce a handle that another process can use — for example, in calling GetProcAddress. The other process must make its own call to LoadLibrary for the module before calling GetProcAddress.
If no filename extension is specified in the lpLibFileName parameter, the default library extension .DLL is appended. However, the filename string can include a trailing point character (.) to indicate that the module name has no extension. When no path is specified, the function searches for loaded modules whose base name matches the base name of the module to be loaded. If the name matches, the load succeeds. Otherwise, the function searches for the file in the following sequence:
The directory from which the application loaded.
The current directory.
Windows 95 and Windows 98: The Windows system directory. Use theGetSystemDirectory function to get the path of this directory.
Windows NT: The 32-bit Windows system directory. Use the GetSystemDirectory function to get the path of this directory. The name of this directory is SYSTEM32.
Windows NT: The 16-bit Windows system directory. There is no function that obtains the path of this directory, but it is searched. The name of this directory is SYSTEM.
The Windows directory. Use theGetWindowsDirectory function to get the path of this directory.
The directories that are listed in the PATH environment variable.
The first directory searched is the one directory containing the image file used to create the calling process (for more information, see the CreateProcess function). Doing this allows private dynamic-link library (DLL) files associated with a process to be found without adding the process's installed directory to the PATH environment variable.
The Visual C++ compiler supports a syntax that enables you to declare thread-local variables: _declspec(thread). If you use this syntax in a DLL, you will not be able to load the DLL explicitly using LoadLibrary or LoadLibraryEx. If your DLL will be loaded explicitly, you must use the thread local storage functions instead of _declspec(thread).
Windows 95: If you are using LoadLibrary to load a module that contains a resource whose numeric identifier is greater than 0x7FFF, LoadLibrary fails.
Windows CE: Two different modules cannot have the same filename, given that the extensions are different. These effectively have the same "module" name. For example, if LoadLibrary is made on "Sample.cpl", the operating system will not load Sample.cpl, but instead will again load Sample.dll. A similar limitation exists for modules with the same name but residing in different directories. For example, if LoadLibrary is called on "\\Windows\Sample.dll", and then LoadLibrary is called on "\\MyDir\Sample.dll", "\\Windows\Sample.dll" will simply be reloaded.
A search path to the executable module cannot be specified. Unless the full path to the module is given, Windows CE will search the following path for the module:
The root directory of the PC Card RAM expansion card, if one exists.
The windows directory (\Windows).
The root directory (\).
QuickInfo
Windows NT: Requires version 3.1 or later.
Windows: Requires Windows 95 or later.
Windows CE: Requires version 1.0 or later.
Header: Declared in winbase.h.
Import Library: Use kernel32.lib.
Unicode: Implemented as Unicode and ANSI versions on Windows NT.
See Also
Dynamic-Link Libraries Overview, Dynamic-Link Library Functions, DllMain,FindResource, FreeLibrary, GetProcAddress,GetSystemDirectory,GetWindowsDirectory, LoadLibraryEx,LoadResource