System.Data.SQLite

This information is current as of the 1.0.25.1 release, which is currently pending.

The SQLite provider itself works just fine using all the various Visual Studio 2005 Express Editions.  However, only Visual Web Developer Express Edition supports design-time extensibility.  For all other Express Editions that restrict you to designing for Jet or Sql Express, you have to drop one of those two in order to get SQLite's designer to work.  This is because most of the Express Editions filter the available providers by the GUID in the registry ... so SQLite needs to use one of the only two "permitted" GUID's.

I'm writing a setup utility to take care of installing and uninstalling design-time support for all editions of Visual Studio Express.  It'll have an uninstall as well so you can revert at any time.

Robert

 

I know that EEditions have limited plugin capability, but would it be possible to make designer support for SQL Management Studio?
IF SQL Management Studio supports something like Visual Studio extensibility.

I don't have much experience with the new management studio so I couldn't say for sure.  I am fairly confident however, that it has little or no extensibility support for 3rd party databases.

Robert

 

Bumping, since I edited the original post to reflect some new information.

Robert

 

::does happy wombat dance::

Ok, Im getting this weird error

DB explorer right click -> Add Connection

Datasource : Click Change

Select "SQLite Database File", Click 'OK'

Enter my connection string into the Box(I know the connection string is valid) click OK

Message box: "Failed to find or Load the Registered .Net Framework Data Provider"

I can sucessfuly "test connection"

Sounds like the provider isn't registered in the global assembly cache.  The install.cmd file (or the installvwdexpress.cmd file) should've installed the library in the GAC.  Go to Administrative Tools->Microsoft .NET Framework Configuration and check the assembly cache for System.Data.SQLite.  If its not there, add it.

Robert

 

Ok, It looks like this may have been a versioning issue.  1.0.23.xxx was installed.  I Updated it to reflect the more recent version and now it works.