Splitsville for System.Data.OracleClient & .NET – Part Deux

July 09, 2009 Data & AI

There's been a lot of buzz (see below for some collected links) about Microsoft's decision to deprecate System.Data.OracleClient).

I've received numerous emails, and as a company we've been watching the conversation in particular tracking some vociferous opinions circulating as to the perceived quality of third-party options. If you've used OracleClient for some time, I can certainly appreciate that you may be used to some of the quirks and baggage such as the native OCI Client dll that you used for many years. As a third-party innovator, we are part of a healthy and thriving community of outfits who are fully engaged in building quality technologies on the .NET platform - just walk the conference floors or either TechEd or PDC and it is plain to see.

Still curious on how we do it? Check out this for on details on how we have the most rigorous standards for data connectivity anywhere. We've baked DataDirect Technologies 20-year history providing standards-based data connectivity into our ADO.NET providers. See the difference for yourself and go grab a copy of the DataDirect Connect for ADO.NET data provider for Oracle.

You can also join me on an online webinar, next week where I delve into some of the details on this recent announcement.

As I mentioned above, here's a relatively authoritative list with lots of perspectives on the impact of Microsoft's announcements. Enjoy!

Jonathan Bruce