Yeah... I had considered that... I figured I would post just in case there was a quick/dirty fix. But, if not -- I'll just rebuild the libraries with non-conflicting name.
Ben Stifu wrote: > > Forgive the stupidity of my proposition, but how about simply renaming the > DLL you ship with your application? > > > Ben Henderson wrote: >> >> I am developing an application that needs to invoke methods from the FIPS >> validated libeay32 module. This works fine with the MS CLR, but Mono >> loads the libeay32 library from it's bin folder instead of my application >> directory. >> >> I have read one other topic on this forum that suggests that deleting the >> libeay32 module from the mono/bin directory will solve the problem. I >> know that this will solve the problem, but I am assuming that Mono has >> this library in the bin folder for a reason. >> >> >> Is there a way to force Mono to load my version of the library? >> >> Thanks, >> Ben >> >> > > -- View this message in context: http://www.nabble.com/DllImport%28%22libeay32%22%29-loads-library-in-mono-bin-folder-instead-of-my-version-tp22680025p22680318.html Sent from the Mono - General mailing list archive at Nabble.com. _______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
