Bug #92440 mysql 8.0 and VS 2017 - editing trigger fails with 'unable to load object'
Submitted: 15 Sep 2018 21:02 Modified: 17 Sep 2018 12:39
Reporter: guenter strubinsky Email Updates:
Status: Verified Impact on me:
Category:MySQL Visual Studio Integration Severity:S3 (Non-critical)
Version:8.0 OS:Microsoft Windows
Assigned to: CPU Architecture:Any

[15 Sep 2018 21:02] guenter strubinsky
When trying to alter a trigger (before-insert) VS2017 fails with the message:
'unable to load object with error:
[a]mysql.data.mysqlclient.mysqlconnection cannot cast to [b]mysql.data.mysqlclient.mysqlconnection
Typpe A originates from 'mysql.data version=,,, in the context 'default' at location F:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\PrivateAssemblies\mysql.data.dll
Typpe B originates from 'mysql.data version=,...,,, in the context 'default' at location C:\Windows\Microsoft.NET\assembly\GAC_MSIL\MySql.Data\v4.0_8.0.12.0__c5687fc88969c44d\mysql.data.dll'.

There are obviously two different versions trying to exchange data that are not compatible. I uninstalled mysql-for=vs and reinstalled it. I uninstalled the .net  mysql driver and reinstalled it. Both are 32bit versions on a 64bit mysql svr and a 64bit vs107 installation.(?)

Trying to alter a stored procedure shows no error message but does not open an edit window.
The objects (all of them including SPs and triggers) appear in the object tree (left).

I did not find entries in the locations in event viewer that seemed to be prone to hold such info.

How to repeat:
[17 Sep 2018 12:22] Miguel Solorzano
Thank you for the bug report.
[17 Sep 2018 12:39] guenter strubinsky
Could you duplicate it?