Sqlite not in list of Visual Studio data source options - visual-studio-2010

Downloaded and ran SQLite setup.
Added dll reference to my project
In Server Explorer, added new connection, clicked 'Change' for data source and SQLite was one of the options.
Connected and used my tables.
Then...VS 2010 crashed.
When I reloaded my project, my connection wasn't in Server explorer, so tried to add it again.
SQLite was not in the list of options.
Re-ran SQLite setup, deleted/re-added reference, restarted project...still no SQLite in the list.
How can I get SQLite connected in Server Explorer???

This is an old question but for someone, like me, who finds this before there is a newer answer:
missing SQLite data provider in VS 2013
Basically for the latest versions of SQLite you can download an installer that includes the components
http://system.data.sqlite.org/index.html/doc/trunk/www/downloads.wiki
Choose the right setup for you, for me was:
Setups for 32-bit Windows (.NET Framework 4.5.1)
sqlite-netFx451-setup-bundle-x86-2013-1.0.94.0.exe

I have Windows 7 x64 with Visual Studio community 2015 and this solution worked for me.
Basically you need install SQLite bundel and check the "Install the designer component for Visual Studio 2015".
If you have different version from 2015 (2010/2013 etc.) just search for the bundle the suits your version.
1. Go to:
http://system.data.sqlite.org/index.html/doc/trunk/www/downloads.wiki
2. Download "sqlite-netFx46-setup-bundle-x86-2015-1.0.104.0" (download the most updated, this is the one I found).
Or by a direct link:
http://system.data.sqlite.org/downloads/1.0.104.0/sqlite-netFx46-setup-bundle-x86-2015-1.0.104.0.exe
3. Run the setup:
4. Result:

You can find installers on the System.Data.SQLite Dowload Page. Seteps files will suit your needs.
For example, the description of the Setups for 64-bit Windows (.NET Framework 4.0) states:
This setup package features the mixed-mode assembly and will install all the necessary runtime components and dependencies for the x64 version of the System.Data.SQLite 1.0.81.0 (3.7.12.1) package. The Visual C++ 2010 SP1 runtime for x64 is included. The .NET Framework 4.0 is required.

None of answers worked for me. in addition to #E235 answer
i added sqlite nuget package
updated ef to 6.1.3
then it worked i was able to see datasource

Related

WCF Data Services, WindowsAzure.Storage and Microsoft.Data.OData version nightmare

I am using Visual Studio 2015 (Pre), Framework 4.5.2
I have the folowing project structure
StorageProject
nuget package Microsoft.WidowsAzure.Storage is installed
This Nuget package has (among others) dependencies on Microsoft.Data.OData, wich is also installed
AnotherProject
Has a refernce on StorageProject
Does not have any nuget package or other refernces (except default references on the framework)
Here is the list of the packages installed in StorageProject
WindowsAzure.Storage 4.3.0
Microsoft.WindowsAzure.ConfigurationManager 3.1.0
System.Spatial 4.3.0
Microsoft.Data.Edm 5.6.4
Microsoft.Data.OData 5.6.4
Microsoft.Data.Services.Client 5.6.4
These are all dependencies of WindowsAzure.Storage, latest versions.
There is no other version of these packages installed anywhere on the solution.
I will focus on Microsoft.Data.OData, but the same problem occurs with Microsoft.Data.Edm and Microsoft.Data.Services.Client 5.6.4
When building StorageProject, the correct version of these dll (5.6.4) ends up in the bin folder of the project.
But when building AnotherProject, the bin folder contains version 5.6.2 of the dll.
Now I passed all day trying to figure out where these dlls come from.
There is a version 5.0.0.0 in the GAC, wich I cannot uninstall. (gacutil yields it is used by something).
I did a file search on C:\ to find that the only place where this version of the dll is (beside the bin folder of my project) is in C:\Program Files (x86)\Microsoft WCF Data Services\5.6.2. If I delete (move) this folder, my project builds "normally" and everything is fine. In fact, in this case OData is not in the bin folder at all. And as far as I am concerned, that's ok this way.
Now the real question(s) :
Why is it the version from Microsoft WCF Data Services that ends up in the bin, instead of the version actually installed in the referenced project?
Where does Microsoft WCF Data Services comes from ? I don't remember installing it at all, maybe it comes with a version on Visual Studio? (I have 2012, 2013 and 2015 installed)
Can I uninstall it? I don't see it in Windows' control panel.
•Why is it the version from Microsoft WCF Data Services that ends up in the bin, instead of the version actually installed in the referenced project?
This could be due to the fact that the storage client does not depend on a specific version of the Data Service Client. Since Specific Version is set to false, the GAC will be searched first during compilation, any version will be considered "acceptable", and no other version will be exported.
•Where does Microsoft WCF Data Services comes from ? I don't remember installing it at all, maybe it comes with a version on Visual Studio? (I have 2012, 2013 and 2015 installed)
It could be installed due to a variety of reasons. The Azure SDK contains this as well. So if you ever installed the Azure SDK, it could have come with that.
•Can I uninstall it? I don't see it in Windows' control panel.
Looks like this is only possible by uninstalling the MSI package that installed the assembly via Add/Remove programs. For that, you would have to again figure out which installation brought this assembly with it and check whether that is needed or not.

