Dll pacement
-
HI, Is there any restriction that Dll should be in the same folder with Client exe or system folder ? Can i place DLL any where and can Call ? waiting for your precious advice. Thanks, Rayalu
-
HI, Is there any restriction that Dll should be in the same folder with Client exe or system folder ? Can i place DLL any where and can Call ? waiting for your precious advice. Thanks, Rayalu
See "Dynamic-Link Library Search Order" at
MSDN. :)If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke
[My articles] -
HI, Is there any restriction that Dll should be in the same folder with Client exe or system folder ? Can i place DLL any where and can Call ? waiting for your precious advice. Thanks, Rayalu
Your dll has to be found by your application, which means that it should either be in the system folder or in the same folder of your application. However, if you explicitely load your dll (by using LoadLibrary), you can place it anywhere you want and specify the path of the dll in the call to LoadLibrary.
Cédric Moonen Software developer
Charting control [v3.0] OpenGL game tutorial in C++ -
Your dll has to be found by your application, which means that it should either be in the system folder or in the same folder of your application. However, if you explicitely load your dll (by using LoadLibrary), you can place it anywhere you want and specify the path of the dll in the call to LoadLibrary.
Cédric Moonen Software developer
Charting control [v3.0] OpenGL game tutorial in C++Cedric Moonen wrote:
However, if you explicitely load your dll (by using LoadLibrary), you can place it anywhere you want and specify the path of the dll in the call to LoadLibrary.
I think you may do the same thing with implicit loaded DLLs if you specify the path of the dynamic libraries in the application mainifest (anyway I never made a test...). :)
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke
[My articles] -
Cedric Moonen wrote:
However, if you explicitely load your dll (by using LoadLibrary), you can place it anywhere you want and specify the path of the dll in the call to LoadLibrary.
I think you may do the same thing with implicit loaded DLLs if you specify the path of the dynamic libraries in the application mainifest (anyway I never made a test...). :)
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke
[My articles] -
Your dll has to be found by your application, which means that it should either be in the system folder or in the same folder of your application. However, if you explicitely load your dll (by using LoadLibrary), you can place it anywhere you want and specify the path of the dll in the call to LoadLibrary.
Cédric Moonen Software developer
Charting control [v3.0] OpenGL game tutorial in C++Thanks Cédric Moonen I did same.
-
It also works implicit if you specify the path. I used it to reference to the debug or release version of some dll I wrote, depending on some project setting.
Greetings Covean
You can also use SetDllDirectory[^] to add a search path to locate the DLL.
«_Superman_» I love work. It gives me something to do between weekends.
Microsoft MVP (Visual C++)
