Bug #72050 | installer-community-5.6.16.0 fails to detect newer version of Visual Studio Tool | ||
---|---|---|---|
Submitted: | 15 Mar 2014 19:52 | Modified: | 7 Oct 2015 8:16 |
Reporter: | John Rourke | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL for Windows: Installer | Severity: | S3 (Non-critical) |
Version: | 5.6.16.0 | OS: | Windows (Windows 7 Enterprise SP1 X64) |
Assigned to: | Assigned Account | CPU Architecture: | Any |
Tags: | installer fails, Visual Studio |
[15 Mar 2014 19:52]
John Rourke
[29 Mar 2014 2:28]
radha fournier
I am having the same problem. Please fix this ASAP, as this is critical to the running of our radio station.
[16 Jan 2015 19:35]
Anderson Yamamoto ander182
I am having the same problem but with mysql-installer-community-5.6.22.0 I am using Windows 7 and Office 2010. The installer lists as pendency the Mysql for visual studio 1.2.3 (that should be included in the installer) If I download it and install manualy the MySQL won´t be listed in ODBC avaliable drivers. The list of softwares for uninstall after that is MySQL server (64), MySQLfor VS (32) and the connector ODBC (64). Did you get to solve this on your computer? thanks!
[29 Jun 2015 12:21]
John Rourke
I had to do the full installation of Visual Studio Pro. That isn't economical for everyone though. The same version and installs worked fine on a Windows 8.1 Pro laptop. The Win7 Enterprise x64 was also upgraded from Win7 pro x64. I had other issues with applications failing to install after doing this upgrade, so I kind of attributed many things to that. Sorry I can't give you anything more concrete.
[7 Sep 2015 8:16]
Chiranjeevi Battula
Hello John Rourke, Thank you for the bug report. I tried with latest versions of MySQL 5.6.26, VS 2013 and MySQL Visual Studio integration 1.2.3/4 as well and it worked without any issues. Could you please list out exact steps you tried out at your end, this would help us to reproduce the issue at our end. Thanks, Chiranjeevi.
[8 Oct 2015 1:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".