entity framework - Naming conventions for Code First migrations -

entity framework - Naming conventions for Code First migrations -

we using code first migrations maintain our database , model in sync. @ moment have version number name migration doesn't work out. problem multiple migrations same name created different developers independent of each other local database. led weird behavior imigrationmetadata.id different because of time stamp classes partial same name.

what way go phone call these migrations? examples ridiculous oversimplified: e.g. adding property readers result in migration addreaders. or should migrations broken downwards these little changes? instead of having accumulate changes 1 big migration. if there dependencies?

thanks!

entity-framework ef-code-first code-first-migrations