I've previously posted a few things about SQLite including a HOWTO on how to build from their source code. If you still want to build your own DLL from their source code that is totally fine, but not necessary in most every single case I've seen in app usage. One of the challenges I noted is that since SQLite is a native component and if you are a managed (.NET) app you can't be architecture neutral anymore (AnyCPU). What this means is that you have to build your app for each architecture you want to support: x86, x64 and ARM. The flow of this using SQLite3.dll was that you would have to package, change the DLL, re-package.

Not anymore.

In working with the great folks on the SQLite team, they've packaged the binaries up (for Windows 8 apps) in a nice installer using the Extension SDK format. What this means is you now add a 'reference' to the SQLite binary and based on the architecture being built for your package, it will pull in the right DLL without you having to manage that yourself. Here's some step-by-step.

Read More from: Original Source

I guess you came to this post by searching similar kind of issues in any of the search engine and hope that this resolved your problem. If you find this tips useful, just drop a line below and share the link to others and who knows they might find it useful too.

Stay tuned to my blog, twitter or facebook to read more articles, tutorials, news, tips & tricks on various technology fields. Also Subscribe to our Newsletter with your Email ID to keep you updated on latest posts. We will send newsletter to your registered email address. We will not share your email address to anybody as we respect privacy.

This article is related to

C#,.NET,Architect,Intermediate,Advanced,VS2010,.Net,Articles,Database,SQLite,Windows 8