Page 1 of 1

Upgrade to version 4 bug?

Posted: Wed 18 Apr 2007 15:15
by wcarlson40
I followed the instructions EXACTLY for upgrading from registered version 3 to registered version 4. (First made sure all instances of Visual Basic .NET were closed, and then uninstalled from the Uninstall link on the Start Menu. Then I installed version 4).

Unfortunately, when I open my projects, they had all lost all MySqlConnection and MySqlDataAdapter objects, thus creating multiple errors within my application (and I have MULTIPLE connections and dataadapters for different forms). Thankfully, reinstalling version 3 and restoring my project from a backup resolved everything, but this problem is reproducible.

Perhaps some useful information for debugging - my MySqlConnection and MySqlDataAdapters are named OleDbConnection1 and OleDbDataAdapter1 since I used the Migration Wizard. Perhaps that is where things get messed up when upgrading?

Posted: Thu 19 Apr 2007 07:21
by Alexey
You should delete reference to CoreLab.MySql.dll and re-add it then. Also add reference to CoreLab.Data.dll.

Posted: Fri 20 Apr 2007 01:07
by wcarlson40
Yes, I understand that this would work, but to delete all my references and then reconfigure connections and dataadapters is no upgrade.
This sets me back hours of work. I'll stick with the old version for now...

Posted: Fri 20 Apr 2007 07:48
by Alexey
delete all my references and then reconfigure connections and dataadapters is no upgrade
Each application has only one reference to CoreLab.MySql.dll. Why will it take hours?

Posted: Fri 20 Apr 2007 17:50
by wcarlson40
Ahh, I guess I am truly mistaken. I thought you meant to remove each component? (the icons you drag onto your forms from the Toolbox on the left to create the connections, etc.)

Thanks, I will give it another try.

Posted: Sun 22 Apr 2007 20:39
by wcarlson40
Thanks, that seemed to do the trick. All is well again with version 4.

Posted: Mon 23 Apr 2007 08:56
by Alexey
Well done!