Reputation: 57172
Since System.Data.OracleClient
is deprecated in .NET 4.0 and will be discontinued in a future version of the framework, I would like to try to use OleDb as an alternative.
What are the differences between System.Data.OleDb
and System.Data.OracleClient
when accessing an Oracle database? Is System.Data.OracleClient
offering more features?
Will access to Oracle via OleDb continue working with future .NET framework versions?
Note: I tried ODP.NET, but I got the "The provider is not compatible with the version of Oracle client" problem and did not manage to solve it, that's why I was wondering if OleDb could be an alternative.
Upvotes: 1
Views: 2411
Reputation: 849
You really need to resolve your DLL versioning issues that prevent you from using ODP.Net. We use ODP.Net in several enterprise web applications. It is required for proper support of Entity Framework among other things. I recommend a full de-install and re-install of the Oracle Client.
Upvotes: 0
Reputation: 4558
It's only marked as deprecated, which means that it will no longer updated or developed by Microsoft an might be removed in future versions of .NET framework. But it's stil in the .NET 4.5 preview release:
http://social.msdn.microsoft.com/Forums/en-US/netfxbcl/thread/71e232a7-e845-442e-9e36-f203e14fa196/
So in my opinion, there is no need to change to an (expensive) 3rd party component at the moment. Of course you can try, but I would wait until the release of .NET 4.5 or a later version and see what will be available then.
Upvotes: 1