Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to use SQLite on new Windows 8.1 Store app (Visual Studio 2013)
    primarykey
    data
    text
    <p>So, I installed Visual Studio 2013 on my Windows 8.1 box. I want to experiment with it and created a new <strong>Windows Store Grid App</strong>. I want to persist data on a SQLite database, apparently the database of choice for WinRT apps.</p> <p>Quickly found links to the vsix needed in order to be able to use the SDK: <a href="http://sqlite.org/download.html">SQLite download page</a>, and downloaded sqlite-winrt81-3080002.vsix.</p> <p>Installed it, then in my project, added the reference to the newly installed SDK (right click references, add reference, navigate to Windows, select extensions and tick SQLite for Windows Runtime (Windows 8.1) checkbox.</p> <p>Also quickly found that it won't compile on Any CPU. On Configuration Manager, selected Debug, x64 active platform, that made me able to compile the application.</p> <p>Finally, while attempting to use the namespace <code>SQLite</code> I noticed VS 2013 isn't recognizing it. Attempted many things like adding reference to the .dll directly, exploring the component to see which namespaces were available (which doesn't show anything), and I'm quickly running out of ideas. Because it's kinda new thing, and with limited interest, google, the saviour, doesn't want to save me today.</p> <p>So, how one would be able to use the SQLite SDK in their Visual Studio 2013 projects, targeting Windows Runtime 8.1?</p> <p><a href="http://pastebin.com/pGHHerHq">These are the contents of my csproj file</a></p> <p><strong>UPDATE</strong> Stupid me, thought there was no managed land (.net) in Metro style land. Sorry for causing any confusion.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload