1934022 - How are the unmanaged SQL Anywhere ADO.NET DLL provider files deployed? Are there any considerations for 32-bit vs. 64-bit environments?

The managed SQL Anywhere ADO.NET provider is deployed as part of a .NET project and is loaded by the .NET Common Language Runtime (CLR).

• iAnywhere.Data.SQLAnywhere.dll
• iAnywhere.Data.SQLAnywhere.v3.5.dll
• iAnywhere.Data.SQLAnywhere.v4.0.dll
• iAnywhere.Data.SQLAnywhere.v4.5.dll

The SQL Anywhere ADO.NET provider requires additional unmanaged DLL files to also be deployed to the system and come in two formats: 32-bit (\bin32) and 64-bit (\bin64). For a list of files that need to be deployed with the ADO.NET provider, see the SQL Anywhere documentation. For Microsoft Windows systems using the ADO.NET provider from SQL Anywhere 16, the files required are:

• dblg[LL]16.dll - Where 'LL' is the language code for the error messages desired. 'dblgen16.dll' is the English library language DLL.
• dbicu16.dll
• dbicudt16.dll

Once the managed SQL Anywhere ADO.NET provider is first referenced in a .NET application by the CLR, an unmanaged DLL ("dbdata.dll") is extracted at runtime to the system temporary folder. This DLL file then expects to reference the unmanaged DLL files deployed by using the Dynamic-Link Library Search Order, defined for Microsoft Windows systems. The choice of bitness (32-bit or 64-bit) of this extracted DLL matches the bitness of the running .NET CLR that loaded the SQL Anywhere ADO.NET provider.

• SAP Sybase SQL Anywhere 10
  SAP Sybase SQL Anywhere 11
  SAP Sybase SQL Anywhere 12
  SAP Sybase SQL Anywhere 16
• Microsoft Windows XP, Vista, 2000, 2003, 2008, 2008 R2, 2012, 7, 8
• Microsoft .NET 2.0, 3.0, 3.5, 4.0, and 4.5

native, 11654474 , KBA , BC-SYB-SQA , SQL Anywhere (on premise, on demand) , How To