i'm trying to add mysql connection to my asp.net mvc 4 projects but i dont see it on the data source window.
after installing visual studio 2012 express for web i added mysql Connector/Net through nuget. i wanted to add new connection to mysql db but i did see mysql data source on the data source window list. after a search i realized that i have v6.6.4 and it supported from 6.6.5 so i uninstalled it from nuget and install 6.6.5 from mysql website(a complete install). it didnt helped.. i also tried to uninstall and reinstall it but it didnt change a thing.
how can i solve this?
Adding Connector/NET thru nuget will not install any of the visual studio integration stuff, for that you will need to run the Connector/NET installer (available at http://dev.mysql.com/downloads/connector/net/).
However due to legal constraints from Microsoft, integration with Visual Studio express editions is not possible (you'll need a non express version of visual studio).
The problem is that its an express version.
i installed a non express version and it worked.
Related
I've installed the followings
PowerBI desktop
PostgreSQL
Npgsql v4.1.1 (from https://github.com/npgsql/Npgsql/releases)
Visual Studio 2019 (community)
Even after installing all the above, still I am getting
This connector requires one or more additional components to be installed before it can be used.
Is there anything else, I've to install?
I've re-installed the Visual Studio 2019 and it works.
I've read numerous articles and posts here about getting Entity Framework to work with DB2 but all of them reference prior versions of Visual Studio. When I repeat the steps outlined (too many to remember at this point), I still do not have DB2 in the data providers list.
Has anyone gotten this to work in VS17 and, if so, can you walk me through what you did?
For registering IBM Database Add-Ins for Visual Studio 17, Visual Studio 2015 or earlier supported versions needs to be installed on the machine.
Steps:
Download and install IBM Data Server Driver Package
Download and install IBM Database Add-Ins for Visual Studio.
After successful installation of IBM Database Add-Ins, choose Start -> IBM Database Add-Ins for Visual Studio ->Register IBM Database Add-Ins.
This link has listed the steps needed for the add-in installation
https://www.ibm.com/developerworks/community/blogs/96960515-2ea1-4391-8170-b0515d08e4da/entry/VSAIFORVS2017?lang=en
Note: Make sure to download same version and fix pack of DS Driver and VS IBM Database Add-In. I downloaded v11.1.3fp3 version for both installations and it's working for me.
I want to connect sqlite using EF6 in VS2017.
I installed "System.Data.SQLite" nuget package.
I also installed "sqlite-netFx46-setup-bundle-x86-2015-1.0.104.0.exe" from http://system.data.sqlite.org, but I cannot see the sqlite provider when adding ADO.NET data entity.
Am I missing something? or the above package not supporting VS2017 (it said it is for VS2015)
There is no DDEX provider package for VS 2017 (yet). https://system.data.sqlite.org/index.html/tktview?name=8292431f51
Basically you need to wait for: sqlite-netFx46-setup-bundle-x86-2017-1.0.1xx.0.exe
"Official" update:
The current estimate is that support for Visual Studio 2017 will
be included in the 1.0.106.0 release, which should be released at
some point in the mid-June timeframe.
mistachkin added on 2017-05-28 20:41:40: At this point, it seems unlikely that I'll be able to add VS 2017 support for the design-time components (e.g. table designer, entity wizard, etc).
UPDATE: I have created a DDEX provider that enables SQLite support (for EF6 only) in Visual Studio 2017, see the how-to guide here: https://github.com/ErikEJ/SqlCeToolbox/wiki/EF6-workflow-with-SQLite-DDEX-provider
The issue was solved after installing SQLite/SQL Server Compact Toolbox.
Please try. https://marketplace.visualstudio.com/items?itemName=ErikEJ.SQLServerCompactSQLiteToolbox
The VS 2017 installer is really a pain in the b***.. Installing packages via an automated deployment works, but detecting installation state and such is near to impossible..
Seems like microsoft devs finally got sick of msi packages and implemented their own installer / package manager for VS2017, as other teams did for Office 365 and such..
According to the url provided by the sqlite-netFX46-bundle-win32-2015-1.0.108.0 intaller log : https://system.data.sqlite.org/index.html/info/8292431f51119807241632b092774e60189018d9 Visual Studio 2017 support isn't available yet
I tryied many things without any result, the worst is that I installed also a VS 2015 but cannot install because of the VS 2017 installation on my computer.
This tool looks promising when I went through the available information on website. But when I downloaded free version and when I am trying to install in my local I came across the following error.
OPS-008: OpsHub Visual Studio Migration Utility requires Team Foundation Server 2012 Update 1 Object Model or above.
Do I need to install this software on the server ? No where I could find instructions for installing this software.
Can I get this explained please, we are planning to migrate our project to VSTS.
If you want to migrate from TFS on premise to VSTS, I would suggest you to evaluate which of the three options listed by Microsoft documentation suite your need.
The easier way would be to chose option 2, especially if you already have TFS2015update3 or TFS 2017, as you need to upgrade your TFS collection to one of those version anyway before migrating (and you save the upgrade hassle).
If you want to use OpsHub tool, then you need to install the standalone TFS Object Model for TFS 2012 update 4 where you run the OpsHub tool, not on any of the TFS servers.
In order to run OVSMU, you will have to install TFS Object Model 2012 on the machine where you are installing the tool. This is a pre-requisite and be rest assured this version of OM will not conflict with any other (newer) version of Object Model already existing (which comes bundled with Visual Studio installer) on that machine.
What would be the most frictionless workflow for working with NuGet and Visual Studio 2005? Is this at all possible? I understand that the plugin is only available for Visual Studio 2010, but there is still the package manager console wich seems to be nothing more than powershell. Can I run the console without Visual Studio and can the console download and integrate packages into visual studio 2005 projects? If so, how is this done?
Scott Hanselman blogged about adding NuGet "support" to Visual Studio 2008. You can probably adapt this slightly to work in Visual Studio 2005 too, though of course you won't get the same experience as in Visual Studio 2010.
Well, not really. A better title would be "How to Cobble Together
NuGet Support for Visual Studio 2008 with External Tools and a
Prayer." The point is, there are lots of folks using Visual Studio
2008 who would like NuGet support. I'm exploring this area and there's
a half-dozen ways to make it happen, some difficult and some less so.
The idea would be to enable some things with minimal effort. It'll be
interesting to see if there are folks in the community who think this
is important enough to actually make it happen. Of course, the easiest
thing is to just use 2010 as it sill supports .NET 2.0, 3.0, 3.5, and
4, but not everyone can upgrade.
Someone could:
Backport the existing NuGet Package References dialog to 2008 using
that version's native extensions (not VSiX)
Create MEF (Managed
Extensibility Framework) plugins for the nuget.exe command-line to
update the references in a vbproj or csproj
Use PowerShell scripts and
batch files to get the most basic stuff working (get a package and
update references.)
Maybe write a shim to get DTE automation
working...
But that's coulds and maybes. Let's talk about the MacGyver
solution. more ยป