We've started upgrading from v.2.0 to 2.5 and according to the documentation, DQE's and Oracle 10g drivers are compiled against ODP.NET 10.2. We have 10.2.0.100 installed and to our surprise, LLBLGen Pro threw exception that it can't find 2.102.2.20. This, to me, implies that it's compiled against ODP.NET 10.2.0.220, and will require company wide update of ODP.NET driver to 10.2.0.220+. Can you please confirm, and if so, I would suggest to add clarification to documentation? Now in our case, having company update is an expensive and time consuming proposition at this time, so would you recommend that we take the runtime library source that's part of the LLBLGen Pro v.2.5, loaded the solution up in VS.NET, change the oracle data access reference to 10.2.0.100, and rebuild the runtime library for use?

Thanks in advance.

-cchang.

Did you try using an assembly redirect at you config file? (http://walaapoints.blogspot.com/2007/06/odpnet-llblgen-pro.html)

10.2.0.100 isn't the final version Oracle released for .NET 2.0 and .NET 1.x, IMHO. they released a new version of ODP.NET 10g, which used a different versioning numbering than the previous version. The previous version used 10.1.0.x, the new ones use 1.10x.x for .NET 1.x and 2.10x.x for .net 2.x

So if you have a 10.2.0.100, it sounds like a patch version for the older one OR a beta for the new one. If it's the former, use the redirect as described in the link in David's post above, if it's the latter, please upgrade to the final version.

LLBLGen Pro v2.5 comes with drivers and DQE's build against 10.1.0.4 as well (please see What's new -> General and Using the generated code -> Compiling )

We've also looked at the option of using assembly redirect. Is there any difference between drivers and DQE's built against 10.1.0.4 and assembly redirect vs. one that is compiled against 10.2.0.220? Can assembly redirection fails in cases as described in http://walaapoints.blogspot.com/2007/06/odpnet-llblgen-pro.html ? If not, why have two sets of drivers and DQE's? what's the benefit of using drivers and DQE's against latest ODP.NET version?

Thanks.

so would you recommend that we take the runtime library source that's part of the LLBLGen Pro v.2.5, loaded the solution up in VS.NET, change the oracle data access reference to 10.2.0.100, and rebuild the runtime library for use?

You can safely do that as described in the link posted by David.

Is there any difference between drivers and DQE's built against 10.1.0.4 and assembly redirect vs. one that is compiled against 10.2.0.220?

Most probably there are no substantial difference except the Oracel.DataAccess version they have been built against.

Can assembly redirection fails in cases as described in http://walaapoints.blogspot.com/2007/06/odpnet-llblgen-pro.html ?

Yes it may fail in some cases, that's why if you want to stay in the safe side, you may need to re-build the DQE against the ODP.NET version that you have.