Taken from earlier link i posted:
Q: In ODP.NET 10.2.0.2 and higher, why does the same ODP.NET provider have two different version numbers?
A: For ODP.NET 10.2.0.2 and higher, the same ODP.NET binaries have two different version numbers when viewed from either .NET products (e.g. Visual Studio 2005 would see version 2.102.2.20) or when viewed from Oracle products (e.g. Oracle Universall Installer would see version 10.2.0.2.20). Prior to ODP.NET 10.2.0.2, the latter versioning was employed exclusively. The use the second versioning method was necessary to properly support .NET policy files for .NET Framework 1.x and 2.0.
For further details, read the versioning scheme section of Chapter 2 of the Oracle Data Provider for .NET (10.2.0.2 or higher) Developer's Guide .
...when first setting up an llblgen project, in the database settings, it lists the database drivers in that drop down (e.g. Oracle 10g Driver (ODP.NET 10.1.x)), hence my need for 10.2.... However, when llblgen produces the project code, there is a reference to the dll: E:\oracle\product\10.2.0\client_2\odp.net\bin\2.x\Oracle.DataAccess.dll (my dev machine), having version: 2.102.2.20
My generated code then must have redirect to 2.102.2.20. (truly why..i don't know)
But, apart from this bindingRedirect mess, I'm stuck on getting app to run on same machine as db server.
btw, to confuse matters, newVersion=10.2.0.2 also works in my llblgen config. (without last ".20")