G
goo
Guest
It was to steps that was the problem, first I had added the x64 version instead of x32 (developing x64, but it seems like the customer has installed a x32 bit version on the production server). Then it was the issue regarding workpath for the startup on the server. It was set to d:\progress\oneSite and my workarea was d:\progress\oneSite\thisSite. I did not see that first, so by referring -assemblies assemblies instead of -assemblies thisSite/assemblies, I was pointing to another assemblies area. I found that while I was looking into processMonitor and processExplorer. And of course it is nice to know what directories where a .dll is searched for. Now the dll is working, and I am very pleased to use Chilkat as a tool for doing stuff that is not that easy to do in the openedge language, very cool. Thanks for your help! //Geir Otto
Continue reading...
Continue reading...