LinqPad Error: Unable to find the .Net Framework Data Provider

Question

I am new to LinqPad.

I downloaded a .sdf file from the internet (i know what it is) I wanted to view its tables. So I googled "how to read .sdf files" and came across Linqpad, which I installed.

When I browse to my .sdf file from LinqPad and try to open it as a connection, I get the message "Unable to find the requested .Net framework data provider, it may not be installed"

Does this mean i need to install SQL CE before using LinqPad? I assumed LinqPad was the program to view tables, run queries, etc and that I did not need the original db program.

Please advise on what the error refers to and best way to resolve. thanks

Answer 1

To answer your question, yes you do have to install it. I just ran across this problem while trying to connect to a Sql CE 3.5 DB in LinqPad. You have to have the proper version installed first. I only had 4.0 installed and was trying to connect to a 3.5 DB. So had to use the SSCERuntime msi found here to install the items shown below:

Just go to that link and download it somewhere and then run the msi(s). Note the following:

It is mandatory to install both the 32-bit and the 64-bit version of SQL Server Compact MSI files on a 64-bit Computer. Installing only the 32-bit version of the SQL Server Compact 3.5 SP2 MSI file on a 64-bit computer will lead to failure of the existing SQL Server Compact 3.5 applications on the Computer.

So just follow the instructions shown in the "Install.txt" that is downloaded with the msi's.

After installing them I had to close and reopen LinqPad and then the connection worked.

Answer 2

I'll add a variant on Kasper's solution. For the case of connecting to SQL CE 4, I appeared to already have the SQL CE4 runtimes installed yet I still got the same error.

Trying to install the latest SQL CE 4 from Microsoft reported that a newer version was already installed and aborted the install. Uninstalling the "newer version" and then installing the latest download fixed the problem for me.

I'm not sure how I got that original version, that's "newer" than the latest from Microsoft. Possibly from an older Visual Studio install.