The thing is if it was a recomposition issue I should be able to use the model, few second after the error, once the recomposition is done  right ? because if I navigate to another screen which use the same model I will still get the same error, not matter how long I wait before to navigate.

That would means the error is more certainly because of Postsharp.

But, if I reference the same model in the silverlight Application it works so I am confused to what is the real cause.

The error message about the missing constructor is missleading here. What's actually going on is that the EntityManager fails to instantiate. I can tell that from the following error:

 

 

What does the inner exception say?

 

I see these errors primarly if PostSharp didn't do it's job, but maybe in this case it has something to do with the xap loading. I did test xap loading, but I don't remember if I tested it with a CF domain model in the dynamic xap. I have to put together a small repro and see If I get any issues.

 

Sorry, you are having these issues. We appreciate you attempting this migration. With a beta product there are bound to be issues.

 

We did make composition-related changes in both DevForce and Cocktail in the 2012 beta release, but based on this error I don't know whether the problem is there, or in the XapLoader I see in the sample you sent.  Until DevForce has fired the Recomposed event the newly loaded entity types won't be available, and the lack of metadata for these entities could cause an EntityManager constructor to fail.

If I set a reference to those model on the appplication it works.

Looks like there is a recomposition issue. Maybe something is broken on my part with the mix of yield return and Task.

I will try the Ignore() once I get the domain working. Actually only the Security model works, the 3 others aren't and all get the same error :

Each entityManager owns this constructor I you can see in the model I sent you.

What could cause this error ? everything was working in previous version.

In the Log, the domain assemblies are probed on the server.

Probe Assemblies: xxx.Common.Domain, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null :: xxx.Commun.Domain, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null :: xxx.Security, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null 

I can see the log when it instanciate the security domain :

Metadata file 'xxx.Security.xxxDBSecurity.ibmmx' loaded from assembly 'xxx.Security, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' 

but nothing about the xxx.Commun.Domain model I currently try to use.

below the full error message :

This migration is really a pain in the ass, I started saturday and I still don't have a running application ;(

I think you can work around the issue by using the Ignore method instead of the NotMapped attribute.  I was able to get the model built when I added the following to TiersConfiguration:

 

One other thing to look at is whether you have an older EntityFramework assembly in the Global Assembly Cache, and also ensure that the EntityFramework.dll is in the bin folder of the application project.

 

If that looks good, would you be willing to send us more of your model code?  I'm specifically interested in whether you have a DbContext defined, the full definitions of "Personne", "Adresse" and "Professionel", and what flavor of inheritance you're using.  The EntityManager, and DbContext if present, would help too.  You can send either to me via a PM, or to IdeaBladeSupport.

 

We haven't seen this NullReferenceException issue, and as you say the error message doesn't help.  Is the model project in which you get this error the one referencing the assembly containing the base class?  You mentioned that you created an empty EntityManager to work around the problem building the assembly holding the base class, so one thing to try would be removing this EM.

 

Regarding the attribute problems you mention in your first post, these are due to EF 5 data annotation changes.   We hadn't seen these issues before now, but some quick googling shows that others are having this issue with using NotMapped when inheritance is involved.  We don't have a workaround to suggest right now, but as soon as we do we'll let you know.

So I need access to Aop for the ProvideEntityAspect attribut

 

The DevForce.cf file gets added by the Code-First package. You shouldn't install the Code-First package to a project that doesn't contain model classes.

I am doing the migration on a clean VM under Win8 where I only installed VS2012 and devforce/cocktail thru nuget

For this issue it was related to this one http://www.ideablade.com/forum/forum_posts.asp?TID=3651&title=nuget-packate-server-add-extra-entry-to-webconfig

Like for the global.asax, the server package created a Devforce.cf file that I didn't notice before.

Removing this file fixed it.

Did you completely uninstall DF 2010? Code-First builds currently do not work with DF 2010 and DF 2012 installed side-by-side.

I first though the problem could come from the connection string but here is the log from model which build :

I am trying to migrate from 2010 to 2012.

When I try to build I get this error when it was working in the previous with the 6.1.8.

This assembly doesn't contains any entitymanager or DBContext because it hosts the base class (all abstract) for all the others domains assemblies.

Is it now mandatory to create a DBContext or entitymanager in any assembly hosting a code first class even if all are abstract  ? 

I created an internal empty entityManager to be able to continue the migration but I feel I shouldn't have to.

Another issue (also working in 6.1.8)  :

I already have the NotMapped attribut on the property AdressPrincipal (below the code)

I don't know, generaly speaking, if I should put the DataContract attribute on  the inherited class if the parent class has it

Anyway I tried both case and both give this error