entity-framework-4.1

i used to use the ObjectSet in EF 4.0, I could get the underlying Context for this ObjectSet using myObjectSet.Context which returns ObjectContext . Now with DbSet in Ef4.1, what is the equivalent ?? EF 4.1 does not offer a public API to get the DbContext from the DbSet instance. You would have to use Reflections API to get the DbContext instance. Edit One workaround would be to pass around the DbContext instace with DbSet instance. Eg if you had a constructor that took only a DbSet instance. Pass the DbContext instace also. public MyService(DbContext context, DbSet<MyClass> mySet){} Other

I am using Web.Config transformations to deploy my application to Azure. I also have 2 sites in my service, a public website, and private WCF site endpoint. I am deploying multiple sites to a single role . When I deploy, the website project (for which the Azure Deploy project is set) transforms the web.config correctly. However, the WCF project (which is only addressed as a "site" in the .csdef file) does not transform the web.debug.config file to web.config. This question is similar, but only addresses the projects building. I have set the dependencies in my project. This workaround forces

I am just getting started with Entity Framework 4.1, trying out the "database first" mode. When EF generates a Model class with the "ADO.Net DbContext Generator," shouldn't it identify the primary key for the class with a [Key] attribute? Without this, it appears incompatible with the T4 MVCScaffolding. Here are the details: Using the Entity Data Model Designer GUI, I have added a simple "country" table to the model from my existing database. The GUI correctly identifies a single integer identity key field named "PK" as my primary key. (Alas! I'm a new user so I can't add a screenshot. I've

Is it possible for Entity Framework 4.0 to have an association/navigation property based off of a foreign key to a non-primary key field (it has a unique constraint). No because EF don't understand unique constraint yet and relations in EF must follow same rules as relations in database. Without unique principal relation cannot exist and the only way to get unique principal in EF is using primary key. 来源： https://stackoverflow.com/questions/9217448/entity-framework-foreign-keys-to-non-primary-key-fields

Consider the following entity model: public class Agreement : Entity { public int AgreementId { get; set; } public virtual ICollection<Participant> Participants { get; set; } } public class Establishment : Entity { public int EstablishmentId { get; set; } } public class Participant : Entity { public int AgreementId { get; set; } public virtual Agreement Agreement { get; set; } public int EstablishmentId { get; set; } public virtual Establishment { get; set; } public bool IsOwner { get; set; } } The reason there is not a direct ICollection<Establishment> on the Agreement entity is because of