.net has entity framework an ORM has has migrations. It isn't problem free, but we found workable solutions to our issues.

By default EF will throw an error if the model (in code) and the database are out of sync. There is a setting you can set to tell the ef not to care about the version, but then you have to take the responsibility of making sure the old code will run against the new db version.

Most of our stuff is adding a new column or table so the old code doesn't rely on it and everything goes fine anyway.