Bug #90491 | Cannot install MySQL for Visual Studio 1.2.7 | ||
---|---|---|---|
Submitted: | 18 Apr 2018 8:59 | Modified: | 18 Apr 2018 11:55 |
Reporter: | John Gorst | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Visual Studio Integration | Severity: | S3 (Non-critical) |
Version: | 2017 Community Edition | OS: | Windows (Windows 7 64bit) |
Assigned to: | CPU Architecture: | Other (i7) |
[18 Apr 2018 8:59]
John Gorst
[18 Apr 2018 10:51]
Chiranjeevi Battula
Hello John Gorst, Thank you for the bug report. This is most likely duplicate of Bug #88745, please see Bug #88745 Thanks, Chiranjeevi.
[18 Apr 2018 11:55]
John Gorst
In response to the suggested bug fix Thank you for the bug report. This is most likely duplicate of Bug #88745, please see Bug #88745 I have reviewed this bug and it appeared that the solution was to delete the file privateregistry.bin. I deleted this and was able to install MySQL for Visual Studio. However, Visual Studio would no longer start. It seems the MySQL installer has installed its own version of privateregisty.bin. I deleted the new version and was able to run Visual Studio. When adding an ADO.Net Entity Data Model, MySQL was not available as a data source. I successfully installed the Connect/Net connector. I have tried removing MySQL for Visual Studio using the MySQL installer and it has failed. I have tried removing it using the control panel and it has also failed.