This skipped past my radar, but it seems 2 days ago the .Net team announced they will be dropping their code base for supporting the packaged ADO.NET provider for Oracle developed by Microsoft that ships as a part of the .NET Framework. Which translates to that you will have to get the Oracle provider direct from Oracle. Which honestly is normally the best practice anyway! The ADO.Net announcement can be found http://blogs.msdn.com/adonet/archive/2009/06/15/system-data-oracleclient-update.aspx.
Some may consider this a non-event, while it may seriously turn the world upside down for others. The latest set of Oracle drivers can be found here http://www.oracle.com/technology/tech/windows/odpnet/index.html
The Oracle Data Provider for .NET (ODP.NET) features optimized ADO.NET data access to the Oracle database. ODP.NET allows developers to take advantage of advanced Oracle database functionality, including Real Application Clusters, XML DB, and advanced security. The data provider can be used with the latest .NET Framework 3.5 version.
ODP.NET makes using Oracle from .NET more flexible, faster, and more stable. ODP.NET includes many features not available from other .NET drivers, including a native XML data type, array parameters, RAC optimizations, and statement caching. ODP.NET is designed for scalable enterprise Windows solutions by providing full support for Unicode and local and distributed transactions. Distributed transactions are supported using the Oracle Services for MTS.
Frankly this package ranks as #1 & #2 when using Google to search for “oracle .net provider” so I suspect a lot of developers who use Google will have gone straight to this approach anyway.
Update
It seems this story is gathering momentum now:
- http://cwebbbi.spaces.live.com/Blog/cns!7B84B0F2C239489A!4573.entry
- http://www.theregister.co.uk/2009/06/18/microsoft_kills_oracle_connector/
Gareth