Ryan stated: > > So what you were asking originally (and still) is 100% impossible. drawing an ostensible contradiction: > I disagree. > > https://www.nuget.org/packages/System.Data.SQLite/ should embed the latest published pre-compiled binary as available at https://www.sqlite.org/download.html See also message#22 > > https://www.sqlite.org/download.html ought to make it plain that it is necessary to download the published pre-compiled binaries ... so that SQLite.EXE, the CLI, is the same version as in System.Data.SQLite What "you were asking originally" was not restricted to the latest SQLite version. (eg. "Programmatically, how can I choose the version of SQLite that I use?", repeatedly. See posts 3, 12, 14.) This was clearly the "original" request to which Ryan was responding. (See post 17.) As Ryan, I and others have mentioned, that is not going to be possible without building your own executable images of the SQLite library code. You assert that the folks managing the NuGet repository should, for the System.Data.SQLite binaries, "embed the latest published pre-compiled binary", as if this refutes Ryan's observation about your original (and repeated) request which is not about the "latest" anything, except perhaps secretly in your own mind because you neglected to mention that using "the latest" is just what you really want. (There is a very simple way to achieve that secret objective.) Your contention that the SQLite development crew (which is quite small) "ought to make it plain that it is necessary to download" anything so that the SQLite shell and System.Data.SQLite have the same version likewise does not refute Ryan's true response to your original request. Furthermore, the contention is silly. If that crew were to busily state every potentially interesting SQLite-related fact as obvious as that, they would never get real development done. Maybe then, System.Data.SQLite would nearly always be caught up with the SQLite library evolution. The download pages (for [SQLite](https://sqlite.org/download.html) and [System.Data.SQLite](http://system.data.sqlite.org/index.html/doc/trunk/www/downloads.wiki) ) have made very clear what version of the library is built into the executable code they make available. Anybody who wants to be sure of using the same library code across multiple platforms and execution contexts has an obvious way to accomplish it: Wait until the downstream library users catch up to the version of particular interest. There is no reason for Richard, Dan or Joe to put a banner somewhere in the docs or download page stating this obvious fact. Nor is there any reason for them to notify downloaders that downstream users of SQLite (whose numbers are legion) might be using older versions. They may as well state that 1+1=2, 1+2=3, etc. until nothing else can be seen. I must say that I admire Ryan's patience in trying to help you past your confusion, frustration, and poorly framed questions while overlooking your whining and silly contentions. To the extent he has been in a patience contest with me, I concede him to be the winner.