Is Classic ADO still viable for a mixed managed/unmanaged App?
Posted
by Andy Dent
on Stack Overflow
See other posts from Stack Overflow
or by Andy Dent
Published on 2010-03-12T08:08:12Z
Indexed on
2010/03/12
8:17 UTC
Read the original article
Hit count: 216
We have a complex architecture with much logic in unmanaged code that needs database access.
Currently this is via ODBC drivers and MFC classes and we're considering the issues of migrating our abstraction layer to use ADO or ADO.Net. In the latter case we'd have to be pushing database logic back up into the .Net layer. I'm trying to decide if the pain of invoking the database via .Net callbacks is offset by the improvements in ADO.Net.
The Wikipedia comparison was interesting although I'm not sure I believe all the points in the comparison table (eg: does ADO.Net always use XML to pass data?).
A 2005 comparison shows ADO.Net performing dramatically faster.
Microsoft's guide to ADO.Net for ADO programmers suggests we will gain much from going to ADO.Net especially the way that data is available in native (.Net) types rather than solely through OLEAutomation's Variant.
© Stack Overflow or respective owner