Visual Studio 2013 connection with Firebird

Though this is not programming specific problem, I hope this is also the right place to ask this.
I'm having problems using Firebird DB with Visual Studio.
I had previously installed FirebirdClient v4.2.0.0 and DDEX v3.0.1.0, but in my project I used newest version of client and there was a mismatch between the two when adding new ADO.net models (connection in Databases window was working perfectly fine).
So I uninstalled the v4.2 and installed newest version (4.6.2.0), but now when I try to add new connection:
Visual Studio 2013 Pro crashes after entering one letter into any of the textboxes:
I tried:
relaunching VS
reinstalling both FirebirdClient v.4.6.2 and DDEX v.3.0.1
but nothing seems to help. Anything I missed I can do to make this work?
I had also downloaded some NuGet packages, but since I even tried this with closed solution I don't suppose this is project-related issue.
Some further notes:
I've read about GAC and the need of adding the assemblies into it, but as far as I understand, in the newest versions of Firebird .Net Provider it is done automatically
My specs:
Win 8.1 Pro
VS Pro 2013
Firebird 2.5.2
FB .Net Provider 4.6.2
DDEX 3.0.1
I had the same Problem and the solution was to uninstall the DDEX 3.0.1 and FB.Net Provider. Remove all Firebird entries from the machine.config provider section. Reinstall both and it should work again, the uninstaller of the Provider doesn't remove this entries so Visual Studio crashes.
The machine config is located under:
32-bit
%windir%\Microsoft.NET\Framework[version]\config\machine.config
64-bit
%windir%\Microsoft.NET\Framework64[version]\config\machine.config

Oracle development tools for visual studio not installing [duplicate]

