Closed tofutim closed 11 years ago
Aha, on my end, it is 3.7.17
Yeah, this happens whenever the extension updates (or if you're unfortunate enough to be running a 32-bit OS, or on a different root drive, etc.). The whole extension experience is...not good, let's say. I see 3.7.16.1 as the current version on sqlite's website, though. VS is not prompting me to update the extension to 3.7.17.
My recommendation is to manually edit the project file for now to point at the correct path. It's what I have to do whenever the version bumps, I just push the change up when I run into it.
Also, you many need to update sqlite3.h in the Headers directory to be matching the extension version as well. I tend to grab the sqlite amalgamation header from the latest version, but I don't see 3.7.17 yet (preview version?)
What I really should do is grab the lib and dll out of this vsix extension nonsense and stick them under git and rev them independently of the extension.
That would be cool. In this case it is my own fault for compiling my own vsix.
On Tue, Apr 9, 2013 at 12:22 PM, peterhuene notifications@github.comwrote:
What I really should do is grab the lib and dll out of this vsix extension nonsense and stick them under git and rev them independently of the extension.
— Reply to this email directly or view it on GitHubhttps://github.com/peterhuene/sqlite-net-wp8/issues/8#issuecomment-16134262 .
The extension is now updated to 3.7.17.
Hi, I tried to add the project to an existing solution and got. In my case my extensions are installed elsewhere - which is probably the issue.