Bug #30425 When creating a new db connection
Submitted: 15 Aug 2007 2:09 Modified: 23 Aug 2007 20:32
Reporter: John Wood Email Updates:
Status: Closed Impact on me:
None 
Category:Connector / NET Severity:S2 (Serious)
Version:5.1 OS:Windows (Visual Studio 2005)
Assigned to: CPU Architecture:Any
Tags: Connecto 5.1, Server Explorer, visual studio 2005

[15 Aug 2007 2:09] John Wood
Description:
I just installed the Connector .net 5.1.2 and when i goto type in the server name, userid, password, or database name into the subsequent fields from within the server explorer in visual studio, it acts as if i press the enter key.  I dont even get the chance to type in any of the actual field values for connecting to even test the connection, after i type the first character into any of the 4 fields, it just "completes".  It does not render a database object in the server explorer.

In past experience this seems like it is an error for whatever reason in the keyboard entry listener.  Im not trying to diagnose the problem just assist in debugging the control mechanism.  In my view of the actions and the way they are being handled, it echos the key i press into the field and in a split second that key character is "not-valid" and kicks me out of the connector connection string wizard.

Well i tried performing a manual connection string creation and the advanced interface works find and takes my keyboard input, and tested the connection and it validated.  But when i went to press "Ok", it said "Unable to find requested .Net Framework Data Provider. It may not be installed."  So it is simplified into the basic connection interface and not the advanced interface.

How to repeat:
1 - Have Visual Studio up and running with a project open.
2 - Have the "Server Explorer" visible
3 - Right-click on the databases object
4 - In the Add Connection interface, click on Change
5 - Select MySQL Database and click OK
6 - Then attempt to type in either a http or ip address *** This is where the hickup is located ***
7 - Once I tried several times using both keyboard and numpad entry methods, i then clicked on Advanced.
8 - From here i manually entered my remote database connection as such:
  A - Server=mysql.avidhosting.com;Database=woodjo1_BB;Uid=woodjo1_phpbb;Password=<wouldnt you like to know>;
9 - Clicked OK from the Advanced interface, and then clicked "Test Connection"
10 - It responded Test Successful.
11 - Then click OK, and it pops up with the same error message as in the bottom of the Description section.

Suggested fix:
Not real sure how the implemented addon is coded into visual studio but its in dealing with the simplified connection string setup and creation and not in the advanced.  The only problem that may pop up is the lack of auto-populating the basic setup fields from the advanced window.  If i had a better understanding of how to implement addons into visual studio and registering the namespace DLLs into Visual Studio, I might be able to make a suggestion.
[15 Aug 2007 2:11] John Wood
The connector/net that i downloaded was version 5.1.2 and downloaded on 8/14/07.
[16 Aug 2007 4:04] scott myers
I ran into the same issue... running VS 2005 v8.0.50727 along with .NET Framework 2.0.50727, MySQL Connector 5.1.2 , and MySQL 5.1.20 (downloaded today).

Another interesting observation... using server explorer, I see the option for MySQL Database as an option for "data source" when "add connection", however, when I drag the datagrid control onto the design surface and attempt to configure it, the MySQL database option does not show.  It's the same dialogue!
[19 Aug 2007 13:22] Tonci Grgin
Hi John and thanks for your report. I was unable to verify it using:
 - Server version: 5.1.22-beta-pb1555 MySQL Pushbuild Edition, build 1555 on WinXP Pro SP2 localhost
 - c/NET 5.1.2.1 (C:\WINDOWS\assembly\GAC_MSIL\MySql.Data\5.1.2.1__c5687fc88969c44d\MySql.Data.dll) on NET FW v2.0.50727
 - VS2005 Pro

There is probably something wrong with your GAC and/or configuration but I can't tell what as I can't repeat the problem...
[19 Aug 2007 21:14] scott myers
Thanks Tonci,

Interesting that I do not have a:

