Oracle DAAB question

Dec 15, 2009 at 5:22 PM

Are there plans in entlib 5.0 to stop using the System.Data.OracleClient provider for Oracle database access in the source?  We've hit issues with both 64-bit deploys and with binding parms to refcursors (result sets from stored procedures).  And I believe I've seen info that says this provider is deprecated starting with 4.0 Framework.  Recently I ended up modifying our copy of the entlib 4.1 release to switch it to ODP.Net (version 11.1.0.7.20), applying the instructions someone kindly provided for entlib 3 at this blog: http://www.codeproject.com/KB/database/DAAB_On_ODPNet.aspx .  There was a little more work in various tester classes in 4.1, but it was still straightfoward.  These changes have resolved our 64-bit deployment issue and the refcursor binding issues.

Are there any plans to do this or something similar for 5.0?

Dec 16, 2009 at 2:47 AM

Hi,

We'll confirm this with the ent lib team and get back to you.

Valiant Dudan
Global Technology and Solutions
Avanade, Inc.
entlib.support@avanade.com

Dec 17, 2009 at 6:36 AM

I didn't see any plan for this in the Current Product Backlog so I don't think you'll be seeing this in the 5.0 version

 

Sarah Urmeneta
Global Technology and Solutions
Avanade, Inc.
entlib.support@avanade.com