VersionTableMetadata info is out of date and inaccurate #69

Activity

1. jzabroski commented on Feb 19, 2024

   

   jzabroski

   on Feb 19, 2024

   Last edited by jzabroski

   Contributor

   More actions

   "Use DI" means:

   • Set-up your own in-process runner where you register dependencies, rather than using dotnet-fm CLI tool or the legacy CLI, etc.
   • In the in-process runner, you can add constructors to your Migrations and have those migrations take an IApplicationContext dependency that can be whatever you want - the type does not even need to be called IApplicationContext.

   The reason Application Context is obsolete is that it doesn't make sense to have it as a property when you could have a strongly typed thing you inject instead. The Context is typically dynamic/external resource, like an IConfiguationService. Additional things that are not Saga-like appplication context state that you might want to inject include your database access layer / library. For examples, NHibernate, EFCore, Dapper, RepoDB.

   What problem are you trying to solve?

   Using .Services.AddSingleton<IConventionSet>(new DefaultConventionSet(defaultSchemaName: "myschema", workingDirectory: null)) with Sql Server doesn't set the schema for version table to myschema, instead defaultSchemaName attempts to set the database!

   I have not looked into this claim, this is a documentation repo, not the code repo. Did you look at how FluentMigrator.DotNet.Cli registers convention sets?