Same problem here.

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for MySQL
Post Reply
MySqlNET320 User

Same problem here.

Post by MySqlNET320 User » Wed 14 Dec 2005 19:03

I am have the same problem.. I added MySqlNet 3.20 final to my web application and now get application exeptions that my license is not valid when trying to open a connection.

All I did was upgrade from 3.20beta to 3.20 final. Looks like new features were added and not tested. I'm very disapointed.

I followed all the instructions in the Licensing help and application is still broken.

RobD
Posts: 25
Joined: Mon 08 Nov 2004 03:41
Location: Sunshine Coast, B.C., Canada

tools greyed out?

Post by RobD » Wed 14 Dec 2005 19:39

Glad to hear I'm not the only one!
Are you using Visual Studio 2005?
Are your MySqlDirect tolls greyed out as well?

Rob

RobD
Posts: 25
Joined: Mon 08 Nov 2004 03:41
Location: Sunshine Coast, B.C., Canada

Post by RobD » Wed 14 Dec 2005 19:40

whoops that should be "tools"

Rob

MySqlNET320 User

MySqlTools

Post by MySqlNET320 User » Wed 14 Dec 2005 19:56

I am only using MySqlNet in a VS2005 web application. I created a Windows Forms application and the tools do not appear to be greyed out. I am just trying to create connections in the code behind the page.

Matt

RobD
Posts: 25
Joined: Mon 08 Nov 2004 03:41
Location: Sunshine Coast, B.C., Canada

Post by RobD » Wed 14 Dec 2005 20:10

My tools are only greyed out for web applications. If I create a windows application I can see them in full color.

Rob

Serious

Post by Serious » Fri 16 Dec 2005 07:51

To use MySQLDirect .NET components you have to use 'Component Designer' view.

Post Reply