dll error
-
I'm starting a service that is dependent on a dll. On doing so I get the below error The procedure entry point XXXX could not be located in the dynamic link library LLLL.dll The service and other related binaries are the release binaries while the dll that is copied is a debug one. I have also copied all the debug dependent dlls in the folder without avail. Should the dll be also release to solve this problem.
-
I'm starting a service that is dependent on a dll. On doing so I get the below error The procedure entry point XXXX could not be located in the dynamic link library LLLL.dll The service and other related binaries are the release binaries while the dll that is copied is a debug one. I have also copied all the debug dependent dlls in the folder without avail. Should the dll be also release to solve this problem.
the only way a release build will fix it is if the release build exports different functions than the debug build does. that would be unusual, though not impossible. but, i'd look at the DLL and see if it's actually exporting the missing function or not, first.
-
I'm starting a service that is dependent on a dll. On doing so I get the below error The procedure entry point XXXX could not be located in the dynamic link library LLLL.dll The service and other related binaries are the release binaries while the dll that is copied is a debug one. I have also copied all the debug dependent dlls in the folder without avail. Should the dll be also release to solve this problem.
Visual C 6 comes with a handy program called depends.exe. Use it and look at your executable, and it will look at dlls it depends on, and give you nice red exclamation makrs if there are problems. I'd be shocked if later versions didn't come with an equivalent tool. I'd be surprised if they didn't come with the *same* tool. It works rather well. Iain.
-
I'm starting a service that is dependent on a dll. On doing so I get the below error The procedure entry point XXXX could not be located in the dynamic link library LLLL.dll The service and other related binaries are the release binaries while the dll that is copied is a debug one. I have also copied all the debug dependent dlls in the folder without avail. Should the dll be also release to solve this problem.
If your DLL is using the debug version(s) of MFC and/or the CRT while the other modules use the release version(s), you may have a problem there as well. Mark
Mark Salsbery Microsoft MVP - Visual C++ :java:
-
Visual C 6 comes with a handy program called depends.exe. Use it and look at your executable, and it will look at dlls it depends on, and give you nice red exclamation makrs if there are problems. I'd be shocked if later versions didn't come with an equivalent tool. I'd be surprised if they didn't come with the *same* tool. It works rather well. Iain.
Iain Clarke wrote:
I'd be shocked if later versions didn't come with an equivalent tool.
Through 2005 it does. Although there is no Start menu entry for it and it's buried in folder structure under Program Files so using a Search is about the only way to find it. :-D
led mike