code-first

In EF 4.3 documentation says: By default, building a database using Code First does not include private, protected, or internal properties. If you manually included these properties in your model, Code First would ignore any data annotations on those members. This is issue now fixed, and Code First processes the data annotations. My question is how to included a protected property manully with code first, espically using fluent API? Look at http://blog.cincura.net/232147-mapping-private-or-protected-properties-with-code-first-efv4-ctp4/ to the comment from Drew Jones . Not entirely clean, but

We have our own external convention of naming objects and I need to change the naming convention for the auto generated foreign key constraints. Now it looks like: FK_dbo.City_dbo.CityType_City_CityTypeId but I would like it to be called City_FKC_CityType . I found a similar question which says that you can change the name of constraints manually. However, this does not suit me, since I have a lot of tables and foreign key constraints. I found some information about "Custom Code First Conventions" and I am wondering if I can change the name of constraint using this or if there are any methods

How can I execute a scalar function using code first? Below is what I have tried but only the query itself is being returned, not the return value. using (var dbContext = new FTTRContext()) { queryResult = dbContext.Database.SqlQuery<string>("SELECT [dbo].[ufnGetTotalUsers] (GETDATE())").ToString(); } SqlQuery returns an instance of DbRawSqlQuery . This class is an enumerable and it expects you to enumerate it via either the standard LINQ operators, or via foreach , etc. .ToString() on this object simply returns the query that will be executed . To get the result you want, use .Single() or

While working with EF code first I get error given below at different times: The entity type SomeType is not part of the model for the current context. What are the possible causes of this error? It may occur because: DbContext configured with an incorrect connection string The entity specified is actually not mapped in configuration I got this when my class that inherited from DbContext did not declare the model as a property. For example, I neglected to add a property for FooModel in the code below: public class MyDBContext : DbContext { public DbSet<FooModel> FooModels{ get; set; } // etc.

I am working with a system that has many stored procedures that need to be displayed. Creating entities for each of my objects is not practical. Is it possible and how would I return a DataTable using ExecuteStoreQuery ? public ObjectResult<DataTable> MethodName(string fileSetName) { using (var dataContext = new DataContext(_connectionString)) { var returnDataTable = ((IObjectContextAdapter)dataContext).ObjectContext.ExecuteStoreQuery<DataTable>("SP_NAME","SP_PARAM"); return returnDataTable; } No, I don't think that'll work - Entity Framework is geared towards returning entities and isn't

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

I have 2 questions: 1) How can I run Seed() method from the package-manager console without updating-database model? 2) Is there a way how to call Seed() method in the code? Thx for any advice. Answering your first question. Create a Migration by running add-migration SeedOnly Clear out all Up() and Down() code generated if there was any pending changes public partial class SeedOnly : DbMigration { public override void Up() { } public override void Down() { } } Then you can Target a Specific Migration by running update-database -TargetMigration SeedOnly in the Package Manager console After

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 have a POCO class that has two one-way unary relationships with another class, both classes share an ancestor. The names of the foreign keys in the generated schema do not reflect the property names. (Properties MainContact and FinancialContact give PersonId and PersonId1 field names). How can I influence schema generation to generate database column names that match the property names? The model looks like this: The code looks like this: public class CustomerContext: DbContext { public DbSet<Organisation> Organisations { get; set; } public DbSet<Person> Persons { get; set; } protected