By now most of the .Net community is well aware that .Net 4.0 and VS2010 will ship with System.Data.OracleClient deprecated. This means your .Net application will build with warnings. BUT, it will still build and work, and Microsoft is still providing critical patch support for this Oracle .Net provider.
I’ve fielded a number of questions about this move and what impact it may have on the Oracle Database Schema Provider we are building for VS2010. The short answer is that it will have no impact. While our DSP intially relied on System.Data.OracleClient we’ve already planned to move to ODP.Net in order to take advantage of the richer feature set. ODP.Net and other 3rd party providers will be able to keep pace with Oracle releases better than a library that ships with .Net(which would be coupled with .Net releases rather than Oracle releases).
So overall, this isn’t at all as detrimental as it may seem on the surface. In the end any software product that moves to ODP.Net or a 3rd party provider will benefit from increased features and release timing.
Daniel Wood.
You can leave a response, or trackback from your own site.
