Breaking changes in migration runner between 3.3.2 and 5.0.0

[Ross-Gargett]

Breaking changes in migration runner between 3.3.2 and 5.0.0

[jzabroski]

I have fixed the 5.0.0 release notes to retroactively flag this breaking change.

https://github.com/fluentmigrator/fluentmigrator/releases/tag/v5.0.0

Thanks for reporting it!

[Ross-Gargett]

Thanks for the follow-up and documentation changes.

[jzabroski]

The breaking change you are referring to is this one: b758e9c

In general, we can't provide a backwards compatible interface for this, since C# does not support return type covariance.

I disagree that it needs to be backward compatible. There are very few projects out there that still support .NET Framework Classic applications. I get why you want me to support it - it's probably less work for you.

As an alternative, why cannot your team use 3.3.2 for old projects not yet upgraded, and .NET 8 for new projects, and run .NET 8 migrations using FluentMigrator 5.0, and .NET Framework Classic migrations using 3.3.2? I am guessing this is not a lot of work for your team to support.