Pavel(@pavozo) 's Twitter Profile Photo

Marina Dave Callan | dotnet How do you deal with EF core migrations in large teams in a source-control environment. Often times you need to change your model and database between UAT/testing previous release and future release.

account_circle
Pavel(@pavozo) 's Twitter Profile Photo

Dave Callan | dotnet Kleber But if you continue to scaffold each time there is a change to the database, won't it override all the changes you've made (ie. remove public constructors and make all properties private)?

account_circle
Pavel(@pavozo) 's Twitter Profile Photo

Julie Lerman Pluralsight Julie, I’ve taken several EF courses, some on Udemy and some on PluralSight. None are as thorough and relevant as your Fundamentals course. Really enjoyed it. Thank you.

account_circle
Pavel(@pavozo) 's Twitter Profile Photo

Arya - آریا 🇮🇷 We don’t mind. In fact this is the reason why we continue to pay more for healthcare so our defense budget can be larger than the next 15 countries defense budgets combined. And proud of it.

account_circle
Karen Payne MVP(@KarenPayneMVP) 's Twitter Profile Photo

Pavel Dave Callan | dotnet Also, check add a table, check then uncheck removes a table. Below I reran EF Power Tools, first time no middle name second time its added.

@pavozo @Dave_DotNet Also, check add a table, check then uncheck removes a table. Below I reran EF Power Tools, first time no middle name second time its added.
account_circle
Karen Payne MVP(@KarenPayneMVP) 's Twitter Profile Photo

Pavel Dave Callan | dotnet Speaking from experience, I simple rerun EF Power Tools to add/remove a column, so that means what's in the database is in code. With EF Power Tools you can focus on one or two etc table rather than the entire database. Also I've done by hand modifications which is rare and far…

@pavozo @Dave_DotNet Speaking from experience,  I simple rerun EF Power Tools to add/remove a column, so that means what's in the database is in code. With EF Power Tools you can focus on one or two etc table rather than the entire database. Also I've done by hand modifications which is rare and far…
account_circle
Marina(@marna_li) 's Twitter Profile Photo

Pavel Dave Callan | dotnet I have not done this in production myself. But I would ha a separate database for tests. That one you can reset whenever you need. Of course, it is easier if you have one DB per context. So you don’t have to throw away all data and to minimize risks with incongruity.

account_circle