Bug #85908 Community Edition Installer can't find Visual Studio 2017
Submitted: 12 Apr 2017 1:27 Modified: 9 Feb 2018 18:40
Reporter: Jerry Stuckle Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Visual Studio Integration Severity:S2 (Serious)
Version:5.7 OS:Microsoft Windows
Assigned to: CPU Architecture:Any

[12 Apr 2017 1:27] Jerry Stuckle
Description:
Visual Studio 2017 Community Edition is installed and running normally.  However, MySQL Windows installer doesn't recognize it, saying "Visual Studio 1.2.6 has Failing Requirements.  Visual Studio version 2010, 2012, 2015 or 2017 must be installed."

How to repeat:
Install Visual Studio 2017 (on this system it is installed on the E: drive).  Attempt to install MySQL 5.7 Community Edition using the Windows installer file (mysql-installer-community-5.7.18.0.msi).  Install the "Developer Default", "Full" or "Custom" version (the last manually selecting "MySQL for Visual Studio 1.2.6") and attempt to install.   
"MySQL for Visual Studio 1.2.6" shows status as Manual, when you place the cursor over it, a popup window shows the message "Visual Studio version 2010, 2012, 2015 or 2017 must be installed.".
[12 Apr 2017 2:12] MySQL Verification Team
I was able to install it on Windows 10 Pro with server 5.7.18 already installed:

1: Action 23:09:46: RollbackCleanup. Removing backup files
1: 1: MySQL for Visual Studio 1.2.6 2: {D885AD96-9178-4CF2-836C-33AE57A57427} 3: 1 
1: The action 'Install' for product 'MySQL for Visual Studio 1.2.6' completed successfully.
[12 Apr 2017 2:54] Jerry Stuckle
Which version of Visual Studio do you have installed?  This is Visual Studio 2017 Community Edition (on Windows 7 Pro).
[12 Apr 2017 9:14] Chiranjeevi Battula
Hello Jerry Stuckle,

Thank you for the feedback.
I could not repeat the issue at our end using with Visual Studio 2017 Community with Visual Studio 1.2.6/7 versions.

Pre requirements user manual:
https://dev.mysql.com/doc/visual-studio/en/visual-studio-install.html

Thanks,
Chiranjeevi.
[12 Apr 2017 13:38] Jerry Stuckle
Ok, more information.  When I added .NET development to Visual Studio (we only develop cross-platform - C/C++, Java, etc. No .NET), MySQL did detect Visual Studio.  The message could be more clear on this.
[13 Apr 2017 8:14] Chiranjeevi Battula
Hello Jerry Stuckle,

Thank you for the feedback.
I could not repeat the issue at our end using with Visual Studio 2017 Community with Visual Studio 1.2.7 and C/Net 6.9.9 versions.
If you can provide more information, feel free to add it to this bug and change the status back to 'Open'.

Thank you for your interest in MySQL.

Thanks,
Chiranjeevi.
[13 Apr 2017 8:15] Chiranjeevi Battula
Database Connection

Attachment: 85908_1.JPG (image/jpeg, text), 116.26 KiB.

[13 Apr 2017 8:15] Chiranjeevi Battula
Screenshot

Attachment: 85908_2.JPG (image/jpeg, text), 171.15 KiB.

[15 Apr 2017 1:34] Jerry Stuckle
Of course you can't repeat the problem.  Did you read my comment?  It occurs when you do NOT have .NET development installed in Visual Studio 2017.  In this case the message is not at all clear.

And I am unable to change the status to open, but would like to have it reopened and fixed properly.
[19 Aug 2017 1:47] Rex Thorpe
I had exactly the same issue...I down loaded the smaller version of the MySql installer for Visual Studio(Not the full installer) and now My Visual Studio 2017 Community has MySql Database connection available...
[26 Aug 2017 23:35] Amy Wilson
Thank you, Jerry.  That resolved my problem.
[27 Aug 2017 0:16] MySQL Verification Team
https://bugs.mysql.com/bug.php?id=87550 marked as duplicate of this one.
[31 Aug 2017 13:49] Michael Leih
I'm having the same issues.  I have added the .Net Developer module to Visual Studio 2017 Community, but I am still unable to load the MySQL for Visual Studio using either the web installer of the full download installer.  

