CODEWITHSUNDEEP
xamarinxamarin.android
Andrew Stephens
Andrew Stephens

Reputation: 10203

Xamarin Android SQLite.Net NuGet package

I'm having a go at creating my first Android app using Xamarin. I'll be needing a database, and the Xamarin docs recommend the "SQLite-net-pcl" NuGet package (here). When I go to install this package it lists approx 50 dependencies that it wants to install! How much is this going to increase the size of my app by?

Is this normal with Xamarin development? Coming from a WPF background I admit I haven't got my head around all this .Net core/standard stuff yet.

And why do the docs recommend this package over the built-in 'Android.Database.Sqlite' namespace? Does the ease of use (of the SQLite.net package) outweigh the increase in app size?

Upvotes: 2

Views: 345

Answers (1)

Prashant Cholachagudda
Prashant Cholachagudda

Reputation: 13090

How much is this going to increase the size of my app by?

Not much, Xamarin links out (removes) the unused code when you build your app in release mode. For example if you're not using any methods from System.IO, the assembly will not be included in the final build

Does the ease of use (of the SQLite.net package) outweigh the increase in app size?

Part of it is ease of use and the real advantage is you can reuse the code on iOS or any other platforms. Using Android.Database.Sqlite doesn't help you much if you're planning porting your app to other platforms

What determines which of those 50+ assemblies get pulled into my app?

Dependency on the netstanderd is what pulling those 50+ assemblies, otherwise Sqlite-net-pcl just need SQLitePCLRaw.* assemblies

There is nice series explaining netstanderd from one of the .Net engineers on youtube here - https://www.youtube.com/playlist?list=PLRAdsfhKI4OWx321A_pr-7HhRNk7wOLLY Hope it will answer your questions regarading netstanderd

Upvotes: 2

Related Questions