MySQL Bugs: #29483: Connector 5.1.2 cannot be used with VS 2005 SP1

Bug #29483	Connector 5.1.2 cannot be used with VS 2005 SP1
Submitted:	2 Jul 2007 11:57	Modified:	13 Aug 2007 9:12
Reporter:	Petr Kuzel	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	Connector / NET	Severity:	S2 (Serious)
Version:		OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
After installing the connector and trying to Add new data source... the dialog crashes with ... message.

furtunatelly, after uninstalling connector all is OK.

Applie sto both 5.0.7 and 5.1.2.

How to repeat:
Add new data source...

Now I installed without VS Integration so no problem.

Went to samples/.  VB TableEditor sample code server address is hardcoded in code. It does not work out of box!

Wrong assumption: mysql database is not mandatory and it does not exist on my server. 

        connStr = String.Format("server={0};user id={1}; password={2}; database=mysql; pooling=false", _
				server.Text, userid.Text, password.Text )

Just kick-off database=mysql component and it works. 

Conclusion out-of box experinece is cripled because VS integration does not work and sample does not wotk too.

Hi Petr and thanks for your report. I'm having troubles following it; can you please summarize what is the problem / inconvenience / bug here? Is there a bug at all?

Summary

1) if I install connector's VS 2005 SP1 (on XP) integration the integration code throws a runtime exception (caught by VS and reported without details), so it's not possible to manage datasources anymore.

2) Examples are wrong, their connection string assumes existence of mysql catalog, Connection must be constructed using connection-string without this component and then show databases;.

Very bad out-of-box experience (I spend 1-2 hours trying to figure out, installed various versions, checking my server settings, my network settings (because missing catalog is reported as unreachable server at 254.* address,) ...) but if one do not give up it works...

...without the integration code.

Petr, thanks for clarification. Looking into this problem again.

Petr. We tested on 2 machines, both XP, VS2005 Pro with and without SP1. c/NET used is 5.1.2GA. No problems detected.

Now, for Q1). Are you by any chance using Express edition of VS? If so, it does not support plug-ins.

Q2) You're right. TableEditor project assumes existence of *mysql* catalog which is true for every MySQL server installation. I think this is a leftover from times when catalog was required by client protocol and *mysql* was sure to exist. If you want I can change this report to feature request with synopsis "Please remove hard-coded catalog in sample projects".

If you scan though your forums it's reported by another developer as well. My VS version is:

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

Installed Edition: Enterprise

Microsoft Visual Studio 2005 Team Edition for Software Developers - ENU Service Pack 1 (KB926601)   
This service pack is for Microsoft Visual Studio 2005 Team Edition for Software Developers - ENU. 
If you later install a more recent service pack, this service pack will be uninstalled automatically. 
For more information, visit http://support.microsoft.com/kb/926601

Visual Studio Package Load Analyzer   1.0
A utility that analyzes package load failures in Visual Studio 2005.

Petr, I don't believe there's single Enterprise installation available to me... In any case, Pro with/without SP1 does not exhibit this problem. Can we agree that it's impossible to fix something one can't reproduce?

I will forward your problem to c/NET team leader and see what he makes of it.

For me, this is "Can't repeat".

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".