I'm getting the same error with the latest 1.4 API. I have compiled to x64 and it runs just fine in development in on my VS2013 x64. When I deploy the output to my host x64 or Windows Server 2012 box it won't run at all. I'm using the exact structure as in the sample.
1>------ Rebuild All started: Project: AVL, Configuration: Debug x64 ------
1> 4 File(s) copied
1> 2 File(s) copied
1> AVL -> C:\temp\CityTrackerNav\CityDPW_NavmanTracker\bin64\AVLTracker.exe
========== Rebuild All: 1 succeeded, 0 failed, 0 skipped ==========
Esri.FileGDBAPI.dll version 1.4.0.183, VS2013 Update 5, Target framework 4.5.1
Error Log:
Quartz.SchedulerException: Job threw an unhandled exception. ---> System.IO.FileNotFoundException: Could not load file or assembly 'Esri.FileGDBAPI.dll' or one of its dependencies. The specified module could not be found.
at SnowBlower.SnowJob.Execute(IJobExecutionContext context)
at Quartz.Core.JobRunShell.Run() in c:\Program Files (x86)\Jenkins\workspace\Quartz.NET\src\Quartz\Core\JobRunShell.cs:line 187
--- End of inner exception stack trace --- [See nested exception: System.IO.FileNotFoundException: Could not load file or assembly 'Esri.FileGDBAPI.dll' or one of its dependencies. The specified module could not be found.
File name: 'Esri.FileGDBAPI.dll'
Thx in advance!
-BC
You always need to be careful when Windows says it can't find a DLL, because sometimes it finds a DLL with the right name, but the wrong architecture, and fails.
You should make sure that the target directory is before the FileGDB API installation in your PATH when testing locally (actually, even better would to not have the FILEGDBAPI_HOME\bin* in the PATH at all), and to make sure that the required binaries (both the C# wrapper DLL and FileGDBAPI runtime DLL are in the bin folder with your application).
Please check the contents of C:\temp\CityTrackerNav\CityDPW_NavmanTracker\bin64 to make sure all the pieces are present.
Linux has an OS-level tool to inspect binaries for DLL resolution, but Windows requires a third-party tool (I have used Dependency Walker successfully for this purpose).
- V