code-first

How do you represent a many-to-many relationship in the EF4 Code-First CTP3? For example if I have the following classes: class User { public int Id { get; set; } public string Name { get; set; } public ICollection<Profile> Profiles { get; set; } } class Profile { public int Id { get; set; } public string Name { get; set; } } In the database there is a UserProfiles table that has the FK for User and FK for Profile. How can I map this? EDIT: I understand how to to currently map with having a ICollection<User> property on the Profile , but I really don't want to have a an opposite navigation

All the examples I've found refer to a class called ObjectContext, which doesn't appear to exist in CTP5. I must stress at this point, CTP5 is my first exposure to the Entity Framework. I have a disconnected POCO that I have attached to my DbContext. SaveChanges does not pick up the change though, how I tell my context to update that entity? _context.Users.Attach(user); // The user has been replaced. _context.SaveChanges(); // The change is not saved. What am I doing wrong? Update 12/01/2011 Might be obvious to most, but as a first time user of EF, it didn't occur to me that attaching an

I created an Entity Framework model based on an existing database, then generated the POCO entities from the model. The connection string in my web.config isn't Entity Framework, it's just the standard connection string (it's missing the CSDL, SSDL, MSL references). I can compile my application, but when I run I get this error: Code generated using the T4 templates for Database First and Model First development may not work correctly if used in Code First mode. To continue using Database First or Model First ensure that the Entity Framework connection string is specified in the config file of

I am trying to map a TimeSpan Code First property to SQL server. Code First seems to be creating it as a Time(7) in SQL. However TimeSpan in .Net can handle longer periods than 24 hours and I need to store longer than 24 hour for event length. What is the best way to handle this with Code First. As per my previous question on how to store TimeSpan in SQL I was advised to store it as seconds or tickets etc. In the end I didn't map the TimeSpan column as there is no equivalent in SQL server. I simply created a 2nd field which converted the TimeSpan to ticks and stored that in the DB. I then

I would like to have a short example on how do you actually perform relationships in Entity Framework 4 Code-First CTP 5 ? Would love an example for these kind of relations : * one-to-many * many-to-many Thanks a lots! WestDiscGolf One to One public class One { public int Id {get;set;} public virtual Two RelationTwo {get;set;} } public class Two { public int Id {get;set;} public virtual One RelationOne {get;set;} } Things to note, it has to be virtual One to Many public class One { public int Id {get;set;} public virtual ICollection<Two> RelationTwo {get;set;} } public class Two { public int

I have two database each with their own dbcontext. I've setup two migration configurations. I can add a migration for the first db ust fine ( Add-Migration DB1_InitialCreate -ConfigurationTypeName DB1Configuration ). When I try to create an initial migration with the second db using: Add-Migration DB2_InitialCreate -ConfigurationTypeName DB2Configuration , I get the following error: Unable to generate an explicit migration because the following explicit migrations are pending: [201205082215265_DB1_InitialCreate]. Apply the pending explicit migrations before attempting to generate a new

I want to created Bi-Directional One-One relationship between two entities using EF Code First. I have trouble with the following code. What do you think I should do? public class User { public string ID { get; set; } public string LastName { get; set; } public string Password { get; set; } public string FirstName { get; set; } public int ProfileID { get; set; } public Profile Profile { get; set; } } public class Profile { public int UserID { get; set; } public User User { get; set; } public int ProfileID { get; set; } public string ProfileName { get; set; } public DateTime CreateDate { get;

So here's the scenario: DDD states that you use a repository to get the aggregate root, then use that to add/remove to any collections it has. Adding is simple, you simple call .Add(Item item) on the Collection you wish to add to. A new row is added to the database when you save. However, deleting is different - calling .Remove(Item item) doesn't remove the item from the database, it simply removes the foreign key. So while, yes, it is technically no longer part of the collection anymore, it's still in the database. Reading around, the only solution is to delete it using the data context. But