This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(297.6, 64%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EF%3C/text%3E%3C/svg%3E)
For a VC++ project, is there a way to setup a path to load a dll from another path than the current project it is ?
For instance, I have a project, Test, which generate Test.exe. The current path is C:\Project\Test\Debug\Test.exe
The question is, how can I setup in my current project, Test, another path in such a way, to load (at rutime of course) another dll, let say, Customer.dll, from C:\Project\Customer\Debug\Customer.dll ?
I suggest your review this documentation since there are various ways to make a dll available for runtime loading.
dynamic-link-library-search-order
For example, one way would be to configure your project properties so that the working directory when running your executable is the directory containing the dll that you want to load.
No, the C:\Project\Test\Debug\Test.exe path should be different from C:\Project\Customer\Debug\Customer.dll path.
I know I could migrate the dll into my Test.exe path (programmatically or not), but the request is to not to do that.
I assume that your issue really refers to successfully loading a dll from an alternate path when your executable is first loaded by Windows.
I'm not sure I understand your comment so following are examples of two different ways to configure the Test project properties so that the Customer dll can be loaded when Test.exe is executed. In each case Test.exe is referred to by the default built-in Visual Studio macro $(TargetPath).
Alternative 1 -- Visual Studio sets working directory when executing Test.exe
Alternative 2 -- Visual Studio adds path to Customer. dll to path environment variable for Test.exe process
These settings only affect the project's runtime environment within Visual Studio. Of course they would need to be set properly for the various platform/configuration settings.
In my opinion the benefit of these alternatives is they are used by Visual Studio and do not otherwise impact the code for Test.exe or its linker options beyond what would ordinarily be needed to reference the Customer.dll import library.
Yes, I have found the issue: I need to load from PATH some directory in VC++ Directories, and it didn't load it because I should restart Visual Studio Environment to re-load new path from PATH (system PATH). And I was searching for other methods to load that dll from another path than the current project directory, but it has been solved.
Anyway, I learnt a lot within these posts, so, I kindly thank you, all of you. I accept the answer the first one, but I it could be accepted any of them as answer.