Link to home
Start Free TrialLog in
Avatar of nicoleheritage
nicoleheritage

asked on

The procedure entry point could not be located in the dll

I just removed a function GeographicalEngine::addPoint -both from the GeographicalEngine.h and GeographicalEngine.cpp. There is no other reference in the project to this function. I can compile and link just fine, but when i try to run my software, It gives the procedure entry point could not be found error. I am thinking this is because there is still some kind of reference to this function in some project settings file, because in the code window, i can see the function's signature, but when i click on it, vc++ takes me to the line where the function declaration used to be in the .h file. any ideas?
thanks
Avatar of jkr
jkr
Flag of Germany image
You'll have to rebuild the application that uses the DLL also, then this issue should be resolved.
Avatar of jkr
jkr
Flag of Germany image
Even better: Rebuild all modules contained in the project, just to be on the sage side.
Avatar of nicoleheritage
nicoleheritage

ASKER

I have done that. I have also tried restarting visual studio. I even restarted the computer. The issue remains unresolved.
ASKER CERTIFIED SOLUTION
Avatar of jkr
jkr
Flag of Germany image
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Avatar of evilrix
evilrix
Flag of United Kingdom of Great Britain and Northern Ireland image
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of evilrix
evilrix
Flag of United Kingdom of Great Britain and Northern Ireland image
Note to jkr: Sorry, was reading and typing and didn't refresh.
Avatar of nicoleheritage
nicoleheritage

ASKER

Thanks a lot guys, dependencywalker saved me a lot of trouble. turns out that there was an old dll project that depended on the function i mentioned. because that project was removed from the solution some time ago, i did not realize that the project that created the executable still had that dll listed as dependency. When I removed that dependency, the problem was resolved.