My question is similar to this one but the crash happens later. I must interoperate an EF database-first model between SQL Server and MySQL. More specifical
Well I can tell you that connector 8.0.xxx and all of the 8.0.xxx dll's that MySQL has put out for MySql Server 8 are a complete bust.
There has been a major bug out https://bugs.mysql.com/bug.php?id=91030&thanks=3¬ify=195 for over a year now.
If your trying to work with MySql 8.0 many of the connectors and libraries will give you an error....
"The provider did not return a ProviderManifestToken string."
It is a testament to the absolutely sub zero level of visual studio support, documentation, testing and basic development skill applied in the mysql dll's connector and documentation that I have spent the last 40 hrs of my waking life trying to put together a working model to get my application to connect with MySql 8.0.16 and to have a working entity framework wizard. At this point I am almost wishing I developed it using SQL Server.
I am using a variant of ASP.NET Identity 2.0 and this is what I would get back when trying to log in
"The provider did not return a ProviderManifestToken string."
Anyway here is what I got to work for me.
This is something I got to work with Server 8.0 on Windows 10 that does a connection and allows log in with ASP.NET Identity 2.0 and will at least run the Data Entity Wizard to completion.
Install Connector / Net 6.10.7
DLL's
c:..\EntityFramework.6.2.0\lib\net45\EntityFramework.dll
C:..\EntityFramework.6.2.0\lib\net45\EntityFramework.SqlServer.dll
C:..\MySql.Data.6.10.7\v4.5.2\MySql.Data.dll
C:..\MySql.Data.6.10.7\v4.5.2\MySql.Data.Entity.EF6.dll
Web.Config
I hope this helps some people out there but I have a funny feeling your mileage may vary.