MySQL Forums
Forum List  »  Announcements

MySQL for Visual Studio 2.0.5 m4 release has been released
Posted by: Nawaz Nazeer ahamed
Date: April 25, 2017 04:25AM

Dear MySQL users,

The MySQL Windows Experience Team is proud to announce the release of 
MySQL for Visual Studio 2.0.5 m4. Note that this is a development 
preview release and not intended for production usage. 
MySQL for Visual Studio 2.0.5 m4 is the fourth development release of
the MySQL for Visual Studio 2.0 series.  This series adds support for
the new X DevAPI. The X DevAPI enables application developers to write
code that combines the strengths of the relational and document models
using a modern, NoSQL-like syntax that does not assume previous
experience writing traditional SQL.

To learn more about how to write applications using the X DevAPI, see
http://dev.mysql.com/doc/x-devapi-userguide/en/. For more information
about how the X DevAPI is implemented in MySQL for Visual Studio, and
its usage, see
http://dev.mysql.com/doc/refman/5.7/en/mysql-shell-visual-studio.html.

Please note that the X DevAPI requires at least MySQL Server version
5.7.12 or higher with the X Plugin enabled. For general documentation
about how to get started using MySQL as a document store, see
http://dev.mysql.com/doc/refman/5.7/en/document-store.html.

You can download MySQL Installer from our official Downloads page at
http://dev.mysql.com/downloads/installer/.

MySQL for Visual Studio can also be downloaded by using the product
standalone installer found at
http://dev.mysql.com/downloads/windows/visualstudio/, under the 
tab "Development Releases".

Changes in MySQL for Visual Studio 2.0.5 (2017-04-25, Milestone 4)

   Known limitation of this release: MySQL Connections Manager does not
   save the changes made to the default schema when editing a
   connection. Use one of the following workarounds to resolve this
   limitation:

     * For new connections created with MySQL Connections
       Manager in which a default schema is specified, close MySQL
       Connections Manager and then reopen it. After performing this
       action, you can add the connection to the Microsoft Visual Studio
       Server Explorer.

     * For existing connections, set the default schema with
       MySQL Workbench.

   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)

     * The bit() data type was incorrectly implemented as
       bit(10) for MySQL tables in the Table Designer window.  (Bug
       #13477821)


Quick links:

* MySQL for Visual Studio documentation: 
https://dev.mysql.com/doc/visual-studio/en/
* Inside MySQL blog (NEW blog home): http://insidemysql.com/
* MySQL on Windows blog (OLD blog home): 
http://blogs.oracle.com/MySQLOnWindows/
* MySQL for Visual Studio forum: http://forums.mysql.com/list.php?174
* MySQL YouTube channel: http://www.youtube.com/user/MySQLChannel
* MySQL Bugs database: http://bugs.mysql.com


On behalf of the Oracle MySQL Release Engineering Team, 
Nawaz Nazeer Ahamed

Options: ReplyQuote


Subject
Views
Written By
Posted
MySQL for Visual Studio 2.0.5 m4 release has been released
1039
April 25, 2017 04:25AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.