I am interested in the same - the writeup describes Nop.Data changes very nicely but does not pick up changes in the plugin data. When I reproduce the setps in my plugin project I get "The EntityFramework package is not installed on project" when I enable-migrations. Am a little nervous to install EF into my plugin project - any help greatly appreciated!
I am interested in the same - the writeup describes Nop.Data changes very nicely but does not pick up changes in the plugin data. When I reproduce the setps in my plugin project I get "The EntityFramework package is not installed on project" when I enable-migrations. Am a little nervous to install EF into my plugin project - any help greatly appreciated!
I got same issue, It seems that EntityFramework library was dropped in the latest version.
It was very helpful for me developing a plugin that utilizes EF's db migrations, so that my plugin's db tables and entities could automatically reflect any latest changes without running any db scripts, or uninstalling/reinstalling.
Thanks for the step-by-step procedure, I did it and it worked.
However can anybody please explain how and what mechanisms for migrations able to detect that these specific classes in Nop.Core.Domain will be created when update-database is executed?