This is a migrated thread and some comments may be shown as answers.

Exception Thrown from Mismatched Assemblies

1 Answer 92 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
This question is locked. New answers and comments are not allowed.
EVP
Top achievements
Rank 2
EVP asked on 25 Oct 2014, 02:06 AM
Hi there,
           I'm getting this exception when trying to query through OpenAccess. I recently had to reload Windows on my system, so I'm assuming that something is just pointing incorrectly, since I've reloaded the project onto this machine. After doing some reading on here, it looks like several others had the issue, and you told them it was caused by differing versions of the assemblies in the project. However, I can't seem to figure out how to set things straight from within the two projects, to get it working. 

Here's the exception:

An exception of type 'Telerik.OpenAccess.OpenAccessException' occurred in Telerik.OpenAccess.Runtime.dll but was not handled in user code

Additional information: Application id class 'Telerik.OpenAccess.RT.OID.IntIdentity' used by class 'Horizon_PlatformModel.Account' must have field: 'public System.Int32 _account_id'.

ASP.NET Web Application has these references:
Telerik.OpenAccess
Telerik.OpenAccess.35.Extensions
Telerik.OpenAccess.Runtime
Telerik.OpenAccess.Web.40
Telerik.OpenAccess.Web

And the EntitiesModel Project has:
Telerik.OpenAccess
Telerik.OpenAccess.35.Extensions

Any suggestions on how I can straighten this out would be appreciated!

Thanks,

Eric

(all versions 2013.3.1014.1)

1 Answer, 1 is accepted

Sort by
0
Kristian Nikolov
Telerik team
answered on 28 Oct 2014, 11:31 AM
Hi Eric,

Thank you for contacting us.

Indeed it is likely that the error you are experiencing could occur due to inconsistent versions of the Telerik Data Access assemblies in the bin folder of your projects. We would recommend deleting the bin folders of the projects in your solution which have references to Telerik Data Access assemblies and then rebuilding the solution. This should resolve the situation.

I hope this helps. Should you have further questions, feel free to post at our forums again.

Regards,
Kristian Nikolov
Telerik
 
OpenAccess ORM is now Telerik Data Access. For more information on the new names, please, check out the Telerik Product Map.
 
Tags
General Discussions
Asked by
EVP
Top achievements
Rank 2
Answers by
Kristian Nikolov
Telerik team
Share this question
or