Bug #90767 | Mysql and VS 2015 / 2017 | ||
---|---|---|---|
Submitted: | 5 May 2018 22:59 | Modified: | 8 May 2018 8:38 |
Reporter: | Pedro Dias | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | Connector / NET | Severity: | S1 (Critical) |
Version: | Any | OS: | Windows (W 10) |
Assigned to: | Assigned Account | CPU Architecture: | x86 (Intel I7 7700-HQ) |
Tags: | Connector/NET / Mysql Visual Studio, Visual Studio |
[5 May 2018 22:59]
Pedro Dias
[6 May 2018 21:30]
Pedro Dias
After installing the mysql for visual studio
Attachment: vs2017error.png (image/png, text), 143.65 KiB.
[6 May 2018 21:31]
Pedro Dias
Before the previous print and when configuring the connection
Attachment: vs2017error_1.png (image/png, text), 147.19 KiB.
[6 May 2018 21:32]
Pedro Dias
Error on the after the first print and final message
Attachment: mysql_error.txt (text/plain), 356 bytes.
[7 May 2018 8:23]
Chiranjeevi Battula
Hello Pedro Dias, Thank you for the bug report. This is most likely duplicate of Bug #88351, please see Bug #88351 Thanks, Chiranjeevi.
[7 May 2018 9:49]
Pedro Dias
Hi Chiranjeevi Battula, I added a new print just for you to see what happens in a fresh windows 10 install and a new VS 2017 install. added a new pic. How can I use Mysql inside the VS 2017?
[7 May 2018 9:49]
Pedro Dias
new install
Attachment: vs2017error_2.png (image/png, text), 111.29 KiB.
[7 May 2018 21:04]
Pedro Dias
Hi Chiranjeevi Battula, I added a new print just for you to see what happens in a fresh windows 10 install and a new VS 2017 install. added a new pic. How can I use Mysql inside the VS 2017 or 2015? Please do not put this issue as a duplicate if in the duplicate doesn't have a fix that I can use. In my opinion it is not a duplicate! If that happens again I will change to another DBMS! I can not afford to lose client because you (Mysql) can not or will not give a reply or a solution that can be used. Best regards, Pedro Dias
[8 May 2018 8:38]
Chiranjeevi Battula
Hello Pedro Dias, Thank you for the feedback. Confirmed internally that the fix to Bug #88351 also fixes both the issues reported in your bug report. Plesae follow the Bug #88351 for fixes and bug system don't comment the release date for fixes. Thanks, Chiranjeevi.