TFS build order
<div> <DeployOnceUseSemver>True</DeployOnceUseSemver></div><div> <SemverInitialBaseline>True</SemverInitialBaseline></div>
<div> <MigrationOrdering>SemanticVersioning</MigrationOrdering></div><div> <Baselining>FolderBased</Baselining></div>I did not worry about it and pushed the commit. The automatic build then ran but processed the scripts in file name order, ignoring the folder name. As you would probably expect this then failed.
I changed the migration order to FilePath but the build still put the files in file name order. I've now rolled back my version of ReadyRoll to 1.14 and manually reverted the project file so it now builds and deploys OK. However I don't think this is a good long term fix.
Is this just a breaking change in the project file structure that would be fixed by moving everyone in the team to the latest version of ReadyRoll at the same time or is there a bigger problem here?