I should also mention that the informix ADO.NET driver can be downloaded from the IBM web site. The link is in the support forums.
Also, the MySQL provider has been compiled against the latest official 1.0.4 release. There is a slight name change in namespace usage from ByteFX to MySQL as a result.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I've just committed some changes to make the providers for each database separate .DLLs.
The initial testing for OLEDB (access) works Ok and I'll check the others over time.
Be aware that the class="" attribute in the database mapping is now a provider="" and it should reference a .DLL file name, not a class name.
- Richard.
I should also mention that the informix ADO.NET driver can be downloaded from the IBM web site. The link is in the support forums.
Also, the MySQL provider has been compiled against the latest official 1.0.4 release. There is a slight name change in namespace usage from ByteFX to MySQL as a result.
what happens with ODBC
Use provider="AF_ODBC.dll" and set up the XML file to use a connection string for the name parameter
for example
<database name="myName" provider="AF_ODBC.dll">
<parameter name="name" value="myconnectionstring"/>
<parameter name="ansinulls" value="true"/>
</database>