This is probably not news to a lot or most of you.. SQLite doesn’t work on medium trust hosting. The reason makes sense. The .Net assembly has to talk (p-invoke) to a native dll. That’s something you can’t do in a standard medium trust environment.
Why this matters – to me – is that we had plans to move some of the non-blog content of the web site to an embedded database. SQLite was the embedded db of choice, but it doesn’t matter which one. This would be a problem with most all embedded db’s; perhaps something like VistaDB would work. That would require a license though. It was intended to be a first step towards a touch of CMS, and would have been pretty easy using FluentMigrator and Fluent-NHibernate. That will have to be put on hold until a suitable approach is found. Or suggested by a reader!
-j
If you’re a windows dev and use github for source control, you should set the autocrlf setting in git like described in this github article. I’m also setting the safecrlf setting, and hopefully those funky end of line characters I got going on will wiggle there way out. I wasn’t aware of this but probably should have thought of it, but git will add unix end of line characters to your files when you check them into a git repository. Just make sure everyone on the project has the autcrlf set to true, and everything will be fine. Use git bash and run these commands:
git config --global core.autocrlf false
git config --global core.safecrlf false
It’s easy to miss. I ended up adding those unix eof’s into the solution file and others for FluentMigrator. Justin Etheredge pointed out the problem and the fix. Hopefully it will all be cleared up soon. It doesn’t seem to prevent VS from opening and compiling, and even the build server continues to run.
UPDATE: I realized I was giving bad advice. You should set autocrlf to false not true.
-j