Bug #78655 | MySQL for Visual Studio 1.2.4 does not work in Visual Studio 2015 | ||
---|---|---|---|
Submitted: | 1 Oct 2015 0:47 | Modified: | 11 Nov 2015 0:20 |
Reporter: | Mark C | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Visual Studio Integration | Severity: | S2 (Serious) |
Version: | 1.2.4 | OS: | Windows |
Assigned to: | Luis Penunuri | CPU Architecture: | Any |
[1 Oct 2015 0:47]
Mark C
[1 Oct 2015 14:51]
Luis Penunuri
Hi Mark, Thanks for using MySQL. We are taking a look into it right now. As soon we have an update on this we will let you know. Thanks, and have a good one ! Regards. Luis Alfonso Penunuri.
[1 Oct 2015 15:17]
Chiranjeevi Battula
Hello Mark, Thank you for the bug report. Verified based on internal discussion with dev's. Thanks, Chiranjeevi.
[19 Oct 2015 4:44]
Javier TreviƱo
Posted by developer: Please try installing Connector/NET and see of the ADO.NET Entity Model wizard does not close. Some dependencies are currently needed that are installed by Connector/NET. While this bug is resolved, I think this is a viable and easy workaround.
[11 Nov 2015 0:20]
Luis Penunuri
Hi, I was unable to reproduce the issue, following the next steps in a new PC with a fresh VS2015 Enterprise installation (default options selected): 1.- Install MySQL for Visual Studio 1.2.4 2.- Create a new web project -> File -> New -> Project -> Visual C# -> Web -> ASP.NET Web Application -> MVC -> 3.- Add a new model -> Add -> New Item -> Data -> ADO.NET Entity Data Model Actual results: The template "ADO.NET Entity Data Model" is available from the "Data" templates list. Also, I tried with a windows form project: 1.- Install MySQL for Visual Studio 1.2.4 2.- Create a new web project -> File -> New -> Project -> Visual C# -> Windows -> Windows Forms Application 3.- Add a new model -> Add -> New Item -> Data -> ADO.NET Entity Data Model Actual results: The template "ADO.NET Entity Data Model" is available from the "Data" templates list. Can you please provide specific steps on how to reproduce this issue ? Any detailed information can be helpful so we can try to reproduce the possible bug you are getting. Thanks in advance.