Documentation Home
MySQL for Visual Studio Release Notes
Download these Release Notes
PDF (US Ltr) - 91.3Kb
PDF (A4) - 90.5Kb


MySQL for Visual Studio Release Notes  /  Changes in MySQL for Visual Studio 2.0  /  Changes in MySQL for Visual Studio 2.0.3 (2016-07-01, Development Milestone)

Changes in MySQL for Visual Studio 2.0.3 (2016-07-01, Development Milestone)

Known limitation of this release: Some features such as the Entity Framework, and some Server Explorer functionality like drag and drop elements into a Dataset Designer, or Design Tables, do not function in this version.

Functionality Added or Changed

  • Added an error handler to manage exceptions from MySQL Shell, and to display relevant information about the exceptions in the selected output. This includes the full error message from MySQL Shell, and extra validation in case it contains terms such as "undefined" or "null".

  • Added SSL support for MySQL connections that use the X Protocol. SSL support works with PEM files, so SSL connections need to be created through the "MySQL Connections Manager" in MySQL for Visual Studio, or from MySQL Workbench.

  • Added support for the following X DevAPI functions: parseUri() and isOpen().

  • A new MySQL Output pane was added that contains a results grid view similar to the view found in MySQL Workbench. It contains the following data for executed statements: Success (with an icon if possible), Execution index (sequential), Execution Time, Query Text, Message (output from the server), and Duration / Fetch. This functionality is available for JavaScript and Python queries.

  • Added a console mode editor, where pressing Enter executes the code.

  • Added the ability to switch between "Batch" (execute multiple statements) and "Console" (execute each statement after pressing Enter) modes, from the Query Editor toolbar as a dropdown list.

  • A MySQL connection manager dialog was added to help fully manage MySQL connections. It supports connection sharing with MySQL Workbench, and supports create, edit, configure, and delete actions.

    MySQL connections created with the connection manager where the password is securely stored in the system's password vault functions with the Server Explorer in Visual Studio. The password is extracted from the password vault, and persists in the Server Explorer connections.

Bugs Fixed

  • The "mysqlx" module was not imported properly to execute JavaScript queries. (Bug #23091964, Bug #81052)

  • After opening a valid MySQL connection and creating a new JavaScript MySQL script, disconnecting then reconnecting to the MySQL Server while changing the port to 33060 would fail.

  • MySQL for Visual Studio now shows a message stating that a SSL connection is required by the MySQL server if the require_secure_transport variable is set.

  • All script editors now display detailed information about the connection used. Before, the information was displayed in the toolbar as labels, but now all information is consolidated in a menu opened where the connection name is displayed. Additional information includes the connection method, host identifier, server version, user, and schema.

  • Output from executing JavaScript and Python commands were not visible unless the Output window was already opened. The Output window now automatically opens when executing commands.