Trying to generate the entities with VS2013 using MYSQL connector/net 6.8.3.0 but it shows me the above error. Following are the screenshots of installed applications list and Nuget package manager.
Please help me to fix this.
MYSQL EF6 is having a new dll "MySql.Data.Entity.EF6.dll". Refer this dll in your assembly, rebuild the application and try again to generate the entities.
Related
UWP App not being able to work with MySql
I have made an app in UWP and instead of using SQLLite which seems to be the norm for Visual Studio 2015 I want to use MySql. I have already connected my Azure mysql database to Visual Studio via the 'Server Explorer'.
I'm using MySQL Workbench to update my tables within my connected database from Azure but I cannot actually write any code to access my tables as whenever I try to install MySql.data/.entity/etc in the NuGet Package Manager I get an error.
nuget error
I tried downloading the Mysql installer, the Mysql drivers for Ado and ODBC. I even tried downloading the MySql for Visual Studio option as I found out that Visual Studio is not compatibile with MySql and instead requires the MySql for Visual Studio download but I still have errors whenever I try to use MySql in my code as I need an assembly reference for it but I'm having no luck in being able to get one that doesn't error.
Does anybody have any idea how I could actually use MySql within Visual Studio 2015?
This is what I've been using as my guideline but I can't seem to get past the Mysql.data errors when installing.
http://web3.codeproject.com/Articles/1074242/Designig-your-Azure-MySQL-DB-with-a-UWP-Demo
I have seen a lot of people talk about this but there is no one straightforward fix (I've tried a lot of the fixes, one in particular being to use Vs13 to install Mysql in the Nuget package manager and then it should update within VS15 but as my app is a UWP VS13 does not actually load/read it so that idea isn't good to me, might help anyone else though)
Starting with 6.7, Connector/Net fully supports building Windows Store apps. But using Connector/Net RT is not by install the Nuget package, it just reference the MySql.Data.RT.dll assembly according to MySQL Connector/Net Developer Guide:
Using Connector/Net RT is easy. Simply create a Windows Store application using Visual Studio and then reference the MySql.Data.RT.dll assembly in your project. The code you write should be exactly the same as for normal Connector/Net (including using same namespace MySql.Data.MySqlClient) except for the differences listed above.
You may find this dll at C:\Program Files (x86)\MySQL\Connector.NET 6.79\Assemblies\RT if you have install the connector. You can also download the mysql-connector-net-6.7.9-noinstall.zip to find this file inside the folder. I also have a MySql UWP sample before and has the dll here. Right click your project and add reference for this it will work.
More details please reference this sample
I googled about this topic but I don't really find a solution :
I try this method : I installed in my vs2013 these tools :
MySQL for Visual Studio 1.1.1
MySQL Connector/Net
I Installed also, using NuGet, all MySql library or tools. But I'm still not find the MySql Provider.
So I need to know How can I fix this issue?
You can add the reference for the required package MySql.*.dll
This helped me:
stackoverflow mysql connector
I use visual studio 2010-12 and I installed ADO.NET Entity Framework 4.1 , Mysql .Net Connector and Mysql Workbench
Before formatting, my computer, I could use entity framework for MySQL. but not I cant see MySQL in data source list. Here is what I mean
Well...where is the my mistake or missing?
Try uninstall existing mysqlconnector.
Download mysqlconnector/net 6.5.6
It works with VS2010 on my desktop.
However, id you're using vs2012, you may try the
latest version.
Okay I solved, I opened server explorer and I connected to mysql database, after I tried to add an ado.net entity framework object and it works
We're trying to update our WiX installer to install SQL Server 2008 R2. Regular 2008 seemed to install fine on most machines, but the R2 install seems to fail to install SQLSysClrTypes - so we hit an error with a missing dll called SQLServerSpatial.dll.
Is there a way to get the SQL installer to correctly install this? I have found some discussions of this issue online but no solutions, except for manually installing SQLSysClrTypes.msi after SQL Server.
We want the install to be silent and need the minimum of user interaction.
We're using WiX 3.5 & VS2010.
Edit
Further reading and thinking leads me to understand that SQL 2008 SP1 didn't install SQLServerSpatial.dll either, and it is changes to our code which have made this a requirement now. So my question has become simplier:
Can I configure the SqlServer install to include/install SqlServerSpatial?
or
Can I use WiX to install SQLSysClrTypes.msi (I would need the package.xml and product.xml)? Has anyone done this?
While I am unsure about the changes to SQL Server and why SqlServerSpatial.dll is missing, I can answer with regards to installing prerequisites using a bootstrapper.
Can I use WiX to install SQLSysClrTypes.msi (I would need the package.xml and product.xml)? Has anyone done this?
It sounds like you are using the visual studio bootstrapper. You can use the bootstrapper manifest generator tool to create the bootstrapper manifest (package.xml and product.xml) so that you can create a bootstrapper like you would for other prereqs (for example, the .NET framework).
Of course, if you are open to upgrading to WiX 3.6 (still in beta but pretty stable), you may use the new bootstrapper functionality called Burn to create package bundles in order to chain your packages together.
Does any one know how to connect to MySQL 5.1 with Visual Studio 2010?
I have already tried the MySQL Connector/ODBC route and it got me really nasty results. The table rows were all listed as a view in the views section and nothing at all was listed in the tables or procedures folder.
To get the Entity Frame working with VS2010, I had to do the following:
This only worked with Mysql .net Connector v6.3.1 (alpha). Previous versions ignored VS 2010 (click Development Releases)
I had to rename my Framework\v1.1.4322\CONFIG folder. Otherwise the install will fail. Rename it back when finished
(I've blogged about this here)
Update
6.3.2 is in beta and I can confirm this works. (I didn't need to rename the framework folder)
this seems to solve the issue
UPDATED LINK TO LATEST RELEASE THANKS #Christian Payne
Update: looks like there is already a non-beta!!!!
http://www.mysql.com/downloads/connector/net/
As someone else suggests..
http://dev.mysql.com/downloads/mirror.php?id=382641
..fixes the problem.
I had v6.2.3 installed after I had vs2010 installed and the MySQL driver was not shown in the list of the Database Connect dialog. I wrongly assumed I should use the .NET ODBC drivers instead and it caused all sorts of problems. Although I could easily connect to the DB using codebehind, the server explorer wouldn't connect to the DB.
Luckily after uninstalling 6.2.3 and installing 6.3.0 (from the link above) the MySQL driver was added to VS2010, and I was able to connect to the database and see it in my server explorer.
http://bugs.mysql.com/bug.php?id=45122
I was able to get this to work by doing the following:
My Environment:
Development Box -- Win7 64bit,
VS2010 Pro
Deployment Box -- Win2k8 svr with IIS7
running ASP.NET .Net 2.0/3.0/3.5 sp which is
hosted at DiscountAsp.Net (Note:
DiscountAsp.Net does not provide a
MySQL DB when running on a Win2k8
svr, I'm using a MySQL DB that I connect
to elsewhere on the InterWebs)
Steps I took:
Installed MySql.Data, Version=6.3.6.0, Culture=neutral, PublicKeyToken=c5687fc88969c44d
Ref'd the .Net 2.0 version of the MySQL assembly in my ASP.NET MVC2 Web project set to target .Net 3.5 (the path for the MySQL assemblies I used was C:\Program Files (x86)\MySQL\MySQL Connector Net 6.3.6\Assemblies\v2.0)
I ref'd all 3 of the MySQL assemblies (MySql.Data.dll, MySql.Data.Entity.dll & MySql.Web.dll)
I marked each of those assemblies as "Copy Local=True" in my project (a.k.a bin deployment)
Added a MySQL DB connection string to my Project (using the MySQL provider)
Added an ADO.NET Entity Data Model to my project in VS2010 using the connections string
VS2010 took about 30 secs to chew thru my MySQL DB schema but then provided me with a beautiful GUI interface to tweak my MVC Models
Used the DB Entities in my MVC controllers
Deployed the app to my hosted server at DiscountAsp.Net
It works like a charm :)
Erm... through code? Or do you mean the server explorer add-in? Have you tried the latest (albeit GPL-ed) connector version for .NET from Mysql themselves? Again, it's GPL-ed so be aware of the consequences of using that for your own software.
Microsoft Visual Studio 2010 Beta 2 is busted for DDEX providers. They are auto promoting a VS 2008 assembly from 9.0 to 10.0 and it fails. The failure has to do with the fact that a .NET 2 assembly cannot load a .NET 4 assembly.
This worked in beta 1, so it is something they broke.
I even went back and tried the reference DDEX provider from the SDK. It won't load in VS 2010 beta 2 either. That tells me they have something that needs to be fixed.
When is the next beta?