You can do it by manually edit code first migration:
public override void Up()
{
AddColumn("dbo.Events", "Active", c => c.Boolean(nullable: false, defaultValue: true));
}
More Related Contents:
- Code-first vs Model/Database-first [closed]
- Entity Framework: One Database, Multiple DbContexts. Is this a bad idea? [closed]
- Unique Key constraints for multiple columns in Entity Framework
- EntityFramework code-first custom connection string and migrations
- EF Code First “Invalid column name ‘Discriminator'” but no inheritance
- Improve navigation property names when reverse engineering a database
- Should I enable or disable dynamic proxies with entity framework 4.1 and MVC3?
- How do I detach objects in Entity Framework Code First?
- EF5 Code First Enums and Lookup Tables
- Debug code-first Entity Framework migration codes
- Order navigation properties when using Include and/or Select methods with EF 4.1 Code-First?
- Entity framework code-first null foreign key
- Entity Framework loading child collection with sort order
- How do I singularize my tables in EF Code First?
- Set decimal(16, 3) for a column in Code First Approach in EF4.3 [duplicate]
- How to create index in Entity Framework 6.2 with code first
- DbSet.Find method ridiculously slow compared to .SingleOrDefault on ID
- How do you ensure Cascade Delete is enabled on a table relationship in EF Code first?
- mapping private property entity framework code first [duplicate]
- What is the syntax for self referencing foreign keys in EF Code First?
- How to create index in Entity Framework 6.2 with fluent configuration
- Entity Framework Code First : Setting up One-To-One foreign key association using Annotations
- Mocking or faking DbEntityEntry or creating a new DbEntityEntry
- How to use Entity Framework to map results of a stored procedure to entity with differently named parameters
- EF Code First foreign key without navigation property
- Entity Framework Code First Using Guid as Identity with another Identity Column
- LINQ To Entities + Include + Anonymous type issue
- Why does EF5 code first use datetime2 when inserting a nullable datetime into the database?
- Can anyone spot why I keep getting this error testing the EF 5 beta
- Entity framework code first delete with cascade