entity-framework-4.1

I am using EF Code first with database first approach. "with Database.SetInitializer(null);" My table has two columns createddate and amendddate. They are managed by SQL Server using triggers. The idea is that when data entry happens then these columns gets data via triggers. Now What I want to do is to make this read only from EF Code first point of view. I.e. I want to be able to see the createddate and ameneded dates from my app but I dont want to amend these data. I have tried using private modifiers on setter but no luck.When I try to add new data to the table it tried to enter DateTime

Does anyone have any best practices around deploying database changes in an EF 4.1 code-first solution? I know MS does not currently support database migrations for EF 4.1, but obviously people are going to need to do this from time to time. Thanks Once you deployed database to production you must do incremental changes. It means that before you deploy next version you must prepare two databases in your dev box: Database with DB schema currently deployed in production - you should be able to get this from source control so always correctly label / tag your production releases Database with new

I've spent decent amount of time on this problem and still can't figure out why EF team makes the life so hard using Code First. So here is some sample: My POCO: The way I want the thing to look like: public class Post { public int Id {get; set;} public string Text {get; set;} } protected override void OnModelCreating(DbModelBuilder modelBuilder) { modelBuilder.Entity<Post>() .Property(p => p.Text) .HasColumnType("nvarchar(max)"); } The only thing that works: public class Post { public int Id {get; set;} [StringLength(4000)] public string Text {get; set;} } The problem is that when in first

Looking at my Elmah error logs, I am seeing a few InvalidOperationException s from Entity Framework that deal with: The context cannot be used while the model is being created. This is with the latest EF CodeFirst library from Nuget. The only information I have been able to find on the net is that it is being caused by having data contexts as singletons, which is most certainly not my case. In my Windsor installer, my EF unit of work structure is being registered with: container.Register(Component.For<IUnitOfWork>() .ImplementedBy<EFUnitOfWork>() .LifeStyle .PerWebRequest); I am able to

I am receiving "The context cannot be used while the model is being created." issue in my web application in one of my webpages. This particular webpage POSTs to the server every 2-3 seconds to refresh the screen. From my testing I found that If I have 2 or more browser instances open to this page, after several minutes I receive a "The context cannot be used while the model is being created" exception from deep in the repository. This code calls a "service" to retrieve the needed data. This code is executed in an custom authorization attribute of the MVC Controller class. // Code in custom

I have a simply code in Entity Framework 4.1 code first: PasmISOContext db = new PasmISOContext(); var user = new User(); user.CreationDate = DateTime.Now; user.LastActivityDate = DateTime.Now; user.LastLoginDate = DateTime.Now; db.Users.Add(user); db.SaveChanges(); user.Avatar = new Avatar() { Link = new Uri("http://myUrl/%2E%2E/%2E%2E") }; db.SaveChanges(); db.Users.Add(new User() { Avatar = new Avatar() { Link = new Uri("http://myUrl/%2E%2E/%2E%2E") } }); db.SaveChanges(); The problem is that I get an error An error occurred while saving entities that do not expose foreign key properties

I've faced with situation when I need to have EF readonly property in case of 'optimistic update'(you do not load current state of your domain object from database to check what properties are really changed. You just set your object as Modified and update it to database. You avoid redundant select and merge operations in this case). You can't write something like this : DataContext.Entry(entity).Property(propertyName).IsModified = false; , because setting of 'false' value is not supported and you will get an exception. (in EF 4.1) I've created a simple structure for registering readonly