Migrate/Create schema from C#?

[srad]

Is there a way to call the dotnet mysql-cache create ... from C# code, like with DbContext and EnsureMigrated()? Otherwise I need to roll out a launch script for every container image to run dotnet mysql-cache create before each application launches.

[ChaosEngine]

How does this approach sounds:

1. dotnet tool install --global Pomelo.Extensions.Caching.MySqlConfig.Tools --version 2.2.0
2. In Your project add this project reference:

  <ItemGroup>
    <Reference Include="dotnet-mysql-cache">
      <HintPath>..\..\..\..\.dotnet\tools\.store\pomelo.extensions.caching.mysqlconfig.tools\2.2.0\pomelo.extensions.caching.mysqlconfig.tools\2.2.0\tools\net8.0\any\dotnet-mysql-cache.dll</HintPath>
    </Reference>
  </ItemGroup>

meaning, reference the internal installed tool library in Your project

3. Now You can execute following code passinjg any input parameters as one would do for CLI tool:

void MySQLCacheToolTest()
{
	var program = new Pomelo.Extensions.Caching.MySqlConfig.Tools.Program();
	//program.Run(["-h"]);
	//program.Run(["script", "tabName1"]);
	program.Run([
		"create",
		"server=127.0.0.1;user id=SessionTest;password=SessionTest;persistsecurityinfo=True;port=3306;database=SessionTest;Allow User Variables=True",
		"tabNameXXX"
	]);
}

@srad, is this feasible ?

[srad]

Thank you, that of course would probably work, I can also just execute a command to the shell, but I thought this is a more general case which concerns deployment. Why not just run a migration when the cache is added in Program.cs? Like Hangfire for example does, it just is added and runs internally the migration and just works.

[ChaosEngine]

Thank you, that of course would probably work, I can also just execute a command to the shell, but I thought this is a more general case which concerns deployment. Why not just run a migration when the cache is added in Program.cs? Like Hangfire for example does, it just is added and runs internally the migration and just works.

Because that would mix up the separated responsibilities rule:

• Pomelo.Extensions.Caching.MySql is a caching library very much based on the SqlServer equivalent
• Pomelo.Extensions.Caching.MySqlConfig.Tools is a tool for creating the structures that the above operates on.
• I don't want the same table creation code (DDL) in both. DRY rule also suffers here.