Got an email forwarded by the co-worker, saying the Microsoft ADO.NET team is going to deprecate OracleClient as a part of their ADO.NET roadmap.
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.
Recommendation and Guidance:
System.Data.OracleClient will be available in the upcoming 4.0 release of .NET Framework; however, it will be marked as deprecated. This will have no impact to existing applications and these applications will continue to work as expected. Developing new applications which use OracleClient will be supported; however, warnings will be raised if the applications are compiled against .Net 4.0. Once compiled, no warnings or errors will be generated while running these applications. We strongly recommend customers to use our partners’ ADO.NET Provider for Oracle instead of continuing to use Microsoft’s OracleClient for new application development.
I tried Oracle .net provider ODP for .NET before, but it is easier to use OracleClient from Microsoft since it was more integrated in the .net framework and visual studio.
Now I will have to go back to look at ODP for .net again. Because most of my web applications are built on ASP.net against Oracle database.
For more information, check the blog below:
http://blogs.msdn.com/adonet/archive/200…
Very neat blog.Really looking forward to read more. Cool.
[Reply]