[fdo-users] ah! : Redistributing FDO - "The specified module could
not be found"?
Crispin at 1Spatial
Crispin.Hoult at 1Spatial.com
Tue Jan 15 04:32:29 EST 2008
I did all the "hard stuff" trawling through depends etc and checking MFC DLL
version numbers... and then it turned out to be the simplest thing -
provider path in the XML file. Klutz!
A bit of tinkering and two comments/questions on the providers.xml file...
1) The "<Version>" in the file within the 3.3 beta were still all 3.2.1
although the actual fileversions in the DLLs were 3.2
2) I edited the xml to remove the path from the DLLs and the providers were
picked up fine... would it be better to redistribute the provders file with
just the DLLs and not the default "C:\Opensource_FDO\..." path that everyone
then changes? Are there any other ramifications of this?
It looks as if a DLL is missing from the path. Do you have all the FDO
binaries in the path, managed and unmanaged? Also, try and run the
depends.exe application to see if it can tell you what binary is missing.
Thirdly, check the content of providers.xml to ensure that the provider path
locations are correct.
View this message in context: http://www.nabble.com/Redistributing-FDO---%22The-specified-module-could-not-be-found%22--tp14806626s18162p14834969.html
Sent from the fdo-users mailing list archive at Nabble.com.
More information about the fdo-users