entity-framework-4.1

I have following two Entities that I am trying to relate (one to one) using foreign key associations. public class StandardRack { public int Id {get;set} public StandardRelay StandardRelay {get;set} } public class StandardRelay { public int Id {get;set} public int StandardRack_Id {get;set;} [Required][ForeignKey("StandardRack_Id")] public StandardRack StandardRack { get; set; } } This throws ModelValidationException. Any ideas why such a seemingly simple one-to-one bidirectional relationship cannot be configured. Edit: Here is the Exception: System.Data.Entity.ModelConfiguration

How do I define a database view using Entity Framework 4 Code-First? I can't find anything about this anywhere! Ladislav Mrnka That's because you cannot define database view using code-first approach. Database view is database construct which uses SQL Query on top of existing tables / functions. You can't define such constructs using code first. If you want view you must create it manually by executing CREATE VIEW SQL script for example in custom initializer - it will be similar like this answer . Just be aware that this will not help you if you want to map entity to a view. In such case you

I'm using Entity Framework 4.1 code first approach. I want to make eager loading as my the dafault configuration, and by that avoid using the Include extension method in each fetching query. I did as recomended in MSDN, changing the simple lazy property at the DbContext constructor: public class EMarketContext : DbContext { public EMarketContext() { // Change the default lazy loading to eager loading this.Configuration.LazyLoadingEnabled = false; } } unfortunately, this approach is not working. I have to use the Include method to perform eager loading in each query. Any ideas why? Thanks in

I am a bit confused about whether to use DbSet.Create, or simply new up an entity and add it. I don't really understand the ramifications of using DbSet.Create. I understand that DbSet.Create will create a proxied version if applicable, but I don't really understand what that means. Why do I care? It seems to me that an empty Proxied class is no more useful than a non-proxied class, since there are no related entities to lazy load. Can you tell me the difference, beyond the obvious? And why would you care? Slauma A scenario where using DbSet<T>.Create() makes sense is attaching an existing

All my models contain at least two associations. When modeling this in ef4 I've only been able to do this without a second Foreign Key property through the use of the fluent interface. ForeignKey seems like the right attribute to use, except for the fact that it requires a string parameter. So my question is, can you have a navigational property and declare it as such using an attribute? public class User : IAuditable { // other code public virtual User Creator { get; set; } public virtual User Modifier { get; set; } } I believe, it is not possible to define the relationship only with data