On Mon, Nov 18, 2019 at 2:23 AM Joe Mistachkin
wrote:
>
> Mike King wrote:
> >
> > "It needs to be clearly stated somewhere that EF 6.3 is meant only as a
> > tool for migrating from .NET Framework, and that EF Core is the version
> > that should be used." *2
> >
>
> Given the phrasing here, it
I've done some reading and kind of side stepped the issue a bit by adding a
reference to System.Data.SQLite and use that connection object to connect
to the database and pass the connection to the MS SQLite driver. I can now
password encrypt databases and (from my very brief tests) it looks like I
Mike King wrote:
>
> "It needs to be clearly stated somewhere that EF 6.3 is meant only as a
> tool for migrating from .NET Framework, and that EF Core is the version
> that should be used." *2
>
Given the phrasing here, it sounds like this guidance is relatively new
and/or unofficial at this
"The EF team is now focused on the EF Core 3.1 release, which is planned
for later this year, and on making sure that the documentation for EF Core
3.0 is complete." *1
"It needs to be clearly stated somewhere that EF 6.3 is meant only as a
tool for migrating from .NET Framework, and that EF Core
Mike King wrote:
>
> Sorry to chase an answer but is there any plans to support Entity
Framework
> Core in the roadmap? As I understand it the current version of EF6 is
> probably going to be the last and it's likely that MS is going to
recommend
> people move over to Core.
>
Given that Entity
Hi,
Sorry to chase an answer but is there any plans to support Entity Framework
Core in the roadmap? As I understand it the current version of EF6 is
probably going to be the last and it's likely that MS is going to recommend
people move over to Core.
Cheers,
Mike
On Fri, 15 Nov 2019 at 00:02,
Hi All,
I can see System.Data.Sqlite supports Entity Framework 6. Are there any
plans to support Entity Framework Core?
Apologies if this is a basic question!
Cheers,
Mike
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
7 matches
Mail list logo
