Hello,
I know that questions has been asked many times, but I just can't find an answer that satisfies me. I am developing a plugin that uses data access as described in the "plugin with data access" article in NopCommerce's documentation. It works fine, but I know I will have many versions, adding many features along the way and I know the data model will evolve over time. How can I make sure I can make that data model evolve without causing major problems for my clients when installing a new version? Must I resort to update scripts? I find it complicated for some less technical clients. Can there be an automated way for the plugin to update its own tables? I've seen some solutions using EF's migration functionality, but some say it does not work with NopCommerce version 4.0 and up. What is the "standard" way to go with this?
Obviously, if I uninstall the plugin and install it again, the tables are created accordingly, but the uninstall process drops the original tables along with the data they contain, so it's not acceptable in a production environment.
What must I do so it's easy for the client and still remains flexible enough so I can provide an evolving product?
Thanks
Dany Latulippe