ADO.NET is part of the .NET framework. There are no additional depencencies and with SQLite there is nothing to setup outside your own application.
The performance impact of using ADO.NET vs direct is miniscule and greatly outweighed by the improved efficiency in development. Sam On Sun, Mar 2, 2008 at 10:36 PM, Gilles Ganault <[EMAIL PROTECTED]> wrote: > On Sun, 2 Mar 2008 21:07:03 -0500, "Samuel Neff" > <[EMAIL PROTECTED]> wrote: > > I would go the ADO.NET route 'cause it'll fit into your .NET application > much > >better. The overhead is minimal compared to the normal cost of running > >database queries (in any database). > > The reason I'm concerned about using ADO.Net instead of hitting the > SQLite library directly, is that this adds dependencies in addition to > the .Net framework. Our customers are anything but computer-savvy, and > most don't have anyone technical around in case things don't work, so > that I'd like to minimize dependencies as much as possible. > > Also, what about performance when using the SQLite library directly > vs. going through ADO.Net? > > Hopefully, I'll have VS2005/2008 and SQLite up and running by the end > of the week, so I can check for myself. > > Thank you. > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > -- ----------------------------------------------------------------- We're Hiring! Seeking passionate Flex, C#, or C++ (RTSP, H264) developer. Position is in the Washington D.C. metro area. Contact [EMAIL PROTECTED] _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
