I too had problems around EX9_16lib.dll. finally resolved it by putting a copy of EX9_16lib.dll in both the source folder and the debug folder. The debug folder gave a problem, as I have two. I am using Visual Studio 2005 in its default state. Hence it appears to create a hierarchy of project files. For example: If I create a new project EX9_16, I get:
-EX9_16
EX9_16
Once I start debugging, I get:
-EX9_16
-EX9_16
Debug
and once compiled (I think; maybe earlier)
-EX9_16
Debug
-EX9_16
Debug
My initial problems came about by putting the dll in the third level down debug; wrong one. I needed it in the second level debug, where the exe is -and a copy in the second level down EX9_16 folder in order to compile.
(The hierarchy maybe a problem of my own making; perhaps I will find out as I proceed.)
I hope that this helps others.
(Edit later: I think my directory confusion comes about because the top level is the solution folder and the second level, above, is the project folder. Confusion arises as both have the same names.)
|