Versions conflict

Versions conflict

Postby R. Santana » Tue 19 Dec 2006 18:56

Hello,

I have a small website created with VS2005 .net 2.0 C# originally created with CoreLab.MySql 3.20.9.0.

Now I've recopiled it with 3.50.14.0 (latest version) and all the pages of the site are working properly except one of them, I've reviewed all the references and everything is OK, theres no reference to the old assembly anywhere, and the site works fine on dev server, just fails on production server.

Can you help me?

It's very urgent.

Thanks in advance.
R. Santana
 
Posts: 36
Joined: Tue 18 Jan 2005 20:52
Location: SPAIN

Postby Alexey » Wed 20 Dec 2006 07:36

First of all, the latest version of MySQLDirect .NET is 3.55.17.
Please describe the problem in detail. How does it fail? Did you look for the old assemblies on production server?
Alexey
 
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Postby R. Santana » Wed 20 Dec 2006 07:46

Thanks for the info, I'll update to the latest one.

The whole site is working with 3.50.14.0 and that dll is on bin folder, so I don't understand why this page ask for an older version.

What I mean with fails is that only one page on the site returns this error

------------------------------------------------------------------------------------
Server Error in '/' Application.
Could not load file or assembly 'CoreLab.MySql, Version=3.20.9.0, Culture=neutral, PublicKeyToken=09af7300eec23701' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.IO.FileLoadException: Could not load file or assembly 'CoreLab.MySql, Version=3.20.9.0, Culture=neutral, PublicKeyToken=09af7300eec23701' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
------------------------------------------------------------------------------------

On the production server the only DLLs are in the bin folder of the current site.

Thanks
R. Santana
 
Posts: 36
Joined: Tue 18 Jan 2005 20:52
Location: SPAIN

Postby Alexey » Wed 20 Dec 2006 08:40

Check policy files in the GAC.
Alexey
 
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Postby R. Santana » Wed 20 Dec 2006 08:47

How can I do that?
R. Santana
 
Posts: 36
Joined: Tue 18 Jan 2005 20:52
Location: SPAIN

Postby Alexey » Wed 20 Dec 2006 08:49

Go to the GAC and delete all policy files for MySQLDirect .NET.
Alexey
 
Posts: 2756
Joined: Mon 13 Mar 2006 07:43


Return to dotConnect for MySQL