title: Getting control of a legacy DbUp project
body: <p>I'm working on a ASP.NET Core Razor pages project that includes IdentityServer and IdentityFramework with various customisations to the identity model -- all quite standard stuff.</p>
  <p>What's not standard, though, is that someone has deicded to not use EntityFramework migrations but use <code>DbUp</code> instead.</p>
  <p>I can see that changes to the C# model correspond to SQL files -- in the same way that they would correspond to EF migrations.</p>
  <p>The mystery is how the DbUp SQL files were produced.</p>
  <p>The filename are of the format <code>M&lt;timestamp&gt;_&lt;name&gt;.sql</code> -- where has the initial <code>M</code> come from?</p>
  <p>None of the projects has the <code>dbup-add-migration</code> package installed (only <code>dbup-core</code> and <code>dbup-sqlserver</code>).</p>
  <p>So: if, say, I edit a model class then what do I do to make the corresponding <code>MyyyyMMdd_name.sql</code> file?</p>