I open another bug report, but it was closed as a duplicate to this one.  However, there seems to be no solution to the issue for me.  

I am using Visual Studio 2017 Community version 15.3.3 and the MySQL MSI Installer version 5.7.19

I have attempted the installation on two different computers running Windows 7, but neither will allow for the installation of the MySQL for Visual Studio.

Does anyone know what specifically the MySQL Installer is looking for to verify that Visual Studio is installed?  There might be a work around if I could create what it is looking for until the MySQL Installer is fixed.  

For those doing the testing that cannot repeat this issue, I recommend that you do not use a machine that has never had an older version of Visual Studio installed on it.  I suspect that some have not been able to replicate the problem because something has been added during the installation of an older version of Visual Studio.
[31 Aug 2017 17:38] Tersoo Atsen
Hi Jerry Stuckle, what exactly is .NET development? Are you referring to MS .Net v4? I have that installed but it doesn't resolve this problem.
[31 Aug 2017 17:52] Søren Ramus
I can repeat this issue.
Just make a clean windows 10 install with Visusal Studio Community.
And You are stuck
[31 Aug 2017 18:13] Jerry Stuckle
Tersoo Atsen It is the development libraries and tools for .NET.  They are not the same as the runtime libraries, which are only required to run .NET applications.  .NET development tools are required to create .NET applications.
[6 Sep 2017 2:08] Matthew Mills
I had the same problem. MySQL installer did not detect that I had installed Visual Studio. So I downloaded and installed the patch at this link https://dev.mysql.com/downloads/windows/visualstudio/ and then the MySQL installer was able to detect Visual Studio.
[6 Sep 2017 17:04] Søren Ramus
I dont see any patch at 
https://dev.mysql.com/downloads/windows/visualstudio/

I have tried MySQl installer Web Community 5.7.18.1 - no success Visual studio Community 2017 not detected

Mysql for visual studio 1.2.7 + MySql Connector net 6.9.9 - partial success. But EF6 not useable.
[8 Sep 2017 0:20] Mark Schumann
As with Søren, I don't see a patch file there. I'm having the same problem as the others: Visual Studio runs fine, but the MySQL installer won't install the Visual Studio plugin.

Visual Studio 15.3.3
.NET Framework 4.7.02053
MySQL For Visual Studio 1.2.7

Also tried with MySQL for Visual Studio 2.0.5
Also tried from the Web Installer 5.7.19.0
[9 Sep 2017 21:29] Stuart Binder
Rex (above) has a good workaround. 
After installing MySQL using the recommended method ("MySQL Installer for Windows"), use the "Windows (x86, 32-bit), MSI Installer" located lower on the <a href="https://dev.mysql.com/downloads/windows/visualstudio/"> Download MySQL for Visual Studio page</a>. page. This installs only the MySQL for Visual Studio components, and will succeed even when the general installer fails.
[9 Sep 2017 22:40] Søren Ramus
@Stuart

You're right. The installer runs to end without errors.
But Entity Framework still does'nt work. At least not EF6.

MySQL for Visual Studio seems to be at bit crappy.

regards
[11 Sep 2017 12:39] Mark Schumann
Not here.

The MSI installers (both 1.2.7 and 2.0.5) get all the way to "Publishing Product Information" and perhaps one other step that flashes too quickly to read. Then they roll back to the error dialog: "MySQL for Visual Studio ended prematurely..."

If you can't fix this right away, fine, but can Oracle simply tell us what it is that the installer is looking for? A file, a registry key, a DLL, what?
[18 Sep 2017 14:33] Shaun Gosse
Hi,

Just adding to the chorus of replication here. I hit this as well, already had .net components, installed everything .net I could for visual studio, still didn't work.

I did the direct installer as mentioned (installer below the mega-installer), and it seems to have worked, although I haven't verified it yet.

I would rate this as a critical issue: can't install; that seems important. It also seems highly repeatable by customers, might be worth looking at again.

But we can't reopen it, so at least chiming in here so anyone else who finds this thread while trying to get started, as I did, will know they aren't alone.
[22 Sep 2017 15:45] Adam Smith
I have come across this bug too after initially installing Visual Studio Community 2017. Even after modifying the install to include .NET desktop development module, the MySQL installer couldn't find Visual Studio. Only after downloading MySQL for Visual Studio 1.2.7 and installing did the MySQL installer find Visual Studio.

