MySQL Forums
Forum List  »  MySQL for Visual Studio

Re: Visual Studio 2019 support
Posted by: Grigore Dolghin
Date: April 18, 2019 06:19AM

Well, I couldn't just leave, it was personal.

Eventually I made it work and I am writing here my findings, maybe they'll help someone else.

My projects were using MySQL 5.7 + MySql Connector .NET 6.10.8 + MySQL for Visual Studio 2.0.5. They were working fine under VS2017.

I installed VS2019 on the same machine, side-by-side, however, I couldn't make it work. (read my previous message in thread).

I don't have a second computer, so I used a virtual machine. Windows 10 + VS2019 + MySQL 8.0.15 + MySql Connector .NET 8.0.15 + MySQL for Visual Studio 2.0.5. Yep, I had to use a different version of MySQL Server (that's more overhead added to upgrade process, but oh well).

After installing everything listed above, I could create a database connection to MySQL from Visual Studio but the Entity Framework part in existing projects still didn't work (could not update model, and so on).

After digging a bit I have found that the guys have changed the name of EF provider. (!!!!!)

Previous setting was:
======================
<providers>
<provider invariantName="MySql.Data.MySqlClient" type="MySql.Data.MySqlClient.MySqlProviderServices, MySql.Data.Entity.EF6" />
</providers>
======================

After upgrading to MySQL Connector .NET 8.0.15 the setting is
======================
<providers>
<provider invariantName="MySql.Data.MySqlClient" type="MySql.Data.MySqlClient.MySqlProviderServices, MySql.Data.EntityFramework" />
</providers>
======================

So eventually I could make the thing work, but I have to use a separate machine for that. Swell.....

Options: ReplyQuote


Subject
Views
Written By
Posted
2186
April 08, 2019 04:34AM
1418
April 10, 2019 08:03AM
1334
April 15, 2019 09:49AM
1198
April 18, 2019 04:31AM
Re: Visual Studio 2019 support
8078
April 18, 2019 06:19AM
1269
May 26, 2019 05:58PM
119
August 07, 2019 02:22AM


Sorry, only registered users may post in this forum.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.