This article lists the files that need to be redistributed for a 32-bit ODBC driver on Windows built using C#.

Although C# can be platform and bitness agnostic, the bridge from the native Simba ODBC layer is not. This means that separate files need to be deployed depending on the bitness of the driver.

For a 32-bit ODBC driver built using C#, the following files need to be included:

– simbaicudt38_32.dll
– simbaicuin38_32.dll
– simbaicuuc38_32.dll
– The appropriate run-time redistributables, see http://msdn.microsoft.com/en-us/library/vstudio/ms235299.aspx
– Your native CLIDSI based driver DLL

If you are building as server, then you will also need the following 32-bit files:

– libeay32.dll
– ssleay32.dll

Note that for some files, the 32- and 64-bit versions have the same name so you should ensure that you use the 32-bit versions of these files.

You should also copy the managed DLLs to the same directory on the machine and install them in the GAC using gacutil.exe. The managed DLLs are:

– Simba.DotNetDSI.dll
– Simba.DotNetDSIExt.dll
– Your managed driver DLL (this should be different from the native one)
– Any dependencies of your driver
– Any of the relevant Simba.DotNetDSI.resources.dll and Simba.DotNetDSIExt.resources.dll files for the appropriate locales for your driver

Note that the Simba.ADO.Net.DDEX.dll file is only required if you wish to be able to use your provider via Microsoft Analysis Services, Visual Studio, and Reporting Services.

You will also need the following error messages files:

– ODBCMessages.xml
– CLIDSIMessages.xml
– SQLEngineMessages.xml   (Only if you are using the SQLEngine with your driver)
– ServerMessages.xml   (Only if you are building as a server)
– CSCommonMessages.xml   (Only if you are building as a server)

Note that you should include the appropriate error message locales for your driver.