I have tested mysql direct and i like it, its the fastest connector arround. But before i buy it i found an issue with clearing the current connection pool when you update the asp.net application. Let me clarefy things:
When you have an asp.net (webservice) application running there are connections made and these are being pooled, the connections remain open to the mysql server. Now when you rebuild the application and so refreshing the dll's etc. the connections that are opened with the previous build will not get closed and the new build adds new connections. After a few builds you run out of connections to the database. The same thing happens with the dbexplorer it keeps adding connections for almost every operation you perform.
I'm using Visualstudio 2003 and MySqlDirect v2.80.
Hope this can be fixed in a new build. Or maybe i'm doing something wrong? but other connectors don't seem to have this problem but they are so slow

Richard.