Jose R. Guay Paz

Most of the time on
ASP.NET, C# & SQL Server

Sponsors

News

INETA Community Speakers Program

My latest tweets

this.blog.owner=

  • CSW Solutions
  • Follow Me
  • Works On My Machine

.NET Communities

  • INETA Latam

Blogs I Read

Websites I like

News: System.Data.OracleClient update

Microsoft has made a huge announcement regarding the OracleClient library in ADO.NET. Himanshu Vasishth, Program Manager for ADO.NET OracleClient made the following information available in the ADO.NET Team Blog yesterday:

As a part of formulating our long term strategy for ADO.NET, we have had several discussions with number of our customers, internal and external partners, and MVPs to better align our development efforts to ensure we are delivering the right technologies according to our customers’ highest priority needs. One of the key intent of these discussions and the associated research was to understand the needs and requirements of customers who develop applications with Oracle using “System.Data.OracleClient” (OracleClient).   OracleClient is the ADO.NET provider for Oracle developed by Microsoft and ships as a part of the .NET Framework.

We learned  that a significantly large portion of customers use our partners’  ADO.NET providers for Oracle;  with regularly updated support for Oracle releases and new features. In addition, many of the third party providers are able to consistently provide the same level of quality and support that customers have come to expect from Microsoft. This is strong testament of our partners support for our technologies and the strength of our partner ecosystem.  It is our assessment that even if we made significant investments in ADO.Net OracleClient to bring it at parity with our partners based providers, customers would not have a compelling reason to switch to ADO.Net OracleClient.

The Decision

After carefully considering all the options and talking to our customers, partners, and MVPs it was decided to deprecate OracleClient as a part of our ADO.NET roadmap.

Read the full story here.

Comments

Prasad Khandekar said:

Overall I think it's a good decision from Microsoft Side. Oracle is doing great job in keeping their own ADO.NET provider upto-date and infact they are the right people to provide robust connectivity options with their database.

In fact Microsoft should never have shipped this provider at all.

# June 19, 2009 5:36 AM

Mike Nelson said:

Hi Jose,

I work with DataDirect Technologies, and if you’re skeptical about Microsoft’s announcement you might consider Connect for ADO.NET from DataDirect Technologies. Connect for ADO.NET offers a client-less solution for .NET platforms –free from OracleClient or so called Instant Client. Go grab a copy of our install and check out what a true pedigree, 100% managed provider, can offer while supporting the latest .NET technologies such as the ADO.NET Entity Framework provider for Oracle –blogs.datadirect.com/.../net-connections

Thanks,

Mike

mnelson@crt-tanaka.com

# June 23, 2009 5:59 PM
Leave a Comment

(required) 

(required) 

(optional)

(required)