Open joaofbantunes opened 5 years ago
Should we have a separate helpers/utilities project?
Yes. I can create a new repository.
My idea with this one would be to use something like this AspNetCore.AsyncInitialization package (we could role our own, but since someone already done it, we can take advantage of it.).
To make it easier to test if it's working, we can create the shared project in this solution for now, and then we'll move it to the new repository. What do you think?
Want to grab this one @romanolester? If so, I'll assign the issue to you.
The steps I had imagined for this one:
CodingMilitia.PlayBall.Shared.StartupTasks
IAsyncInitializer
to handle the migrations, using AspNetCore.AsyncInitializationServiceCollection
extensions to make it easier to register the initializer in DIYes I want this one. Just please help me with the initial creation of the repo and project as I don't want to mess up with your naming convention 😊
IAsyncInitializer
to handle the migrations ServiceCollection
extensions to make it easier to register the initializer in DI@romanolester created the project and a bunch of issues, to split the work into smaller steps.
Azure Artifacts doesn't allow for anonymous access to the feeds to install the packages (at least right now). Gotta think of an alternative 😐
EnsureDbUpToDate
(besides lacking theAsync
suffix) should probably be, in this form or in another that makes more sense, extracted into a shared project, as we'll probably use it in other projects with EF Core.