| Bug #26177 | Can't make the connection | ||
|---|---|---|---|
| Submitted: | 8 Feb 2007 5:12 | Modified: | 12 Feb 2007 15:07 |
| Reporter: | Paweł Wereński | Email Updates: | |
| Status: | Not a Bug | Impact on me: | |
| Category: | MySQL Visual Studio Plugin | Severity: | S1 (Critical) |
| Version: | 1.0.2 & 1.1.2 Alpha | OS: | Windows (Windows 2000) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | Connection, freeze, visual studio plugin | ||
[12 Feb 2007 10:14]
Tonci Grgin
Hi and thanks for your report. I am unable to verify it with: - MySQL server 4.1.22BK to 5.0.34BK on WinXP Pro SP2 localhost - NET FW 2, c/NET 5.0.3 Is it possible that you missed some of restrictions: - Support for MySQL versions 4.1 and higher. - This product will only work correctly with Connector/Net 5.0.2 and higher. - This product requires VS Pro at least.
[12 Feb 2007 10:17]
Paweł Wereński
Sorry, it was version 3.23.52 of MySQL (but I need to connect to all versions anyway)
[12 Feb 2007 15:07]
Tonci Grgin
Hi. Than I have no other option but to rule "Not a bug" as the limitation is stated clearly in the docs. You should choose different approach then.

Description: My Visual Studio 2005 freezes (to death) when I'm trying to test a newly created connection to MySQL. If the data (server,user,pass) is correct, the VS hangs up. If the data is incorrect, I get the error message ("Access denied for user.."). The same as described here by Mark Czelnik: http://forums.mysql.com/read.php?38,138219,138219#msg-138219 I have found the similiar bug: #24875, but that is about upper and mixed case DB names and I have tried all kind of names, especially lower case and it is still not working. I can't do anything. I'm trying to connect to MySQL 4.* because my application must be able to connect to this version. How to repeat: Under Visual Studio: 1. Data -> Add new data source.. -> Database -> [New Connection] 2. Data Source [Change] to MySQL Database 3. Fill in the settings for a localhost MySQL database connection 4. Press [Test Connection] 5. No you can't do anything except killing whole Visual Studio. Suggested fix: Wish I could know...