Christian Sindberg Oddershede

I guess i could write my own executable and have a look at if there is anything that is being downgraded with the specified version. Then do a migrateDown if...

@jzabroski I'm not questioning the quality of FluentMigrator. I find it to be clean and easy to understand and generally an excellent tool. :) However specifying up or down on...

I'm trying out Continous Delivery. So I'm trying to avoid branching all together. But even with rigorous testing you still might need a rollback every now and then.

Continuous delivery to me is a lot of small incremental commits where all commits should be ready for primetime. That means having adequate testing. With those premises branches don't make...

I can absolutely use this assuming at least one of the versions is inclusive (for example minimumversion = 1.0.0 means >= 1.0.0)

Sorry I'm on the holidays and did some NuGet before I left for the holidays. (Hence the version confusion) 1. I agree that minimumversion and maxversion are better names in...

I see your pickle. But if you are including a modified version of a listed package things can get really confusing. If I install your package and afterwards install the...

I had the same approach in mind that Collin mentions. Simply including the code in your assembly under a different namespace. This shouldn't be a breaking change. Since you are...

It's not possibly to supply a release name for the HelmTemplate task at the moment. If you use SetName it will supply the --name parameter which is obsolete per: https://helm.sh/docs/helm/helm_template/