Take namespaces into account in POCO mapping
This is a must for modularity. We already support this feature on our side with schemas (sql server) the only problem is EF does not take namespaces into account.
This is now complete in EF Core. We are not planning to retrofit the capability into EF6 but if this is very important to you, create and issue in our github issue tracker.
This is a must for clean Domain Driven Implementation.
tim ford commented
Please change the key to use full class name instead of name.
The type 'WebApplication8.Models.Tests.Person' and the type 'WebApplication8.Models.Person' both have the same simple name of 'Person' and so cannot be used in the same model. All types in a given model must have unique simple names. Use 'NotMappedAttribute' or call Ignore in the Code First fluent API to explicitly exclude a property or type from the model.
Dr. David T. Macknet commented
Please FIX THIS! This is not a feature. This is an obscenity. Otherwise what's the use of Namespaces?
Please this feature is a must
Kevin Forbes commented
More details about the error here: http://social.msdn.microsoft.com/Forums/et-EE/adodotnetentityframework/thread/cad3ca46-cf7a-4371-91f9-541c46284d18
The actual exception is: "The mapping of CLR type to EDM type is ambiguous because multiple CLR types match the EDM type..."