This question is locked. New answers and comments are not allowed.
Dear Sir/Madam,
I've been using artificial fields in the past to extend existing modelled classes however I wanted to add an artificial type following the guide here http://www.telerik.com/help/openaccess-orm/artificial-types.html and I received the following exception
Exception:
Mapping for class 'XXX' is specified in file 'config' but the class could not be found. --> (Database.Get parameter):mapping-id=mssqlMapping/namespace[XXX]/class[XX]"}
Inner Exception:
{"Could not load type 'XXX.XX' from assembly 'Telerik.OpenAccess.Runtime, Version=2011.2.713.3, Culture=neutral, PublicKeyToken=7ce17eeaf1d59342'.":"XXX.XX"}
The artificial type is in the same namespace as the existing model, is there a setting im missing that tells the metadatabuilder to not try looking up the class?
Any help would be greatly appreciated,
Chad
I've been using artificial fields in the past to extend existing modelled classes however I wanted to add an artificial type following the guide here http://www.telerik.com/help/openaccess-orm/artificial-types.html and I received the following exception
Exception:
Mapping for class 'XXX' is specified in file 'config' but the class could not be found. --> (Database.Get parameter):mapping-id=mssqlMapping/namespace[XXX]/class[XX]"}
Inner Exception:
{"Could not load type 'XXX.XX' from assembly 'Telerik.OpenAccess.Runtime, Version=2011.2.713.3, Culture=neutral, PublicKeyToken=7ce17eeaf1d59342'.":"XXX.XX"}
The artificial type is in the same namespace as the existing model, is there a setting im missing that tells the metadatabuilder to not try looking up the class?
Any help would be greatly appreciated,
Chad
1 Answer, 1 is accepted
0
Hi Chad,
Can you double check that it is there and if you confirm it, I would like to ask you, if possible, to send us a sample application that reproduces the issue so we can debug it on our site. Greetings,
Zoran
the Telerik team
We were not able to reproduce the exception you are seeing locally. This exception usually means that the following line in the configuration is missing:
<extension key="artificial-types" value=""/>Can you double check that it is there and if you confirm it, I would like to ask you, if possible, to send us a sample application that reproduces the issue so we can debug it on our site. Greetings,
Zoran
the Telerik team
Q3’11 of Telerik OpenAccess ORM is available for download. Register for the What's New in Data Tools webinar to see what's new and get a chance to WIN A FREE LICENSE!