The error "failed to load the file or assembly" mysql. Data, version = 5.1.4.0, culture = neutral,... "is prompted during connection to MySQL ,........"

PM

Codesmith4.1.3 failed to Load file or assembly "MySQL. data, version = 5.1.4.0, culture = neutral ,........ or one of its dependencies. The Assembly list definition found does not match the Assembly reference. " Solution: Download the mysql. Data. dll (5.1.4) assembly at ftp.ntu.edu.tw/pub/mysql/downloads/connector-net/mysql-connector-net-5.1.4-noinstall.zip. Put mysql. Data. dll in the bin directory of the codesmith directory and run it again. The problem is solved! Note: the download of MySQL. Data. dll must correspond to the version number in the connection error prompt. Change "5.1.4" to the required version number.     The message "failed to load the file or assembly" mysql. Data, version = 5.0.7.0, culture = neutral, publickeytoken = c5687fc88969c44d "or one of its dependencies. The Assembly list definition found does not match the Assembly reference. (Exception from hresult: 0x80131040 )" Copy mysql. Data. DLL to the bin directory under codesmith. The call is still incorrect, Later, we can see that the mysql. Data. dll file version is 5.2.1.0, which is larger than the error message. It seems that we need to try the next 5.0.7.0, Is the http://ftp.ntu.edu.tw/pub/MySQL/Downloads/Connecto R-net/mysql-connector-net-5.0.7-noinstall.zip, Copy the mysql. Data. dll file to the bin directory under codesmith again, and then configure the test. OK. It seems that codesmith has killed the database program calling and should be set to a configuration file to allow users to define their own versions so that they can be more flexible.       Http://www.cnblogs.com/68681395/archive/2010/09/26/1835971.html Failed to Load file or assembly "oracle. dataaccess, version = 2.111.7.0, culture = neutral, publickeytoken = 89b483f429c47342" or one of its dependencies. Trying to load a program with an incorrect format For 64-bit operating systems: advanced options for the application pool of Oracle. dataaccess. dll IIS     Set this parameter to true. The above is a 32-bit database. This is the solution for the last error. However, when the database is 64-bit, replace oracle. dataaccess. dll with the file of the current database, and set the location to false. Recently, Oracle was used in ASP. NET development. The database provider ODP. Net provided by Oracle was used, and the Oracle. dataaccess. dll component was used. In practice, several times of "failed to Load file or assembly" oracle. dataaccess, Version = 2.112.1.0 ..."", As shown in. Here, the problem and solution are summarized as follows: 1. Possible causes (1) reference error: when the file cannot be loaded, the path referenced by Oracle. dataaccess. dll may be incorrect; (2) version mismatch: The Oracle. dataaccess. dll referenced in development does not match the version in Oracle. The so-called version mismatch means that the version number does not match; on the other hand, the 64-bit and 32-bit do not match. When using a 64-bit Oracle, you must use the corresponding 64-bit oracle. dataaccess. DLL. 2. Solution (1) It is easy to check whether the reference has an error. Check whether the file oracle. dataaccess. dll exists in the reference path; (2) oracle. dataaccess. DLL is generally located in the Oracle installation directory ".. /product/11.2.0/dbhome_1/ODP. net/bin/2.x/ ", you can use the DLL corresponding to Oracle in the program during development.