Entity Framework Design Meeting Notes
The Entity Framework team has a weekly design meeting in which we discuss/recap design and other issues with the codebase. These are the notes from those meetings. The intention is to provide a history of what decisions have been made and why. No attempt
is made to go back and update notes from older meetings if we later change a decision and decide to do something different.
- Metadata API surface
- Pluralization service exploratory testing feedback
- Metadata unification
- Porting existing SQL tests
- How should pluralizers be made available?
- Clustered/non-clustered unique identifier primary keys and SQL Azure
- Lightweight conventions
- Clustered/non-clustered unique identifier primary keys
- Potential contribution for pluralization service
- Additional ObjectContext and EntityConnection constructors
- Default schema changes during initialization
- Making EF queries buffer by default
- SQL Azure connection resiliency
- WET, DAMP, or DRY tests
- Handling pull requests
- Making READ_COMMITTED_SNAPSHOT the default
- Database First WinForms data binding
- Automatic EntityTypeConfiguration discovery
- Lightweight conventions
- View generation API
- Removal of Code Contracts
- Lightweight conventions
- Connection resiliency to transient failures
- Change default mapping for DateTime
- Lightweight conventions
- DbConfiguration exploratory testing
- Code Contracts discussion
- Global spatial provider
- Set-based configuration
- Dependency resolver scoping
- Sugar methods for services
- Simplified API for common conventions
- By-convention parameter binding SqlQuery overload
- SqlCE relative path connection string UX issues with Migrations
- Pluggable Conventions
- Polish the conventions API
- Breaking change
- Make ObjectContext implement IObjectContextAdapter
- Migrations multi-tenancy
- Designer versioning
- Async protection
- Getting schema Information from providers
- Using IDbDependencyResolver with existing IoC containers
- CUD Batching
- Bulk operations
- Async
- One-pagers
- Initializer proposal
- Model key caching
- Migrations history table schema changes
- Async immediate LINQ operators
- Refactoring and unit tests
- Making database connections in the test suite more configurable
- Naming convention for static readonly and const fields
- How will we handle breaking changes in EF6?
- High-level ideas for using dependency injection with EF and specifics for the provider
- Making EF code more testable
- Code duplication in Async
- Supporting MVC scaffolding