Author: mcbrown
Date: 2006-12-14 11:46:31 +0100 (Thu, 14 Dec 2006)
New Revision: 4250
Log:
Updating the name of C/NET (no MySQL prefix)
Updating the name of the VStudio plugin
Modified:
trunk/refman-4.1/connector-net.xml
trunk/refman-5.0/connector-net.xml
trunk/refman-5.0/connector-vstudioplugin.xml
trunk/refman-5.1/connector-net.xml
trunk/refman-5.1/connector-vstudioplugin.xml
Modified: trunk/refman-4.1/connector-net.xml
===================================================================
--- trunk/refman-4.1/connector-net.xml 2006-12-14 07:31:56 UTC (rev 4249)
+++ trunk/refman-4.1/connector-net.xml 2006-12-14 10:46:31 UTC (rev 4250)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 3; 825 bytes
@@ -4,15 +4,15 @@
[
<!ENTITY % fixedchars.entities SYSTEM "../common/fixedchars.ent">
%fixedchars.entities;
- <!ENTITY % title.entities SYSTEM "../refman-common/urls.ent">
- %title.entities;
+ <!ENTITY % urls.entities SYSTEM "../refman-common/urls.ent">
+ %urls.entities;
<!ENTITY % versions.entities SYSTEM "versions.ent">
%versions.entities;
<!ENTITY connector_net "MySQL Connector/NET">
]>
<section id="connector-net">
- <title>Connector/NET</title>
+ <title>MySQL Connector/NET</title>
<indexterm>
<primary>Connector/NET</primary>
Modified: trunk/refman-5.0/connector-net.xml
===================================================================
--- trunk/refman-5.0/connector-net.xml 2006-12-14 07:31:56 UTC (rev 4249)
+++ trunk/refman-5.0/connector-net.xml 2006-12-14 10:46:31 UTC (rev 4250)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 3; 825 bytes
@@ -4,15 +4,15 @@
[
<!ENTITY % fixedchars.entities SYSTEM "../common/fixedchars.ent">
%fixedchars.entities;
- <!ENTITY % title.entities SYSTEM "../refman-common/urls.ent">
- %title.entities;
+ <!ENTITY % urls.entities SYSTEM "../refman-common/urls.ent">
+ %urls.entities;
<!ENTITY % versions.entities SYSTEM "versions.ent">
%versions.entities;
<!ENTITY connector_net "MySQL Connector/NET">
]>
<section id="connector-net">
- <title>Connector/NET</title>
+ <title>MySQL Connector/NET</title>
<indexterm>
<primary>Connector/NET</primary>
Modified: trunk/refman-5.0/connector-vstudioplugin.xml
===================================================================
--- trunk/refman-5.0/connector-vstudioplugin.xml 2006-12-14 07:31:56 UTC (rev 4249)
+++ trunk/refman-5.0/connector-vstudioplugin.xml 2006-12-14 10:46:31 UTC (rev 4250)
Changed blocks: 13, Lines Added: 41, Lines Deleted: 39; 7599 bytes
@@ -30,9 +30,9 @@
</para>
<para>
- The MySQL DDEX Provider is designed to work with MySQL version 5.0,
- but is also compatible with MySQL 4.1.1 and provides limited
- compatibility with MySQL 5.1.
+ The MySQL Visual Studio Plugin is designed to work with MySQL
+ version 5.0, but is also compatible with MySQL 4.1.1 and provides
+ limited compatibility with MySQL 5.1.
</para>
<section id="connector-vstudio-install">
@@ -40,14 +40,15 @@
<title>Installing the MySQL Visual Studio Plugin</title>
<para>
- The MySQL DDEX Provider requires Visual Studio 2005 Professional
- Edition to be installed, and therefore it has the same hardware
- and system requirements.
+ The MySQL Visual Studio Plugin requires Visual Studio 2005
+ Professional Edition to be installed, and therefore it has the
+ same hardware and system requirements.
</para>
<para>
Here is the list of components that should already be installed
- before starting the installation of the MySQL DDEX Provider:
+ before starting the installation of the MySQL Visual Studio
+ Plugin:
</para>
<itemizedlist>
@@ -77,7 +78,7 @@
<para>
The user used to connect to the MySQL server must have the
following privileges to use the functionality provided by the
- MySQL DDEX Provider:
+ MySQL Visual Studio Plugin:
</para>
<itemizedlist>
@@ -131,19 +132,19 @@
</itemizedlist>
<para>
- The MySQL DDEX Provider is delivered as a MSI package that can be
- used to install, uninstall or reinstall the Provider. If you are
- not using Windows XP or Windows Server 2003 you upgrade the
- Windows Installer system to the latest version (see
+ The MySQL Visual Studio Plugin is delivered as a MSI package that
+ can be used to install, uninstall or reinstall the Provider. If
+ you are not using Windows XP or Windows Server 2003 you upgrade
+ the Windows Installer system to the latest version (see
<ulink url="http://support.microsoft.com/default.aspx?scid=kb;EN-US;292539">http://support.microsoft.com/default.aspx?scid=kb;EN-US;292539</ulink>
for details).
</para>
<para>
The MSI-package is named <filename>MySQL-DDEX.msi</filename>. To
- install the MySQL DDEX Provider, right click on the MSI file and
- select <guimenu>Install</guimenu>. The installation process is as
- follow:
+ install the MySQL Visual Studio Plugin, right click on the MSI
+ file and select <guimenu>Install</guimenu>. The installation
+ process is as follow:
</para>
<orderedlist>
@@ -165,8 +166,8 @@
<listitem>
<para>
The destination folder choice dialog is opened. Here you can
- point out the folder where the MySQL DDEX Provider will be
- installed. The default destination folder is
+ point out the folder where the MySQL Visual Studio Plugin will
+ be installed. The default destination folder is
<filename>%ProgramFilesDir%\MySQL\MySQL DDEX Data
Provider</filename>, where
<filename>%ProgramFilesDir%</filename> is the Program Files
@@ -201,7 +202,7 @@
</orderedlist>
<para>
- To uninstall the MySQL DDEX Provider, you can use either
+ To uninstall the MySQL Visual Studio Plugin, you can use either
Add/Remove Programs component of the Control Panel or the same
MSI-package. Choose the <guilabel>Remove</guilabel> option, and
the Provider will be uninstalled automatically.
@@ -209,8 +210,8 @@
<para>
To repair the Provider, right click the MSI-package and choose the
- <guimenu>Repair</guimenu> option. The MySQL DDEX Provider will be
- repaired automatically.
+ <guimenu>Repair</guimenu> option. The MySQL Visual Studio Plugin
+ will be repaired automatically.
</para>
<para>
@@ -237,8 +238,8 @@
<listitem>
<para>
<filename>MySql.VisualStudio.dll.config</filename> — the
- configuration file for the MySQL DDEX Provider. This file
- contains default values for the provider GUI layout.
+ configuration file for the MySQL Visual Studio Plugin. This
+ file contains default values for the provider GUI layout.
</para>
<note>
@@ -301,8 +302,8 @@
<title>Creating a connection to the MySQL server</title>
<para>
- Once the MySQL DDEX Provider is installed, you can use it to
- create, modify and delete connections to MySQL databases. To
+ Once the MySQL Visual Studio Plugin is installed, you can use it
+ to create, modify and delete connections to MySQL databases. To
create a connection with a MySQL database, perform the following
steps:
</para>
@@ -418,13 +419,14 @@
<section id="connector-vstudio-using">
- <title>Using the MySQL DDEX Provider</title>
+ <title>Using the MySQL Visual Studio Plugin</title>
<para>
- To work with a MySQL server using the MySQL DDEX Provider, open
- the Visual Studio 2005, open the <guilabel>Server
+ To work with a MySQL server using the MySQL Visual Studio Plugin,
+ open the Visual Studio 2005, open the <guilabel>Server
Explorer</guilabel>, and select the required connection. The
- working area of the MySQL DDEX Provider consists of three parts.
+ working area of the MySQL Visual Studio Plugin consists of three
+ parts.
</para>
<mediaobject>
@@ -492,9 +494,9 @@
</mediaobject>
<para>
- The MySQL DDEX Provider Table Editor is implemented in a similar
- fashion to the standard Query Browser Table Editor, but with
- minor differences.
+ The MySQL Visual Studio Plugin Table Editor is implemented in a
+ similar fashion to the standard Query Browser Table Editor, but
+ with minor differences.
</para>
<para>
@@ -684,11 +686,11 @@
<listitem>
<para>
- When a foreign key is changed, the MySQL DDEX Provider
- generates two queries: the first query drops the changed
- keys and the second one recreates the new values. The
- reason for such a behavior is to avoid the Bug #8377 and
- Bug #8919.
+ When a foreign key is changed, the MySQL Visual Studio
+ Plugin generates two queries: the first query drops the
+ changed keys and the second one recreates the new values.
+ The reason for such a behavior is to avoid the Bug #8377
+ and Bug #8919.
</para>
</listitem>
@@ -698,9 +700,9 @@
<para>
If changed values are for some reason inconsistent and cause
the second query to fail, all affected foreign keys will be
- dropped. If this is the case, the MySQL DDEX Provider will
- mark them as new in the Table Editor, and you will have to
- recreate them later. But if you close the Table Editor
+ dropped. If this is the case, the MySQL Visual Studio Plugin
+ will mark them as new in the Table Editor, and you will have
+ to recreate them later. But if you close the Table Editor
without saving, these foreign keys will be lost.
</para>
</note>
Modified: trunk/refman-5.1/connector-net.xml
===================================================================
--- trunk/refman-5.1/connector-net.xml 2006-12-14 07:31:56 UTC (rev 4249)
+++ trunk/refman-5.1/connector-net.xml 2006-12-14 10:46:31 UTC (rev 4250)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 427 bytes
@@ -12,7 +12,7 @@
]>
<section id="connector-net">
- <title>Connector/NET</title>
+ <title>MySQL Connector/NET</title>
<indexterm>
<primary>Connector/NET</primary>
Modified: trunk/refman-5.1/connector-vstudioplugin.xml
===================================================================
--- trunk/refman-5.1/connector-vstudioplugin.xml 2006-12-14 07:31:56 UTC (rev 4249)
+++ trunk/refman-5.1/connector-vstudioplugin.xml 2006-12-14 10:46:31 UTC (rev 4250)
Changed blocks: 13, Lines Added: 41, Lines Deleted: 39; 7599 bytes
@@ -30,9 +30,9 @@
</para>
<para>
- The MySQL DDEX Provider is designed to work with MySQL version 5.0,
- but is also compatible with MySQL 4.1.1 and provides limited
- compatibility with MySQL 5.1.
+ The MySQL Visual Studio Plugin is designed to work with MySQL
+ version 5.0, but is also compatible with MySQL 4.1.1 and provides
+ limited compatibility with MySQL 5.1.
</para>
<section id="connector-vstudio-install">
@@ -40,14 +40,15 @@
<title>Installing the MySQL Visual Studio Plugin</title>
<para>
- The MySQL DDEX Provider requires Visual Studio 2005 Professional
- Edition to be installed, and therefore it has the same hardware
- and system requirements.
+ The MySQL Visual Studio Plugin requires Visual Studio 2005
+ Professional Edition to be installed, and therefore it has the
+ same hardware and system requirements.
</para>
<para>
Here is the list of components that should already be installed
- before starting the installation of the MySQL DDEX Provider:
+ before starting the installation of the MySQL Visual Studio
+ Plugin:
</para>
<itemizedlist>
@@ -77,7 +78,7 @@
<para>
The user used to connect to the MySQL server must have the
following privileges to use the functionality provided by the
- MySQL DDEX Provider:
+ MySQL Visual Studio Plugin:
</para>
<itemizedlist>
@@ -131,19 +132,19 @@
</itemizedlist>
<para>
- The MySQL DDEX Provider is delivered as a MSI package that can be
- used to install, uninstall or reinstall the Provider. If you are
- not using Windows XP or Windows Server 2003 you upgrade the
- Windows Installer system to the latest version (see
+ The MySQL Visual Studio Plugin is delivered as a MSI package that
+ can be used to install, uninstall or reinstall the Provider. If
+ you are not using Windows XP or Windows Server 2003 you upgrade
+ the Windows Installer system to the latest version (see
<ulink url="http://support.microsoft.com/default.aspx?scid=kb;EN-US;292539">http://support.microsoft.com/default.aspx?scid=kb;EN-US;292539</ulink>
for details).
</para>
<para>
The MSI-package is named <filename>MySQL-DDEX.msi</filename>. To
- install the MySQL DDEX Provider, right click on the MSI file and
- select <guimenu>Install</guimenu>. The installation process is as
- follow:
+ install the MySQL Visual Studio Plugin, right click on the MSI
+ file and select <guimenu>Install</guimenu>. The installation
+ process is as follow:
</para>
<orderedlist>
@@ -165,8 +166,8 @@
<listitem>
<para>
The destination folder choice dialog is opened. Here you can
- point out the folder where the MySQL DDEX Provider will be
- installed. The default destination folder is
+ point out the folder where the MySQL Visual Studio Plugin will
+ be installed. The default destination folder is
<filename>%ProgramFilesDir%\MySQL\MySQL DDEX Data
Provider</filename>, where
<filename>%ProgramFilesDir%</filename> is the Program Files
@@ -201,7 +202,7 @@
</orderedlist>
<para>
- To uninstall the MySQL DDEX Provider, you can use either
+ To uninstall the MySQL Visual Studio Plugin, you can use either
Add/Remove Programs component of the Control Panel or the same
MSI-package. Choose the <guilabel>Remove</guilabel> option, and
the Provider will be uninstalled automatically.
@@ -209,8 +210,8 @@
<para>
To repair the Provider, right click the MSI-package and choose the
- <guimenu>Repair</guimenu> option. The MySQL DDEX Provider will be
- repaired automatically.
+ <guimenu>Repair</guimenu> option. The MySQL Visual Studio Plugin
+ will be repaired automatically.
</para>
<para>
@@ -237,8 +238,8 @@
<listitem>
<para>
<filename>MySql.VisualStudio.dll.config</filename> — the
- configuration file for the MySQL DDEX Provider. This file
- contains default values for the provider GUI layout.
+ configuration file for the MySQL Visual Studio Plugin. This
+ file contains default values for the provider GUI layout.
</para>
<note>
@@ -301,8 +302,8 @@
<title>Creating a connection to the MySQL server</title>
<para>
- Once the MySQL DDEX Provider is installed, you can use it to
- create, modify and delete connections to MySQL databases. To
+ Once the MySQL Visual Studio Plugin is installed, you can use it
+ to create, modify and delete connections to MySQL databases. To
create a connection with a MySQL database, perform the following
steps:
</para>
@@ -418,13 +419,14 @@
<section id="connector-vstudio-using">
- <title>Using the MySQL DDEX Provider</title>
+ <title>Using the MySQL Visual Studio Plugin</title>
<para>
- To work with a MySQL server using the MySQL DDEX Provider, open
- the Visual Studio 2005, open the <guilabel>Server
+ To work with a MySQL server using the MySQL Visual Studio Plugin,
+ open the Visual Studio 2005, open the <guilabel>Server
Explorer</guilabel>, and select the required connection. The
- working area of the MySQL DDEX Provider consists of three parts.
+ working area of the MySQL Visual Studio Plugin consists of three
+ parts.
</para>
<mediaobject>
@@ -492,9 +494,9 @@
</mediaobject>
<para>
- The MySQL DDEX Provider Table Editor is implemented in a similar
- fashion to the standard Query Browser Table Editor, but with
- minor differences.
+ The MySQL Visual Studio Plugin Table Editor is implemented in a
+ similar fashion to the standard Query Browser Table Editor, but
+ with minor differences.
</para>
<para>
@@ -684,11 +686,11 @@
<listitem>
<para>
- When a foreign key is changed, the MySQL DDEX Provider
- generates two queries: the first query drops the changed
- keys and the second one recreates the new values. The
- reason for such a behavior is to avoid the Bug #8377 and
- Bug #8919.
+ When a foreign key is changed, the MySQL Visual Studio
+ Plugin generates two queries: the first query drops the
+ changed keys and the second one recreates the new values.
+ The reason for such a behavior is to avoid the Bug #8377
+ and Bug #8919.
</para>
</listitem>
@@ -698,9 +700,9 @@
<para>
If changed values are for some reason inconsistent and cause
the second query to fail, all affected foreign keys will be
- dropped. If this is the case, the MySQL DDEX Provider will
- mark them as new in the Table Editor, and you will have to
- recreate them later. But if you close the Table Editor
+ dropped. If this is the case, the MySQL Visual Studio Plugin
+ will mark them as new in the Table Editor, and you will have
+ to recreate them later. But if you close the Table Editor
without saving, these foreign keys will be lost.
</para>
</note>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r4250 - in trunk: refman-4.1 refman-5.0 refman-5.1 | mcbrown | 14 Dec |
