Repository navigation
[document enhancement] compare with Microsoft.EntityFrameworkCore.Sqlite? #166
Description
The readme doesn't mention the initial motivation to create the project. I'm a curious is it because there's no sqlite code first at that time? From commit history I noticed the oldest file was created 7 years ago. Maybe there's no other EF sqlite adapters at that time? I also found the stackoverflow answer refering this repo.
Now there's Microsoft.EntityFrameworkCore.Sqlite, with which one can create sqlite code first way.
While this repo is really excellent, people may feel hard choosing between the two.
So still any advantage using SQLite.CodeFirst?
One of the possible difference might be:
SQLite.CodeFirstis usingSystem.Data.SQLite, whileMicrosoft.EntityFrameworkCore.SqliteusesMicrosoft.Data.Sqlite.
Activity
msallin commentedon Aug 12, 2021
Back then there was full Framework and Entity Framework 6. EF 6 didn't (and still does not AFAIK) offer Code First for SQLite.
It is possible to use EF 6 also with .NET Core / .NET 5 and hence I did the necessary adjustments to support this.
Long story short:
If you use EF Core, there is a built-in (much better) option to use.
If you use EF 6 (for whatever reason) AFAIK there is no better option than using this library.
Maintaining this lib do not take much time (updating dependencies from time to time, answering few questions and merge some PRs) and I plan to continue as long as it is useful for somebody.
I edited my answer on Stack Overflow to state this and I'm also going to update the README of this repo.
Here we go:
LeiYangGH commentedon Aug 12, 2021
thanks for your quick reply, and contiouns effort to maintain this repo!
LeiYangGH commentedon Nov 24, 2021
I just tried .net framework 4.8(netstandard2.1) and works well with ef core 3.x code first.