Seems like this is bug is coming up often. I only figured out how to work around this when I Google'd the issue and came across the bug with instructions for the work around.
[22 Sep 2017 17:53] M B
it stopped working when I made an update to visual studio 15.3.5 community edition.
I'm working on Windows 7 Ultimate x64 fully updated.
I tried to uninstall both all mysql components and visual studio, installers included. then I installed again visual studio community edition (with .net 4.7 framework and all .net components for desktop development) and then I tried again to install mysql client components using the mysql installer, but again it can't find visual studio installed. I tried to use the msi installer, but it ends with an error and doesn't install it.
I can't reinstall the PC, since there are a lot of software on it
[22 Sep 2017 19:59] M B
I updated visual studio 2017 community to 13.3.5 (the last update) on a Windows 10 pro x64 PC. on that PC mysql had not been installed.
Then I downloaded mysql installer and I've tried to install MySql for visual studio , but it  can't find visual studio and doesn't let mi install it.
probably a problem with the last update?
I need to use it and Entity Framework, so if it's not possible to correct the bug I'll have to go back to MS SQL Server.
[24 Sep 2017 13:53] M B
MySQL Installer log with errors for MySQL for VS 2017

Attachment: MYSQL FOR VISUAL STUDIO 2017 INSTALLER ERROR.txt (text/plain), 16.79 KiB.

[27 Sep 2017 5:27] Chiranjeevi Battula
http://bugs.mysql.com/bug.php?id=87877 marked as duplicate of this one.
[29 Sep 2017 9:22] Chiranjeevi Battula
http://bugs.mysql.com/bug.php?id=87902 marked as duplicate of this one.
[2 Oct 2017 7:17] L V
According to MB's log file, is it possible 'MySQL for VS' doesn't create the proper registry key for VS Community? 

Although the installer recognises the directory (C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\...), it seems it doesn't create the key for Community version, just for Enterprise and Professional:

1: Action 15:43:06: CreateRegKeyAndExtensionsFile_VS2012. 
1: Action 15:43:06: CreateRegKeyAndExtensionsFile_VS2013. 
1: Action 15:43:07: CreateRegKeyAndExtensionsFile_VS2015. 
1: Action 15:43:07: CreateRegKeyAndExtensionsFile_VS2017_Ent. 
1: Action 15:43:07: CreateRegKeyAndExtensionsFile_VS2017_Pro.
[7 Oct 2017 5:11] Noah Wingate-Dolph
Can verify this is still an issue. Visual Studio Community 2015. Did not detect that VS was insatlled and had to use the standalone installer for MySQL for Visual Studio.
[7 Oct 2017 10:02] M B
Sorry, I tried with the mysql for visual studio installer, too, but it doesn't work. it rolls back.
[10 Oct 2017 5:28] Chiranjeevi Battula
Hello  Jerry Stuckle,

Thank you for the bug report.
Verified based on internal discussion with dev's.

Thanks,
Chiranjeevi.
[10 Oct 2017 5:30] Chiranjeevi Battula
http://bugs.mysql.com/bug.php?id=88000 marked as duplicate of this one.
[10 Oct 2017 15:21] M B
I installed Visual studio 15.4 update, but there's no change.
Don't you know any workaround for this problem?
[11 Oct 2017 6:14] Γεώργιος Βλάχος
Hello,

Yesterday i encountered the same problem.
Visual Studio 2017 installed in my coumputer and when i tried to install MySQL for Visual Studio , the installer couldn't locate the Visual Studio installation with the error
"Visual Studio 1.2.6 has Failing Requirements.  Visual Studio version 2010, 2012, 2015 or 2017 must be installed."

I solved it by downloading and installing mysql for visual studio 1.2.7 for the address below:
ftp://ftp.gwdg.de/pub/linux/mysql/Downloads/MySQL-for-VisualStudio/mysql-for-visualstudio-...

This solved the problem for me.

