SQLite with EF Code First

Question

After my success using SQLite with NHibernate, I am very happy to use it for testing with Entity Framework Code First.

If you have some example connections string and set up demos, that would be great and save a bit of time from my hectic day.

Thanks a lot.

EDIT:

Worth mentioning that I am getting this error during debugging when applying crud actions via the EF "data context":

Unable to determine the provider name for connection of type 'System.Data.SQLite.SQLiteConnection'.

<system.data>
    <DbProviderFactories>
        <remove invariant="System.Data.SQLite"/>
        <add name="SQLite Data Provider" invariant="System.Data.SQLite" description=".Net Framework Data Provider for SQLite"
   type="System.Data.SQLite.SQLiteFactory, System.Data.SQLite" />
    </DbProviderFactories>
</system.data>


<connectionStrings>
    <add name="DataContext"
         connectionString="Data Source=:memory:;Version=3;New=True;"
         providerName="System.Data.SQLite"
     />
</connectionStrings>

Hopefully EF does integrate with SQLite in this fashion. Although the error message, alarmingly, suggests probably not.

Could you solve your problem already?

codymanix
– codymanix

2011-05-23 10:26:15 +00:00
Commented May 23, 2011 at 10:26 — codymanix
– codymanix, Commented May 23, 2011 at 10:26

Max Toro · Accepted Answer · 2011-03-26 05:18:55Z

6

You need to use the assembly qualified name:

<add name="SQLite Data Provider" 
     invariant="System.Data.SQLite" 
     description=".Net Framework Data Provider for SQLite" 
     type="System.Data.SQLite.SQLiteFactory, System.Data.SQLite, Version=1.0.66.0, Culture=neutral, PublicKeyToken=db937bc2d44ff139" />

answered Mar 26, 2011 at 5:18

Max Toro

28.7k11 gold badges81 silver badges116 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

oo_dev Over a year ago

And the connection string?

DamienG · Accepted Answer · 2017-10-24 16:08:47Z

5

Code First should work just fine with any ADO.NET 3.5 level provider (these implement Entity Framework functionality).

The 4.0 capable providers also add DeleteDatabase/CreateDatabase/DatabaseExists functionality.

Code First requires no additional provider functionality beyond these.

What happens is that it looks at the type of the Connection and then tries to map that back to the provider and its provider factory so it can create everything else it needs.

It would be worth checking to make sure you have an up-to-date SQLLite provider installed in your GAC that supports the 3.5 level functionality.

edited Oct 24, 2017 at 16:08

answered Dec 29, 2010 at 18:46

DamienG

6,6841 gold badge30 silver badges43 bronze badges

Collectives™ on Stack Overflow

SQLite with EF Code First

2 Answers 2

1 Comment

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

1 Comment

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related