Collectives™ on Stack Overflow

Find centralized, trusted content and collaborate around the technologies you use most.

Learn more about Collectives

Teams

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

Learn more about Teams

I just read this article today about how Microsoft decided to remove the System.Data.OrcaleClient namespace from .NET 4.0 library.

I used this as my primary tool for working with Oracle databases.

When I decide to upgrade my applications from the .NET 2.0 to .NET 4.0, what would bee some alternative options for working with Oracle databases in the .NET 4.0 framework?

Oracle has created a special website for OracleClient developers who are interested in learning about how and why to migrate to the Oracle Data Provider for .NET (ODP.NET).. check it out:

http://www.oracle.com/technetwork/topics/dotnet/index-085703.html

(edit: Fixed the broken link)

Microsoft will still make System.Data.OracleClient available in .NET Framework 4, but it will be labeled as "deprecated"

So go ahead and keep using it for updating existing applications where you relied on it previously. But for new development, you'll want to find an alternative. This shouldn't be too hard, as the whole stated reason it will be discontinued is that most people were already using alternatives. If you read further down the article it lists out the main options:

among those who offer such providers are DataDirect Technologies and Devart (formerly known as Core Lab). In addition, Oracle's provider, called Oracle Data Provider for .NET (ODP.NET), is a popular and viable option

As Joel noted , the Microsoft ADO .NET provider for Oracle will only be deprecated (which means it will still be available, but unsupported).

Alternatives include :

  • Oracle Data Provider for .NET . Free (if your time is, that is...)
  • DataDirect ADO.NET Data Provider for Oracle . Commercial (no first hand experience on this one, but I know several developers who used it successfully)
  • More providers can be found here .

    I don't have a problem with ODP.NET... It fully implements ADO.NET 2.0 standards (DbProviderFactory, etc). And NHibernate fully supports it as a data provider. Anthony Mastrean Jul 28, 2009 at 13:27 Yeah, it works well if you don't care shipping at least 19Mb worth of native Oracle client with your app (cf. stackoverflow.com/questions/70602/… ), if you don't care about parameters being bound by position (cf. stackoverflow.com/questions/1046632/… ), if you don't care about all these little things (I can't mention them all here) that can turn your development experience into a living hell. Mac Jul 28, 2009 at 14:33

    Thanks for contributing an answer to Stack Overflow!

    • Please be sure to answer the question . Provide details and share your research!

    But avoid

    • Asking for help, clarification, or responding to other answers.
    • Making statements based on opinion; back them up with references or personal experience.

    To learn more, see our tips on writing great answers .