dashpax.blogg.se

NET Framework Data Provider for ODBC as the data source on the Choose a Data Source or Choose a Destination page. To connect with an ODBC driver, start by selecting the. ODBC drivers aren't listed in the drop-down list of data sources. After you enter individual values for the MySQL server name ( Server) and login info, the wizard assembles the connection string from the individual properties and their values.Ĭonnect to MySQL with the MySQL ODBC driver

You don't have to enter the connection string in the ConnectionString field of the list. Net Framework Data Provider for MySQL property That is, the options you see are the same on both the Choose a Data Source and the Choose a Destination pages of the wizard. In the past MySQL officially didn't support Visual Studio Express, as per answer below, but they do officially support Visual Studio Community 20, according to this page.The connection options for this data provider are the same whether MySQL is your source or your destination. The OP asks whether MySQL is supported with Visual Studio Express (which as far as I can tell has been renamed to Visual Studio Community). I found the solution here, Thanks to about Visual Studio Express Install the Connector first, then VS plugin after.

The solution for me was to uninstall the Connector and the Visual Studio Plugin, download them as individual components, and then install them separately (not as part of the MySQLServer Installer). The installer I used included the VS Plugin version 1.2.9, which had supposedly fixed installation issues from 1.2.8, but still didn't work for me. When I installed MySQL Community with the ConnectorNET and VisualStudio Plugin options included - MySQL didn't show up as a data provider in Visual Studio.

Supposedly another way is to register the MySql Connector with various Visual Studio versions (2010/2012/2013/2015.) during installation: Go to Modify Product Features and select all the relevant Visual Studio versions. I uninstalled the latest ones because I figured they were somehow related to. I solved it by uninstalling the latest Connector/NET drivers (6.7.4) and then installed the older drivers (6.6.5) and it works.