entity-framework-4.1

I'm pretty new to MVC and i'm having troubles with cascade deleting. For my model I the following 2 classes: public class Blog { [Key] public int Id { get; set; } [Required] public string Name { get; set; } [DisplayFormat()] public virtual ICollection<BlogEntry> BlogEntries { get; set; } public DateTime CreationDateTime { get; set; } public string UserName { get; set; } } public class BlogEntry { [Key] public int Id { get; set; } [Required] public string Title { get; set; } [Required] public string Summary { get; set; } [Required] public string Body { get; set; } public List<Comment> Comments

I have been trying out EF 4.1 ( code first ) with MVC 3. I am thinking ahead to when the application will need changes. I tested a couple of scenarios. I like the idea of manually editing the database when the model (my POCOs) would changed. ASP.NET error when I change the model : "The model backing the 'CTCMContext' context has changed since the database was created. Either manually delete/update the database..." Now, it says that I can " manually update the database ", but I did and still get the same error . Am I missing something !!?! EDIT Does this have to do with the model hash generate

I would like to use a stored procedure to retrieve entities from a DB, I don't care about tracking changes. I just need all entities be resolved including related ones. Do I have to use SqlCommand? What about complex properties, will they be resolved too? Any other limitations you could tell me about? Thanks! Ladislav Mrnka General answer about using stored procedures in EF is here so stored procedure in pure EF will not handle navigation properties. The answer also mentioned EFExtensions but that is not available in DbContext API. To execute stored procedure in DbContext API use: var entities

I know the question already has a solution (eg. this question ) but I really can't afford to attach the mapping logic in the same assembly where the domain (POCO classes) is. Is there any other way? I found this nice blog post but I couldn't get it working. Here is the model: public class Institute { /** Code omitted **/ protected virtual ICollection<InstituteText> InnerInstituteTexts { get; set; } private InstituteTextSet _TextSets; public InstituteTextSet Texts { get { if (_TextSets == null) _TextSets = new InstituteTextSet(InnerInstituteTexts); return _TextSets; } } } Mapping code: var

I want to define a database query using LINQ and my EntityFramework context but I don't want entities returned; I want a datareader! How can I do this? This is for exporting rows to a CSV. Cheers, Ian. This question is around EF 4, but for anyone else with EF 6 or higher you can use the AsStreaming() extension method. http://msdn.microsoft.com/en-us/library/dn237204(v=vs.113).aspx If you need this you are more probably doing something unexpected. Simple iteration through materialized result of the query should be what you need - that is ORM way. If you don't like it use SqlCommand directly.

I'm using code first and can add records without a problem. The database is created properly and is seeded without any problems. But calling SaveChanges() in my Edit action only updates the entity, not any of the navigation or reference properties. A simplified version of my model: public class Contact : IMyBaseObject { public Contact() { this.Delete = false; this.ContactTypes = new HashSet<ContactType>(); } public int Id {get; set;} public string Name {get;set;} public bool Delete {get;set;} public virtual ICollection<ContactType> ContactTypes { get; set; } public virtual USState USState {

I have an ASP.NET MVC 3 app that is using SQL Server CE 4.0 and Entity Framework 4.1 Code First. It works fine locally , but in production, it fails with the following error: The model backing the 'foobar' context has changed since the database was created. Either manually delete/update the database, or call Database.SetInitializer with an IDatabaseInitializer instance. For example, the DropCreateDatabaseIfModelChanges strategy will automatically delete and recreate the database, and optionally seed it with new data. I've verified that my application dll and database file are up-to-date on the

I have an ASP.NET MVC 3 application using an Entity Framework (4.3.1) Code First database. Now I would like to create a comprehensive zip file containing the database, the application package generated by Visual Studio 2010 and a script to deploy everything to a Windows 2008 server with IIS7 and SQL Server 2008 with a prepared (but empty) database. I don't foresee any problems with the deployment of the application package, but I'm unsure of what approach to use in deploying the database. The target environment already has an empty database that's been assigned to me, but I've been told that