Having installed managed ODP.NET on my computer, the ODP.NET Managed Driver does not appear inside the Choose Data Source dialog in Visual Studio 2013 Professional.
This is how it should look like:
This is how it actually looks on my machine:
I've followed the steps described in the "An Easy Drive to .NET" article on the Oracle website.
I've also installed the Oracle Developer Tools for Visual Studio. Still no managed driver to select.
My question:
Is there anything I forgot to do in order to make the data provider appear?
The generic answer to this question is "(Re)install 'Oracle Developer Tools for Visual Studio' (ODT)". Simply getting ODP.NET from Nuget or from other sources is not enough to take advantage of Visual Studio integration. You must install ODT also.
Download "ODTwithODAC":
http://www.oracle.com/technetwork/topics/dotnet/utilsoft-086879.html
Update 4/2018: If you are using Visual Studio 2017 Community edition, please upgrade to version 12.2.0.1.1 or later. That is the first version that works with VS 2017 CE: http://www.oracle.com/technetwork/topics/dotnet/downloads/odacmsidownloadvs2017-3806459.html
As you noticed, sometimes installations get munged. So if you do not see the driver in the dialogs or are getting generic (non-oracle ORA-) errors when you try to use features then you should reinstall ODT.
Open your Registry editor and check if RegKey HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319\AssemblyFoldersEx\odp.net.managed exists. It contains only the (Default) value with location of your Oracle.ManagedDataAccess.dll.
Add the key in case it is missing, example:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319\AssemblyFoldersEx\odp.net.managed]
#="c:\\oracle\\product\\12.1\\odp.net\\managed\\common"
You can also try the Oracle config scripts at {ORACLE HOME}\odp.net\managed\x64\configure.bat and {ORACLE HOME}\odp.net\managed\x86\configure.bat, they should do the same
Then check your compile options whether you selected target Framework at least to .NET Framework 4.
Update for Release 12.2
Key odp.net.managed seems to be used in old version 12.1. Latest release uses Oracle.ManagedDataAccess:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319\AssemblyFoldersEx\Oracle.ManagedDataAccess]
#="C:\\oracle\\product\\12.2\\Client_x64\\odp.net\\managed\\common"
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319\AssemblyFoldersEx\Oracle.ManagedDataAccess.EntityFramework6]
#="C:\\oracle\\product\\12.2\\Client_x64\\odp.net\\managed\\common\\EF6"
While Wernfried posted his answer I tried at the same time the following approach:
Uninstall any previously installed Oracle packages/drivers.
Restart Visual Studio.
After these steps, the drivers were present:
I'm still not 100% sure, why a simple uninstall fixes something.
Old post but same issue. THe root cause is - i think - if you have VS 2022 installed the ODT for VS 2017 or 2019 does not install properly. I had to uninstall all versions of VS, reinstall VS 2017, reinstall ODTwithODAC183. Ensure that it can actually find the latest version of VS 2017 - I used the Visual Studio installer and it installed the latest version of VS 2017 Pro. I think that made a difference too. It looks like otherwise the installer won't find VS 2017 properly (if 2022 is installed) and the whole thing is fubar.
To test if it's installed correctly, add a entity data model and you should be able to see the oracle option in the data source list.
I has same error. Since I installed vs2015 Update 3.
solve
Reinstall Oracle Developer Tools for Visual Studio 2015.
http://www.oracle.com/technetwork/topics/dotnet/downloads/odacmsidownload-2745497.html
ref
https://community.oracle.com/thread/648192

missing SQLite data provider in VS 2013

I'm using VS 2013 to develop Win 8.1 app. I chose to deal with SQLite but I coudn't find the data provider when I was trying to add a new connection to manage my database.
Any help is appreciated
Install this:
http://system.data.sqlite.org/downloads/1.0.101.0/sqlite-netFx46-setup-bundle-x86-2015-1.0.101.0.exe
and reboot evertything
I have lost 3 hours with this problem
Updated with new version.
Updated with sanuel-jackson's comment info.
http://system.data.sqlite.org/index.html/doc/trunk/www/downloads.wiki
and download Setups for 32-bit Windows (.NET Framework 4.5.1) where
This is the only setup package that is capable of installing the design-time components for Visual Studio 2013.

Deploying VS2010 SP1 using .NET 4 bootstrapper

I recently updated Visual Studio 2010 to SP1 and noticed the .NET 4 framework changed from version "4.0.30319.1" to "4.0.30319.225". I was not able to locate an updated .NET 4 framework installer for "4.0.30319.225". I could only find an update exe which is used to update a particular machine. When I deploy my application now, it still uses the older pre-SP1 version of the framework.
Is there a new bootstrapper that I should be using? Are there any issues with deploying an application that is developed/tested on "4.0.30319.225" to a target machine which only has "4.0.30319.1" ?
According to a comment on Announcing Visual Studio 2010 Service Pack 1 (check page two of the comments) from Jason Zander:
There have been questions about
updates to the .NET Framework. There
is no full service pack for .NET
Framework 4. However there is an
update which you can download from
here: go.microsoft.com/fwlink. The
outline of fixes (linked from the
download page) is here:
support.microsoft.com/.../2468871.
This update is titled "Microsoft .NET
Framework 4 KB2468871". You can read
more about what is in the update on
the download page.
As I mentioned in a previous comment,
VS2010 SP1 requires this update and
will automatically install it as part
of setup.
When you build a project using VS2010
SP1, it does not force a dependency on
the update. Whether you need to
deploy the update with your client or
server application depends on your
need for the fixes in the update. You
will need to look through what it
contains to make that call.
I've personally seen no issue publishing to a server before running the update manually.
I can't speak to the bootstrapper question.

Resources