I have been looking for more than 12 hours to find a suitable solution for this particular problem ... I have an ASP MVC application (.NET framework 4.5) that uses the Interbase XE database.
While I run it locally on my machine, it works correctly. However, when I try to publish the site on a remote server, I get some build errors ...
Failed to load file or assembly Borland.Data.DbxCommonDriver, Version = 16.0.0.0, Culture = Neutral, PublicKeyToken = a91a7c5705831a4f 'or one of its dependencies. The installed assembly manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
In addition, looking at every possible solution posted on the Internet (which, unfortunately, did not help me). I also opened Borland.Data.DbxCommonDriver.dll in Reflector.
What amazes me is that Reflector claims that the version I (both local and remote!) Has the value PublicKeyToken = 91d62ebb5b0d1b1b instead of a91a7c5705831a4f , all other settings are equal (including version number 16.0.0.0).
So, the next thing I did was track all possible DLL files on the server. I uninstalled the ADO.NET 2.0 driver and deleted all existing DLL entries. As soon as the server was freed from any DLL, I rebooted it and reinstalled the ADO.NET 2.0 driver for Interbase.
However, I immediately got the same build error. Now I'm a little exhausted by ideas ...
- , PublicKeyToken?
- web.config( )?
- , PublicKeyToken?
:
- 64- . , ApplicationPool 32- , ADO.NET 2.0 Embarcadero.
- MS Visual Studio 2012 Pro.
https://forums.embarcadero.com/message.jspa?messageID=528498
http://docs.embarcadero.com/products/interbase/IBXEUpdate5/Readme.html