Please do not deprecate /MigrationsFolderXML
We are using SQL Compare extensively in our company department and one of the features we are enjoying is the ability to generate the scriptsfolderxml and migrationsfolderxml on the fly based on which database we want to deploy.
In my view deprecating this feature will leave the product in a degerated state. The option is then to use the /migrationsfolder but first I will have to manually sync the migrations folder from source control and then point to it. Sure it is doable but definitely not preferable.
Sorry for the delay in responding to this request. As Sergio notes in this forum thread ( https://forum.red-gate.com/discussion/80946/migrationsfolderxml-in-sqlcompare-12 ) the option has been removed from SQL Compare, since version 12 is now using the new migrations model from SQL Source Control 5 which doesn’t require this extra parameter to work.
David Brower commented
I am disappointed that there was no response to this item from Redgate. There has been no response to a question on the Redgate forum regarding possible workarounds either.