I will investigate your solution.

That might also help me solving my problem with CF Migration and the need of multiple Model, because actually I can't find the best way to do it !!

Do you mean that the StringLengthVerifierAttribute gets ignored when you run the "Add-Migration" command from your Package Manager Console?

If so, this is expected and outside of DevForce control as Add-Migration is an Entity Framework method and as such it can only recognize the attributes that it knows. And I'm guessing it only recognize attributes listed in Code First Data Annotations.

If you want to use DevForce Verifier attributes, and if it were me, I would do the following steps:

1. Use EF Code First attributes first to build the migration scaffolding

2. Run migration and update the database

3. Use DevForce Code Second to help generate the new entities and their properties complete with DevForce Verifier attributes.

It's not quite as straightforward but it's an option. Hopefully someone smarter than me can chime in :)

In the doc http://drc.ideablade.com/xwiki/bin/view/Documentation/code-first-entity-classes it is recommended to use the StringLengthVerifier attribute with CF class.

The problem is this attribute is totally ignored while using CF Migration. So I find myself having to duplicate those information in the Fluent API to be sure the fields will have the required size etc ...

Is this a bug or a normal behavior ?  I can't imagine duplicate this information on all the entities ...

regards