VS2005 RTM compatibility – When?
VS2005 RTM compatibility – When?
Guys – what’s going on? You have been offering a MySQLDirect.Net 2.0 enabled version for at least 6 months – giving us confidence that you would be ready at launch. Why no real reply about timeframes for a fix in the other threads? Are you determined to cement your growing reputation for poor customer service and tardy fixes to critical issues?
At least keep us informed – without information we are left with the frustration of uncertainty about deployment timeframes (your product worked in Beta 2!). The inclination is growing strongly within us to voice our objections loudly on the various third party forums that lead us to select your product in the first place. Is that what it will take to get your focused attention?
At least keep us informed – without information we are left with the frustration of uncertainty about deployment timeframes (your product worked in Beta 2!). The inclination is growing strongly within us to voice our objections loudly on the various third party forums that lead us to select your product in the first place. Is that what it will take to get your focused attention?
I agree.
BTW - How can you expect us to vote you best in class when you are not responsive to your customers on critical issues?
BTW - How can you expect us to vote you best in class when you are not responsive to your customers on critical issues?
Dear users,
Core Lab is pleased to announce that MySQLDirect .NET Data Provider and
MySQL Developer Tools have been nominated for the 2005 .NET Developer's Journal Readers' Choice Award
in the category of Best .NET Providers, Databases, and Tools.
Your vote in support of the performance boosting MySQLDirect .NET would be
greatly appreciated. You can cast your vote for MySQLDirect .NET and MySQL Developer Tools
at the .NET Developer's Journal website.
Please hurry, because voting ends July 31, 2005.
Thank you for your support!
Core Lab Team
-
- Posts: 36
- Joined: Tue 18 Jan 2005 20:52
- Location: SPAIN
As I know from personal experience that it's always very hard to say when some development/patch is ready for production, but I still believe that you will have no difficulties in understanding that this current situation is very disturbing. Given the fact that CLR 2.0 was out there for such a long time as beta I was hoping for immediate compatibility with the final version from your end.
Actually my primary intention for upgrading to 3.x was to be on the safe side for CLR 2.0, but that apparently didn't help much.
So I am hoping that you will tell us when you realistically expect to release the 2.0 compliant version.
Best regards,
Tillman Zschucke
Actually my primary intention for upgrading to 3.x was to be on the safe side for CLR 2.0, but that apparently didn't help much.
So I am hoping that you will tell us when you realistically expect to release the 2.0 compliant version.
Best regards,
Tillman Zschucke
Well, the week is over and still nothing. I am very upset about this. We are holding on dev work waiting for this release. It seems that core lab has been pretty good about getting new versions out but they really dropped the ball on this one. I spent good money for this product and expect to get updates when we are told that we are going to get them.
Still waiting.
ThBeer
Still waiting.
ThBeer
-
- Posts: 29
- Joined: Fri 25 Nov 2005 10:43
Apparently phpBB didn't log me on when I thought I was logged on. That 'guest' was me (not that anyone cares, but still )Anonymous wrote:Are there also plans to support 2.80.x on .NET 2.0 final? I now still have to compile our runtime libs against Beta2 because of the lack of updates on 2.80 for .NET 2.0 final.