![mysql for visual studio 1.2.8 mysql for visual studio 1.2.8](https://i.stack.imgur.com/RKlff.png)
- Mysql for visual studio 1.2.8 .dll#
- Mysql for visual studio 1.2.8 install#
- Mysql for visual studio 1.2.8 drivers#
- Mysql for visual studio 1.2.8 download#
I am not sure if this is caused by the previous install spams from me)Īnd I mean this is in the DEVELOPER GUIDE WHICH CAUSED AT LEAST 1 DAY OF THINKINGĪre you aware that you Guide the developer to update his app.config file at STEP 1 then YOU SUGGEST TO USE Nudget package installer at STEP 2.
Mysql for visual studio 1.2.8 .dll#
dll files from the connector to:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.7.2" (I had to overwrite then and it was a must have step for some reason. I installed the " MySql for visual studio 1.2.8" still with the error. Removed Latest version of Connector/Net and installed What i figured out that for some reason the "latest version of the Connector/Net 8.0.11" wasnt working with windows 7.Īlso worth to mention the MySql for visual studio 1.2.8 even tho it threw an error at installing it kinda installed itself. A S Okay so I solved the problem after like 4 days. For this you'll need to modify your project file directly (e.g. when you build the appx package, etc., you can override only the layout directory instead of the entire output path. If you still want normal output to live next to the sources, e.g. Right-click on the project and change the output directory to something like: $(Temp)$(MSBuildProjectName)bin$(Configuration), where Temp is an environment variable pointing to your Temp directory.
![mysql for visual studio 1.2.8 mysql for visual studio 1.2.8](https://i.ytimg.com/vi/DbjdE9EHsD8/maxresdefault.jpg)
You can still work with sources on a network drive, but you'll have to override the deployment location, which by default is under the project's root directory (e.g.
![mysql for visual studio 1.2.8 mysql for visual studio 1.2.8](https://live.staticflickr.com/1978/44863071062_6e4090f5c5.jpg)
Yes, it's by design that you cannot run a Metro app from a network drive and deployment from Visual Studio essentially registers the app with the system without actually packaging and installing it (so it doesn't get put into the normal install location, which is local). Hopefully this comes in handy for anyone else developing over a network share:
![mysql for visual studio 1.2.8 mysql for visual studio 1.2.8](https://knihyzacal.com/xrlove/84Sf_zlIG0pfoFkILjwU-AHaEs.jpg)
This post by Gearard Boland solves this issue. 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 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.
Mysql for visual studio 1.2.8 download#
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.
Mysql for visual studio 1.2.8 drivers#
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.