Hope I helped.
[15 Oct 2017 13:13] M B
I formatted the computer and reinstalled everything 
In order I installed
- Windows 7 Ultimate, from the original copy of the computer as arrived form the manufacturer
- all the updates and service pack (it took nearly one day and one night!)
- Office 2016 Pro Plus and its updates
- Visual studio 2017 community 15.4.0
- downloaded MySQL Installer 5.7.19 from "https://dev.mysql.com/downloads/installer/"
- MySQL Installer 5.7.19. 
- I launched MySql Installer, and it updated (?) and then started
I tried the "Custom" installation, and when I choose  Applications/MySQL for Visual Studio/MySQL for Visual Studio 1.2/MySQL for Visual Studio 1.2.7 it is grey and it shows the message 1.2.7 has failing requirements. Visual Studio Version 2012, 2013, 2015 or 2017 must be installed
If I open MySQL Installer - About it says it's version 1.4.20.0

Don't you think this is a critical problem?
[15 Oct 2017 13:22] M B
I tried with the MySL for Visual studio installer, downloaded both from https://dev.mysql.com/get/Downloads/MySQL-for-VisualStudio/mysql-for-visualstudio-1.2.7.ms... and from ftp://ftp.gwdg.de/pub/linux/mysql/Downloads/MySQL-for-VisualStudio/mysql-for
-visualstudio-1.2.7.msi . Both rolled back with errors (see previous messages)
[15 Oct 2017 21:41] Søren Ramus
I have now abandoned mySql for. Net.
Installed SQL server. Everything works without problems.
[15 Oct 2017 21:41] Søren Ramus
I have now abandoned mySql for. Net.
Installed SQL server. Everything works without problems.
[16 Oct 2017 19:50] Amir Alfoly
Hello,

I was able to solve the problem.

The setup searches for a specific key in the registry to check if Visual Studio exists or not. You can manually create the key "VS" to complete the path as I did in my case and the setup will recognize the Visual Studio version and install the MySQL Visual Studio Component successfully.

The key that the setup checks for is:
For Visual Studio 2010
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\10.0\Setup\VS

For Visual Studio 2012
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\11.0\Setup\VS

For Visual Studio 2015
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\14.0\Setup\VS

For Visual Studio 2017
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\15.0\Setup\VS

Hope that this helps, waiting for feedback.
[16 Oct 2017 20:12] M B
hello Amir,
I tried and now the installer sees Visual Studio, but it can't install MySQL for Visual Studio. It rollbacks at 90 %.
I think I'll go back to SQL Server
[17 Oct 2017 1:12] Vince Bucchare
Hello, I have this same exact problem. Windows 7, multiple versions of Visual Studio installed, MySQL installer did not detect Visual Studio. Tried the standalone installer, it fails with the error below. Tried the registry work-around, which did make the installer find VS, but the install still failed.

I don't have the option of moving to SQL Server, so I would really appreciate a solution to this issue.

MSI (s) (78:7C) [20:41:53:197]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI4E9A.tmp, Entrypoint: WixQuietExec
WixQuietExec:  Error 0xffffffff: Command line returned an error.
WixQuietExec:  Error 0xffffffff: QuietExec Failed
WixQuietExec:  Error 0xffffffff: Failed in ExecCommon method
CustomAction VS15Setup_Custom returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 20:41:53: InstallFinalize. Return value 3.
M
[17 Oct 2017 20:23] Edward Rothman
Clean install windows 10 10.0.1563 Visual studio 2017 cannot install developer version of mysql
[26 Oct 2017 20:42] Hamad Q
I just solved this on 
Windows 8.1, 
and Visual Studio 2013

by installing "MySQL connector 6.9.10" instead of latest 6.10.4
and installing "MySQL for Visual Studio 1.2.7" instead of latest 2.0.5

Latest releases have bugs i guess. It's working perfectly fine now!

