Enumeration support fails

[Sepp]

So, once again me...

My last domain model which ended in chaos had no problem with enumerations as datatype. My new model thinks "hey would should I do it now?!"...

I have different enumerations, even in other assemblies, and for every enumerations VS2012 tells me:

The type for member with name 'EnumType' of the 'Model' persistent class is not a valid mapping for its column.

But hey... The column is a number field and in the xml I can find the followin lines:

<orm:field name="_result" property="Result" uniqueId="42971877-a54d-46e8-a12e-b361704d699c" type="BeLib.Mail.MailTransmissionCode, BeLib, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null">
  <orm:column name="Result" sql-type="number" nullable="false" length="0" scale="0" converter="OpenAccessRuntime.Data.IntConverter" ado-type="Int32" />
</orm:field>

So what's the problem here?!

[Alexander]

Hello Sepp,

This error is part of our Validation Framework which is meant to warn you about possible inconsistencies in the model. It does not mean that your model will not build or work properly.

Reviewing the details that you provided us I was able to reproduce the problematic behavior. It is caused by the fully qualified name of the MailTransmissionCode enum which seems to be an issue with the validation rule.

I created new item in our product backlog and you could see the rule fixed in some of the future versions of OpenAccess ORM.

For now you could ignore the validation error and there is nothing that you have to worry about - your enum is mapped properly. 

I hope this is applicable for you.
 

Kind regards,
Alexander
the Telerik team

[Sepp]

Hey Alexander ,

Thank you for giving me that information.It's good to hear, that everything is fine although these errors occur.

Greats,
Sepp