Softpedia >Windows >Programming >Other Programming Files >MySQL for Visual Studio >  Changelog

MySQL for Visual Studio Changelog

What's new in MySQL for Visual Studio 1.2.10

Aug 3, 2021
  • Functionality Added or Changed:
  • Parser and debugger revisions now make use of the parser classes generated by ANTLRCS 3.5.2 (the C# port of ANTLR 3). In addition, some syntax was updated to coordinate with MySQL Server 8.0 changes. (Bug #32398998)
  • The performance associated with showing tooltips now is enhanced by switching to (async) Quick Info for UI thread affinity. (Bug #30674699, Bug #97934)
  • Support for Visual Studio 2015 is removed with this release
  • Bugs Fixed:
  • After an active connection exceeded its timeout setting, it could not be used again without restarting Visual Studio. (Bug #33033241)
  • Visual Studio quit unexpectedly after a MySQL script was executed using a timed-out connection
  • Improved error messaging now identifies that a connection may no longer be active when it is selected for use. (Bug #33033225)
  • An incorrect path to the deployed template files prevented the creation of MySQL MVC item templates if they were selected from a Visual Basic project. (Bug #33026170)
  • Some properties and buttons were hidden within the Advanced area of the Connect to MySQL dialog when the DPI setting value was greater than 100. (Bug #33025993)
  • The Configuration Update Tool reapplied the Connector/NET configuration changes to previously updated versions of Visual Studio when it was activated to update a new version. (Bug #33020888)
  • User credentials were not copied fully to Server Explorer if a new connection was created by selecting the "MySQL script with new connection" option from the MySQL toolbar. The resulting connection was insufficient for use with MySQL scripts or when attempting to open the Data Export tool. (Bug
  • 33016238)
  • An error was emitted if an object was not fully initialized before the operation creating it in the MVC Item Template dialog was canceled. (Bug #33005844)
  • Dialog boxes containing text messages did not resize to show the entire message if the DPI setting value was greater than 100. (Bug #33000651)
  • Without Connector/NET, attempting to edit (design) MySQL tables or views returned an error. All error messages of this type now state that Connector/NET must be installed. (Bug #33000642)
  • In Visual Studio 2019, the MySQL Data Export tool did not display properly within the tab. (Bug 32978902)
  • An initial attempt to make a connection using the MySQL connection dialog could cause Visual Studio to stop responding. (Bug #32977888)
  • Server Explorer’s design option in Visual Studio 2019 for a MySQL table did not open in the tab as expected. This fix restores the ability to alter a table. (Bug #32769097)
  • Before creating a new connection, MySQL for Visual Studio prompted the user to update the log file's path and name. However, if selected, the update process returned an error. If the update was declined selecting one of the databases from the list also produced an error. This fix revises the implementation to always initialize the logger first before attempting to log any messages. (Bug #32398894)
  • If an installation targeted the Visual Studio 2015 environment, executing the MSI file to remove MySQL for Visual Studio returned an error and did not finish. (Bug #31966621)
  • A runtime exception resulted when an ASP.NET Web Form Site project was configured to use the default custom SQL value (Dataset) as the DataSource mode. (Bug #30961816)
  • The attempt to generate an entity framework model produced several errors rather than creating a data source with a valid connection to the database. (Bug #28752542, Bug #92681)

New in MySQL for Visual Studio 2.0.5 Development (May 1, 2018)

  • Functionality Added or Changed:
  • Removed Support for Microsoft Visual Studio 2010.
  • Added support for Microsoft Visual Studio 2017.
  • Added an output pane to the MySQL SQL Editor window. The new MySQL Output pane includes the information that previously appeared in the Messages tab.
  • Bugs Fixed:
  • The MySQL Data Export Tool exported data from the wrong schema when a second schema was selected and then deselected. In addition, all selected schemas were deselected when a single schema was deselected. (Bug #25713981, Bug #23666666)
  • Script files did not accept most keyboard input after the file was saved for the first time. (Bug #25713638, Bug #24751945)
  • The Field Type view in the result tab of an executed SQL query did not display field information correctly when the query included a schema name explicitly. (Bug #24601948, Bug #82882)
  • The bit() data type was incorrectly implemented as bit(10) for MySQL tables in the Table Designer window. (Bug #13477821)

New in MySQL for Visual Studio 1.2.8 (May 1, 2018)

  • Functionality Added or Changed:
  • When Microsoft Visual Studio receives a request to register (or unregister) MySQL for Visual Studio within the IDE during the installation, Visual Studio might not execute the command properly if the host is running Windows 7. This fix identifies when Visual Studio does not register MySQL for Visual Studio as requested and then provides an alert to perform the registration manually from the Developer Command Prompt for Visual Studio using the following command: devenv /updateconfiguration /log
  • MySQL for Visual Studio now supports the MySQL 8.0 release series (requires Connector/Net 6.9.12, 6.10.7, or 8.0.11) including:
  • MySQL data dictionary, which uses INFORMATION_SCHEMA tables rather than tables in the mysql database (see MySQL Data Dictionary).
  • The caching_sha2_password authentication plugin introduced in MySQL 8.0 (see Caching SHA-2 Pluggable Authentication).
  • In addition, MySQL for Visual Studio now requires that .NET Framework 4.5.2 (or later) be installed for use within Visual Studio 2012 and Visual Studio 2013.
  • Bugs Fixed:
  • The Website Configuration Tool was unable to add an ADO.NET entity data model to an ADO.NET web application successfully. In addition to aligning the web.config file with the installed version of Connector/Net, this fix also disables the Entity Framework 5 selection when the installed connector no longer includes a provider for EF5 (Connector/Net 6.10 and higher). (Bug #27593219)
  • Queries made with a valid MySQL connection received no response from the server. (Bug #27584991)
  • When the MySQL for Visual Studio parser was unable to parse an SQL statement, it generated an unhandled exception that caused Visual Studio to exit unexpectedly. This fix enables the parser to handle exceptions properly and updates the parser to include support for CREATE USER syntax in the MySQL 8.0 release series. (Bug #27580303)
  • The version for the MySql.Web assembly was incorrectly extracted, which prevented the assembly from loading properly and the MySQL Website Configuration Tool from launching. (Bug #27450530)
  • Attempting to open the MySQL Web Configuration Tool, with MySQL Connector/Net and MySQL for Visual Studio prerequisites installed properly, displayed an error message instead of opening the tool. (Bug #27365141, Bug #88570)