(few guys were reporting MySQL not working in VStudio after installing MySQL for VS 1.2.7. It is because i think they have connector 6.10. 
Connector 6.10 DOES NOT work with "MySQL for vs 1.2.7". For details,
https://dev.mysql.com/doc/visual-studio/en/visual-studio-install.html)
[2 Nov 2017 0:12] Guy Jackman
I had the same problem with being unable to successfully unstall.  On a new machine I had Windows 10 and Visual Studio 2017.4.0 (Enterprise).  I was trying to get the Visual Studio tooling installed for MySQL.  When using the MySQL installer, it wouldn't even allow me to proceed because it didn't detect any Visual Studio version at all.  When I tried to use the standalone msi for MySQL for Visual Studio, it would succeed, but there were not MySQL connection options showing up in VS when using the Entity Framework designer (edmx).

This is what worked for me, but I think there are probably multiple combinations that would work.

First, to make the "MySQL Installer", I used Amir Alfoly's suggestion that adding a VS key in the registry would force a proper detection of VS.
As Amir stated (THANK YOU!), the key that the setup appears to check for is:
For Visual Studio 2017
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\15.0\Setup\VS

See his comment above for other VS versions.

This, by itself didn't help with the entity framework designer situation in Visual Studio.  To make that work, I then had to explicitly install mysql-connector-net-6.9.10.msi, NOT the most recent version which appears to be 6.10.4 which is included in the MySQL installer.

Summary:
- Add the reg. key for Visual Studio.  In my case:  "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\15.0\Setup\VS"
- Install using "MySQL Installer", but ONLY install the "MySQL for Visual Studio" component.  Do NOT install the "Connector/Net" component!
- Download and install the "Connector/NET" V6.9.10.  "mysql-connector-net-6.9.10.msi"  Download here:  https://dev.mysql.com/downloads/connector/net/6.9.html
[2 Nov 2017 0:21] Guy Jackman
Sorry.  It looks like some of what I just posted was previously noted by Hamad Q.

In the link he refers to (https://dev.mysql.com/doc/visual-studio/en/visual-studio-install.html), it does say that for both V1.2 and V2.0 of 'MySQL for Visual Studio', the following:
 "Some features require C/Net 6.9"

Apparently "Some features" include the EDMX support in VS!
[3 Nov 2017 6:05] Chiranjeevi Battula
http://bugs.mysql.com/bug.php?id=88338 marked as duplicate of this one.
[3 Nov 2017 6:06] Chiranjeevi Battula
http://bugs.mysql.com/bug.php?id=88334 marked as duplicate of this one.
[8 Nov 2017 13:46] Pierrick MARTELLIERE
Hi,

I made the three steps of Amir, so I can install mysql for visual studio but at the end of the install it rolls back.
Help please since I can't add MySQL Connection to my Model.
I'm using VS 2017 EF6. Since I installed MySQL connector 6.9, my Entity Data Model Designer is working well, but when I choose "Update Model From Database" it asks me to add a new connection and I don't have MySQL Database. Please help since this is kinda urgent and I tried every workaround and accepted solutions that didnt work. I'm basically stuck.
[8 Nov 2017 16:39] Pierrick MARTELLIERE
In the install log, it displays the key Registration for Visual Studio_Pro but not for Enterprise and I have Enterprise...
[17 Nov 2017 10:25] Stefan Winterstein
Same problem here: the install of "MySQL for Visual Studio" is failing and rolling back.

However, this is happening with VS 2017 Professional.

Also kinda urgent, I cannot generate the database from my model...

Would the installer log help?
[21 Nov 2017 5:49] Andrew Benham
Amir's registry fix allowed me to install "MySQL for Visual Studio 1.2.7".

I'm using both VS2017 Enterprise and VS2015 Enterprise on Windows Server 2016 Standard.

After that I installed Connector/NET 6.9.9.

No failures, simply no MySQL project templates in either version of Visual Studio.
[21 Nov 2017 9:37] Stefan Winterstein
Still doesn't work for me. It keeps getting stuck at 93%, then rolls back.

As the log references other VS versions maybe that's important: In addition to VS2017 Pro, VS2013 Pro is still installed on my machine. VS2015 has been, but has been uninstalled.

Here's the end of the log:

1: Action 10:18:13: InstallFinalize. 
1: Action 10:18:13: DeleteRegKeyAndExtensionsFile_VS2015. 
1: Action 10:18:13: DeleteRegKeyAndExtensionsFile_VS2012. 
1: Action 10:18:13: DeleteRegKeyAndExtensionsFile_VS2017. 
1: Action 10:18:14: DeleteRegKeyAndExtensionsFile_VS2017_Ent. 
1: Action 10:18:14: VS12_UpdatePackageFile. 
1: Action 10:18:14: VS2013Setup.       <------------------------ hangs here, then rollback:
1: Action 10:18:58: VS15_Pro_Setup_Custom. 
1: Action 10:18:58: Rollback. Rolling back action:
1: VS15_Pro_Setup_Custom
1: VS2013Setup
1: VS12_UpdatePackageFile
1: DeleteRegKeyAndExtensionsFile_VS2017_Ent
1: DeleteRegKeyAndExtensionsFile_VS2017
1: DeleteRegKeyAndExtensionsFile_VS2015
1: DeleteRegKeyAndExtensionsFile_VS2012
1: Action 10:18:59: Rollback. Rolling back action:
1: Publishing product information
1: Publishing Product Features
1: Registering product
1: Updating environment strings
1: RegisterPerfCounterData
1: RollbackRegisterPerfCounterData
1: Writing system registry values
1: Creating shortcuts
1: Copying new files
1: Creating folders
1: Updating component registration
1: CreateRegKeyAndExtensionsFile_VS2017_Ent
1: CreateRegKeyAndExtensionsFile_VS2017
1: CreateRegKeyAndExtensionsFile_VS2015
1: CreateRegKeyAndExtensionsFile_VS2012
1: 1: MySQL for Visual Studio 1.2.7 2: {63F92630-4546-4297-A0F5-761886A689EE} 3: 3 
1: The action 'Install' for product 'MySQL for Visual Studio 1.2.7' failed.
[29 Nov 2017 21:16] Evrim Alözkan
I have finally solved it.

Step-1: Add the reg. key for Visual Studio. "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\15.0\Setup\VS"

Step-2: Install the latest "MySQL for Visual Studio..."

Step-3: Install the latest "MySQL connector..."

If still can't use "Import MySql.Data"
Step-4: 
Visual Studio 
  -> Project 
    -> Project Properties 
      -> References 
        -> Add 
          -> Browse 
            -> Browse 
              -> Browse 
                -> "MySql Installation Directory"\MySQL Installer for Windows\MySql.Data.dll
                  -> Save, OK, etc.
!VOILA!

(my client language is not English. Some translation mistakes can occur)
[5 Dec 2017 11:52] Chiranjeevi Battula
http://bugs.mysql.com/bug.php?id=88745 marked as duplicate of this one.
[6 Jan 2018 7:55] Anmol Bishnoi
i have same problem as i have installed a community version of the visual stdio, my sql installer is not not able to find it
[15 Jan 2018 5:02] Chiranjeevi Battula
http://bugs.mysql.com/bug.php?id=89227 marked as duplicate of this one.
[16 Jan 2018 14:56] Thorsten Hojnacki
This could be a problem with the Extension Installer and the new private registry for Visual Studio 2017.

See here:
http://www.visualstudioextensibility.com/2017/07/15/about-the-new-privateregistry-bin-file...

"At run-time, the devenv.exe process of Visual Studio 2017 redirects registry operations on Visual Studio keys to the privateregistry.bin file. So, this change is transparent for extensions (DLLs) that run in the devenv.exe process. Setups (which are external processes) are not so lucky. While they could use the RegLoadAppKey function to write to the 15.0_<instance-id> key for per-user extensions (never for 15.0_<instance-id>_Config, which would be overwritten later), it is much better to switch to .pkgdef files on disk (either per-machine, or per-user)."
[17 Jan 2018 8:26] Stefan Winterstein
Intersting point! Is there anything I as a user can do to work around the current this problem?

And will somebody from the team take notice, please?

Right now, I' still unable to use MySQL with my VS.
[18 Jan 2018 21:59] Arnold Anka
After 5 full work days and a reinstall of win 7 pro sp1 i finaly got it working. EF 5 and connector 6.9.9. Not EF 6 though yet.

No real help from mysql team, thanks for that... This bug is a project killer so its bad if its not solved soon.

This is what finaly did it. (thanks to writers above and other forums that gave clues)

1 move %localappdata%\Microsoft\VisualStudio\<config>\privateregistry.bin
2 dont login to visual.
3 install 1.2.7 mysql for visual studio
4 install connector 6.9.9
5 put the privateregistry.bin back

I used mysql-installer-community-5.7.17.0 to get the 6.9.9 connector net.
mysql-installer-web-community-5.7.20.0 to get the 1.2.7 mysql for visual studio

Then it will work with EF 5.
I also created the /setup/vs keys but dont think it made any difference. Just saying if anyone have the same problem.

Connectors above 6.9.9 just wont work with community edition.

Since this file is where devenv reads the user regestry the problem most likely is that the installer only reads the register where older visual wrote the keys.
So when the mysql team tries to replicate they have the old keys in the register i guess.

If someone at mysql team bother to read this i think it will make sence to start here.

I hope this helps other developers.
[25 Jan 2018 23:50] Michael Ahrndt
here is the relevant download link for v. 6.9.9
https://downloads.mysql.com/archives/c-net/
[26 Jan 2018 13:45] Stefan Winterstein
I can confirm that Arnold's did the trick - thanks Arnold!

It even worked for me using EF 6 (VS 2017 Pro).

Apart from that: a real project killer indeed...
[7 Feb 2018 15:53] Pedro Dias
Hi there,

Ok, I have 2 diferente problems regarding MySql and Visual Studio:

1st problem is with VS community 2015 that don't allow me to connect to any mysql server because it doesnt apper in the menu Tools->Connet to Database

2nd is on the VS professional 2017, that can let me connect to the MySql server but when tried to open the database design it opens a strange error: "Some updating commands could not be generated automatically. The databse returned the following error: Unexpected error." and I hit OK, and a information appears saying: " could not retrieve schema information for the table or view contactos".

I have the latest versions of the mysql connector and visual studio tool both for vs2015 and 2017.

Can anyone give me a hand with this problems? I have a lot of developments with MySql databases and was thinking on moving them from the vs2015 to the vs2017.

but now none of them works :(

Best regards,
Pedro Dias
[9 Feb 2018 1:15] Andrew Amundrud
HOW IS THIS RATED NON_CRITICAL?

I guess the ability to install software is not considered important...

Waste of time. And no, I didn't get it working after many hours of trying.q
[9 Feb 2018 7:48] Pedro Dias
Hi Andrew,

Yes it's important but you do not need to be rude when replying to a post.

I used a open issue and not creating a new one but I think that you know that it's not possible to change the severity on a issue created by other.

Despite of everything, thank you for your reply.

Best regards,
Pedro Dias
[9 Feb 2018 18:40] Jerry Stuckle
I opened this bug and set it at Non-critical because that was it's status for me.  It was a nice tool to have but not a critical piece to the project I was working on.
[10 Feb 2018 19:17] Andrew Amundrud
Yes, I am sorry for over-reacting.

I am new to MySQL (and developing in general).

The learning curve is often frustrating.

For now I will forget about EF.
[19 Feb 2018 12:12] Chiranjeevi Battula
http://bugs.mysql.com/bug.php?id=89708 marked as duplicate of this one.
[7 Mar 2018 7:20] Chiranjeevi Battula
http://bugs.mysql.com/bug.php?id=89935 marked as duplicate of this one.
[19 Mar 2018 12:28] Thorsten Hojnacki
When marking other bugs with severity "critical" as a duplicate if this one, the severity of this bug should be also changed to "critical".
[13 Apr 2018 7:51] Danny Cheung
Arnold Anka's Solution work for my case. Thanks 

1 move %localappdata%\Microsoft\VisualStudio\<config>\privateregistry.bin
2 dont login to visual.
3 install 1.2.7 mysql for visual studio
4 install connector 6.9.9
5 put the privateregistry.bin back
[9 Aug 2018 12:20] stefan auckland
I am having the same issue I have Visual C++ 2017 redistributable, not full VS.
the log states:
"1: Action 13:11:41: INSTALL. 
1: 1: MySQL Workbench 8.0 CE 2: {3D4D54C3-6D4E-435F-8894-2125D900822C} 
1: Action 13:11:41: FindRelatedProducts. Searching for related applications
1: Action 13:11:41: AppSearch. Searching for installed applications
1: Action 13:11:41: SetWIX_IS_NETFRAMEWORK_45_OR_LATER_INSTALLED. 
1: Action 13:11:41: LaunchConditions. Evaluating launch conditions
1: MySQL Workbench requires the Visual C++ 2015 Redistributable Package to be installed. Click the Download-Button on the next page to open a web page containing further instructions.
1: 1: MySQL Workbench 8.0 CE 2: {3D4D54C3-6D4E-435F-8894-2125D900822C} 3: 3 
1: The action 'Install' for product 'MySQL Workbench 8.0.12' failed."

Visual 2015 will not install if a later version is already installed.

workaround would be to;
stop Visual C++ 2017 dependant programs,
remove Visual C++ 2017 Redistributable,
install Visual C++ 2015 Redistributable,
install 'MySQL Workbench 8.0.12',
run 'MySQL Workbench 8.0.12' (need to run and close before updating to 2017),
close 'MySQL Workbench 8.0.12',
re-install Visual C++ 2017 Redistributable.

(also affects MySQL Router, Connector/C++, and Connector ODBC)

This is more than bothersome and should certainly be critical and fixed
[9 Aug 2018 12:23] stefan auckland
MySQL Installer log with errors for MySQL for Visual C++ Redistributable 2017

Attachment: MySQL_Visual_CPP_2017_Redist_installerr.PNG (image/png, text), 34.91 KiB.

[9 Aug 2018 13:12] MySQL Verification Team
https://bugs.mysql.com/bug.php?id=91953 marked as duplicate of this one.
[31 Aug 2018 4:23] MySQL Verification Team
Bug #92248 marked as duplicate of this one
[5 Nov 2018 21:34] MySQL Verification Team
https://bugs.mysql.com/bug.php?id=93087 marked as duplicate of this one.
[26 Dec 2018 2:41] qiang wen
I use the latest version of uninstaller to clean up visual studio 2013 from windows 10.
then I installed visuals studio 2017 enterprise and mysql for visual studio 1.2.8
but mysql for vs 1.2.8 failed to be installed(always prompted by "visual studio 2012, 2013, 2015 must be installed)
I googled all the solutions on the internet. none of them can solve my problem

finally I found a solution:
open registry to search mysql for visual studio in HKEY_LOCAL_MACHINE
deleted searched item for "mysql for visual studio 1.2.6"
then problem solved.

so uninstaller should deleted that registry item automatically.
[26 Dec 2018 2:42] qiang wen
I use the latest version of uninstaller to clean up visual studio 2013 from windows 10.
then I installed visuals studio 2017 enterprise and mysql for visual studio 1.2.8
but mysql for vs 1.2.8 failed to be installed(always prompted by "visual studio 2012, 2013, 2015 must be installed)
I googled all the solutions on the internet. none of them can solve my problem

finally I found a solution:
open registry to search mysql for visual studio in HKEY_LOCAL_MACHINE
deleted searched item for "mysql for visual studio 1.2.6"
then problem solved.

so uninstaller should deleted that registry item automatically.
[12 May 2020 13:10] MySQL Verification Team
Bug #99362 marked as duplicate of this one
[18 Sep 2020 23:25] Anirudh Sharma
Okay, so this issue was solved for me when I repaired my Visual C++ redist. And now mySQL Workbench works fine too   here's what you need to do..

Go to 'add or remove programs' in start menu, find the Visual C++ redist > click modify > repair. This needs to be done separately for each if you have both x32/86 and x64 installations. Reboot PC after this step and it should work fine.
[12 Jun 19:05] Eimantas Kanasevicius
2021 and same issue still persist... MySQL team working hard on this bug... great job...
[3 Sep 12:47] MySQL Verification Team
Bug #104800 marked as duplicate of this one
[1 Oct 9:19] Bjoern Smith
Same problem here with Workbench 8
Even after installation VS Redis 2019 32bite and 64bit, the installation was stopped with the message, it was not installed.

After running the installation as administrator - the installation was successful.
I opened a command shell as administrator and started the installer (msi) from there.

I hope it helps users and the installer maybe changed to ask for admin rights.
[1 Oct 9:19] Bjoern Smith
Same problem here with Workbench 8
Even after installation VS Redis 2019 32bite and 64bit, the installation was stopped with the message, it was not installed.

After running the installation as administrator - the installation was successful.
I opened a command shell as administrator and started the installer (msi) from there.

I hope it helps users and the installer maybe changed to ask for admin rights.