..\GAC_MSIL\MySql.Data\5.1.2.1__c5687fc88969c44d\MySql.Data.dll) folder located under C:\WINDOWS\assembly.

The MySQL.Data.dll that I have is located at C:\Program Files\MySQL\MySQL Connector Net 5.1.2\Binaries\.NET 2.0 folder.

What should the installation process have created???  What do you recommend as the next steps to resolve??

Thanks

--Scott
[20 Aug 2007 14:29] John Wood
Ok further stats on this are i am not running a MySQL server on my computer.  If thats what your GAC directory is, then theres your problem.  You have a MYSQL server running on your box.  Try reproducing this on a box that doesnt have MySQL on it.

And just because you cant reproduce the problem doesnt mean the problem is not there.  Sweep it under the carpet all you want but the problem is still there.  You need to send this to your VS development team that incorporated the interface.
[23 Aug 2007 12:46] gianpy garrone
I have the same problem with:
-C:\WINDOWS\assembly\GAC_MSIL\MySql.Data\5.1.2.2__c5687fc88969c44d\MySql.Data.dllon NET FW v2.0.50727

-server version :5.1.20 beta community 

- Microsoft Visual Studio 2005
Version 8.0.50727.762  (SP.050727-7600)
Microsoft .NET Framework
Versione 2.0.50727

Edizione installata: Professional

Microsoft Visual Basic 2005   77936-009-0000007-41095
Microsoft Visual C# 2005   77936-009-0000007-41095
Microsoft Visual C++ 2005   77936-009-0000007-41095
Microsoft Visual J# 2005   77936-009-0000007-41095
Microsoft Visual Web Developer 2005   77936-009-0000007-41095
Microsoft Web Application Projects 2005   77936-009-0000007-41095
Versione 8.0.50727.762

Microsoft Visual Studio 2005 Professional Edition - ITA Service Pack 1 (KB926608)   

MySQL Connector/Net   5.1
Data design and management tools for MySQL.  Copyright © 2007 MySQL AB

SQL Server Analysis Services   
Versione 9.00.3042.00

SQL Server Integration Services   
Versione 9.00.3042.00

SQL Server Reporting Services   
Versione 9.00.3042.00

VMDebugger
[23 Aug 2007 14:35] Tonci Grgin
Hi John.

[20 Aug 16:29] John Wood

> Ok further stats on this are i am not running a MySQL server on my computer.  If thats what your GAC directory is, then theres your problem.  You have a MYSQL server running on your box.  Try reproducing this on a box that doesnt have MySQL on it.

Of course I will try. May I just remind that under the detailed steps provided there was no mention of remote MySQL host thus I made no error in my test case. Furthermore, we are obliged to test with latest versions of our software involved (as it is publicly available) thus the minor differences.

> And just because you cant reproduce the problem doesnt mean the problem is not there.  Sweep it under the carpet all you want but the problem is still there.  You need to send this to your VS development team that incorporated the interface.

No one is sweeping anything under the carpet. I challenge you to "fix" a bug in situation where you can not reproduce it! I never thought it possible to fix something you don't see. That's why we insist on detailed bug reports, which is an art in itself. It is my opinion that to many layers are involved in your problem and it will be very hard to locate it, but I'll try. As for VS plugin team, bugsdb is public place, they can look into it just like we all did.

To conclude, this report needs reverification as new info is provided. I'll notify c/NET team too. Thanks for your interest in MySQL.
[23 Aug 2007 15:14] Reggie Burnett
John

While I don't know of a specific bug in our 5.1.2 installer that would cause this, I know what the problem is.  The installer is supposed to register mysql.data.dll into the system GAC and that apparently didn't happen on your system.  If you do a gacutil /i mysql.data.dll in our binaries\.net 2.0 folder it will start working.

I'm setting this bug report to closed as we are about to release 5.1.3.  If you continue to see this problem in 5.1.3, please don't hesitate to reopen this bug report or file a new one.
[23 Aug 2007 20:32] John Wood
Thank you for giving me a more detailed explanation of the problem.