CODEWITHSUNDEEP
asp.netoracle-database
user760992
user760992

Reputation: 73

Is it ok to still use System.Data.OracleClient even though its obsolete?

I've been using System.Data.OracleClient for a while now and i'm not sure whether I should keep using it if it is being deprecated?

Although all my pages will still work under the .Net 4 framework i'm worried that when there is a new framework all the pages may stop working.

Does anyone have any suggestions?

Upvotes: 7

Views: 4241

Answers (3)

SQLMason
SQLMason

Reputation: 3275

Using the Oracle DLLs has always performed better (quicker) for me. While System.Data.OracleClient will remain in VS, I don't understand why you wouldn't want to use the Oracle DLLs.

Upvotes: 1

Zach Green
Zach Green

Reputation: 3460

Using it is still ok for now, but what is the future of the app? Do you plan for the application to be used and maintained for years in the future? If so, you should move to ODP.net so that you get updates and new features.

Upvotes: 3

tvanfosson
tvanfosson

Reputation: 532565

Microsoft's recommendation is that you find a third-party client, such as ODP.NET.

The types in System.Data.OracleClient are deprecated. The types are supported in version 4 of the .NET Framework but will be removed in a future release. Microsoft recommends that you use a third-party Oracle provider.

http://msdn.microsoft.com/en-us/library/77d8yct7.aspx

Upvotes: 1

Related Questions