Allow developers to choose what SQLite implementation they use

[HelenMamalakiV1]

The problem
We want to eliminate the SQLite dependency in Mapsui.Extentions which contains specific dependencies on SQLitePCLRaw.config.e_sqlite3 and SourceGear.sqlite3. It would be preferable if the library only depended on SQLitePCLRaw.core which would allow an application to bring in its own lower level sqlite-compatible native library.

In cases where we want to use an encrypted SQLite product such as SQLCipher - we want to avoid having separate implementations of SQLite as this can cause database corruption or worse bypassing encryption.

The proposed solution

1. Remove SQLite dependency in SQLitePCLRaw.config.e_sqlite3 and SourceGear.sqlite3 - add a dependency on SQLitePCLRaw.Core.

2. Update documentation to have integrators add the appropriate SQLitePCLRaw implementation to the Application project. This could be any SQLitePCLRaw-compatibile libraries, either SourceGear, SQLCipher, SQLite3mc, SEE, etc

[pauldendulk]

Thanks for pointing this out. I understand the problem. This is a more general issue which causes problems for other references as well. The reason the SqlitePersistentCache is in the Mapsui.Extensionand not in a more core project is because of its dependency on sqlite, making it less of a problem (only if you add the Mapsui.Extension). The other two things in that package, GeoTiffProvider and DotSpatialProjections, are also in that project because of their dependencies. From my perspective this is a bit of a fringe package, stuff that we also have and we moved aside.

Your proposed solution would remove the explicit dependency but would also come with a downside which is that things would not work unless users would also add the specific dependencies on the sqlite implementation. We would have to document that and users would have to figure that out. If this solution is really common and users expect this it might still be a good idea.

Something else that I consider is to move all three into into separate packages. The downside is more packages and some with just one file in them, like the GeoTiffProvider, so that is also a bit weird. This is all there is in the Mapsui.Extension currently:

Given that I am not sure yet where I want to go with this makes me less inclined to change this right now, so this is not something I want to change in the short term.

Workaround

For your purpose I would suggest to remove the dependency on the Mapsui.Extension and copy the files that you use into your own project, and build it the way you like it.