ef-code-first

When using EF 4.1 Code First, is it possible to create User-Defined Data Types for your schema? Simple answer is no. Longer answer: Current EF implementation leads to multiple issues when trying to use user defined types: The type must be defined prior to its usage in table's DDL definition. Because of that the type cannot be defined in Seed method of database initializer (as often used for other database constructs like triggers or indexes). To make this work you must create whole new initializer by implementing IDatabaseInitializer and separate database creation and table creation because

I'm using Entity Framework Code First approach in my project. I have a problem with database migration. Now I have the entity public class Event { public int Id { get; set; } public string Title { get; set; } public string City { get; set; } } I have already have data in my existing DataBase. Now I want to extend City property, like this public class Event { public int Id { get; set; } public string Title { get; set; } public virtual Location Location { get; set; } } so, City become to Location with many properties. public partial class Location { public int Id { get; set; } public string

​In our Web API application, Continuous deployment need a following scenario. User will check in code in VS, Code will get automatically build, Code will be Published, Code will be deployed. But If we are using Entity Framework Code First approach, How can we update database without manual commands (Add-Migration/Update Database)and make database up to date with that check-in. You can try to run Add-Migration/Update Database commands in the build/deploy process. Assume you are using vNext build, Add a " Nuget Installer " task in your build definition first to restore the Entity Framework

I am new to Code first Entity framework, when logging into the database after running my app for the first time I got a little confused when I saw the "__MigrationHistory" table. I now understand the need for this table, but do not like it being in the standard dbo schema within the user table, I think its obtrusive and a risk. My first thought was to move it to the system folder. When researching how to achieve this within the EF context all I could find is how to move it from system to dbo. I now get the feeling __MigrationHistory should by default be created within the system folder... is

Is it possible to define a SQL case sensitive primary key in entity framework code first? I know that by default SQL is case insensitive when it comes to strings, just to be clear I don't want to change the entire DB definition to case sensitive, just one table column (primary key). I'm getting data from an external API which sends the data with case sensitive primary keys ('a' and 'A' are different records), I know I can modify them and save them differently in my DB, but this will also require me to be consistent about it everywhere in my code. That's defiantly possible, but I would rather