Victor,

It is what I did to get the actual file ADODB.dll, and to be able to put it into the first application directory in production.
I can do the same with the second application, but then I have no choice but to put the second ADODB.dll into the second application production directory.

However, I would like to have only ONE dll file, and be able to share it between two applications in the production environment (where Visual Studio is not installed, and among windows\assemblies there is no ADODB directory).

Is it possible?




>As long as it's not strong named you should be able to put this assembly on the server and reference it from any applications.
>
>One thing you may need to add is "Copy Local = true" in the properties so that when you distribute your app it'll include the ADODB.DLL in the distribution.