On Jul 20, 2011, at 7:25 AM, Gabriel wrote:
> Why all the other implementations of SQLite use the Class names and Assembly
> Names like SQLiteConnection and only the mono implementation uses
> SqliteConnection?
Good question. (Because the System.Data.SQLite folks didn't read the Framework
Design Guidelines? ;-)
> There is any way that you guys can fix this?
That said, it's too late to change Mono.Data.Sqlite.dll (backward compatibility
and all that), so we're going to have to live with it.
However...Mono.Data.Sqlite is really just a ADO.NET wrapper around
SQLITE.DLL/libsqlite.so. There are versions of System.Data.SQLite.dll which are
_also_ just wrappers around SQLITE.dll (the non-mixed-mode assembly versions;
you may need to build from source to get this).
I know that on Linux, you can use the "split" (non-mixed-mode)
System.Data.SQLite.dll assembly and things work properly. It _may_ work
properly on Mono for Android; it would be interesting for someone to try to
compile the System.Data.SQLite sources against Mono for Android's framework
assemblies and see if the resulting assembly works on Android.
> There is any implementation that works With monodroid that uses
> SQLiteConnection like class names?
Worst case...there are always `using-alias` clauses...
#if !MONO
using System.Data.SQLite;
#else
using Mono.Data.Sqlite;
using SQLiteConnection = Mono.Data.Sqlite.SqliteConnection;
// repeat for every other SQLite* type you need.
#endif
I admit that this would get ugly really fast...but it is viable.
- Jon
_______________________________________________
Monodroid mailing list
[email protected]
UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid
