Click here to Skip to main content
15,894,179 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
I am attempting to use a 3rd party API for interfacing with a digital camera.
The camera is from FLIR -- a Blackfly-S 12MP digital camera.
Their API is called Spinnaker and is accessed through a .dll.

They provide example code that is compiled using Visual Studio 2015 with target platform x64 and Target Framework 4.5. The x64 .dll is placed in the .exe folder.
On an Alienware laptop running Windows 10 and VS 2017, the example code runs fine.
The example code compiles and runs w/o error with the connected camera hardware.
However, when I move the identical VS code (.sln) to another PC running Windows 10 and VS 2017 the code compiles w/o error BUT the .dll will not load -- with message "Cant find the .dll or dependencies". The .dll is placed in the .exe folder in both cases.

On the Alienware laptop, when I open the example applications, the project properties/Application/Target Framework/
I see options that include 4.5, 4.51, 4.51, 4.6, 4.61, 4.62 ... but not higher.
The Alienware is an older machine and the VS there was updated over the years to the later versions of VS.

On the NUC, the VS 2017 was installed very recently and the Target Frameworks dropdown options are only .net Core selections for any new application.
However, the code .sln that I move from the Alienware to the NUC, the Framework 4.5 is selected and the code compiles successfully on the NUC.
But not will not run because of the .dll.
If I attempt to load the .net framework 4.5, 4.51, 4.52 onto the NUC PC, the download wont allow this saying I already have a higher framework.

Any assistance will be appreciated.
Jim<

What I have tried:

Modifying the framework on the NUC
Moving only the .exe from the Alienware to the NUC (same .dll error)
Posted
Updated 24-Jun-19 4:10am

1 solution

One usually sets a "reference" to a particular dll in the solution; the "reference's" "properties" then show "where" the dll is being referenced from.

You made no "reference" to a reference; just that you're moving files around.

"Copying a solution" will NOT copy files that are referenced "outside" of the solution.

You should check the "reference" for the dll in the copy to see where it's pointing.

If you're dynamically loading dll's, then your "pathing" is off.
 
Share this answer
 

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900