Hi, Boyko.
I understood the problem and will make changes, only we will use the MigrationBase class to search and not the IMigration interface (I hope this level of abstraction will be enough). But even now any migration will be performed, if its assembly is loaded, the main thing is that there would be at least one AutoReverseMigration migration in the assembly, then all other migrations will also be performed.
I understood the problem and will make changes, only we will use the MigrationBase class to search and not the IMigration interface (I hope this level of abstraction will be enough). But even now any migration will be performed, if its assembly is loaded, the main thing is that there would be at least one AutoReverseMigration migration in the assembly, then all other migrations will also be performed.
Hi Sergei,
Yes, it works fine for plugins that have both types of migrations but we have ones that will not have any AutoReverseMigration migrations in them and we need this change for these plugins.
Using the MigrationBase is perfectly fine as we inherit from the Migration class anyway.
p.s: Actually searching for assemblies containing IMigration causes some NullReference exceptions on a clean nopCommerce install in the GetMigrationInfoForMigration method so please have this in mind when you make the changes and make sure it does not break the clean nopCommerce installation process.
Thank you!
Boyko